Suggestions
Richard Perrott
CoFounder // COO at ThreeFlow
Richard Perrott is the COO and Co-Founder of ThreeFlow, a Benefits Placement System startup based in Chicago.123 He has over 18 years of experience in the employee benefits insurance industry.1
Professional Background
Career Highlights::
- Co-founded ThreeFlow in January 2015, originally launched as WatchTower4
- Previously a Sr. Employee Benefits Representative at Sun Life Financial (July 2005 - June 2014)2
- Member of 1871 and Catapult Chicago tech communities2
Education
Perrott graduated from Western Michigan University with a Bachelor's Degree in Sales & Business Marketing and Economics. He was also a Varsity Soccer player during his university years.2
Professional Role
At ThreeFlow, Perrott serves as the COO, working alongside CEO Ryan Sachtjen and other executives to develop a platform that simplifies the employee benefits insurance placement process.134 The company aims to connect brokers, carriers, and employers through a shared digital system, addressing inefficiencies in the benefits industry.3
Perrott's LinkedIn profile indicates he has 500+ professional connections and is located in Chicago, Illinois.2
Highlights
Will brokers invite more carriers to an RFP when they use tech?
We get this question every so often from carriers. On the surface it’s a reasonable fear — they’re concerned brokers will shotgun the market when tech can enable them to do so, but we’ve observed this not to be the case.
It helps that we aren’t a reverse auction, and never will be. The digital pipes we’re building enable the benefits industry to flow more smoothly and drive better outcomes for brokers, carriers, and employers alike.
What we’ve found is that broker behavior remains largely the same when tech is added. Those who prefer to manage their book of business with a small stable of carriers maintain that position. Those who prefer to send their RFPs to more can still operate that way, but (with data) both parties have a clear view of that reality.
By analyzing over 5,000 RFPs we’ve learned that the average number of carriers invited to an RFP is 6, and the optimal number to find savings for your client is 4.
More data in our blog below. Track it yourself and see what feels right for you.
When faced with a problem, we tend to add when subtracting might generate a better outcome.
ThreeFlow has a complex business.
We’re a 2-sided marketplace (brokers & carriers) transacting an intangible good (insurance) over the internet in service of a 3rd party (the employer). Our industry is antiquated, regulated, and highly seasonal. Plus, we have a multivariate utilization-based revenue model.
I often find myself looking at the ceiling trying to find simplicity on the other side of the complexity.
Lately, I’ve been leaning into the principle of subtraction by asking myself these questions:
𝐖𝐡𝐚𝐭 𝐜𝐚𝐧 𝐲𝐨𝐮 𝐫𝐞𝐦𝐨𝐯𝐞? ⛔ -> Kids don’t learn how to ride a bike with training wheels anymore. The new method is to remove the pedals and lower the seat so they can touch the ground. By removing the pedals they learn how to balance first (the hard part).
I personally stopped scheduling invites for quick syncs with teammates. I leave them an audio file or recording instead. This usually prompts them to start doing the same.
𝐖𝐡𝐚𝐭 𝐜𝐚𝐧 𝐲𝐨𝐮 𝐬𝐡𝐢𝐟𝐭?💡 -> Airports place baggage claims several minutes away from arrival gates to reduce the perceived waiting time of retrieving your bag. The more time you spend walking, the less time you perceive waiting.
Our customers told us they prefer not to build their full book of business out in our system up front. We built workflows to to shift this to the moment of renewal receipt or decision to go to RFP. This aligns better with their needs.
𝐖𝐡𝐚𝐭 𝐜𝐚𝐧 𝐲𝐨𝐮 𝐫𝐞𝐩𝐮𝐫𝐩𝐨𝐬𝐞? ♻️ → Once shipping containers reach their end of life, they usually sit unused in ports. Architects and builders are now repurposing them to create versatile living and working spaces.
ThreeFlow rotated a few members from our Ops team to our Support team during busy season last year. Their knowledge of our product and processes transferred beautifully, and the model is serving as an exciting new way to provide extra support to our customers while providing new experiences for our team.
𝐖𝐡𝐚𝐭 𝐝𝐨𝐞𝐬 𝐭𝐡𝐞 𝐜𝐮𝐬𝐭𝐨𝐦𝐞𝐫 𝐰𝐚𝐧𝐭? ❤️ Our brokers want the analysis that comes out of our system to look EXACTLY like their own branded client deliverables. It makes sense, but building this level of in-app customization would add endless complexity (and likely still fall short of the customer’s needs). We stopped trying to solve this within our product, and found a way to solve it through post-processing AFTER the analysis exported from our system. This gives the customer what they really want.
𝐖𝐡𝐚𝐭 𝐨𝐧𝐞 𝐭𝐡𝐢𝐧𝐠 𝐜𝐚𝐧 𝐲𝐨𝐮 𝐝𝐨 𝐭𝐡𝐚𝐭 𝐰𝐨𝐮𝐥𝐝 𝐦𝐚𝐤𝐞 𝐞𝐯𝐞𝐫𝐲𝐭𝐡𝐢𝐧𝐠 𝐞𝐥𝐬𝐞 𝐞𝐚𝐬𝐢𝐞𝐫?✌ ThreeFlow is on a quest to create a keyboardless quote submission experience for our carrier partners (no manual data entry). More news on this will drop in the next 30 days.
There’s always more to simplify. What questions do you use to cut the noise?
