Johnny McConkie

Case study

Voley

A communications platform for independent insurance agencies, built on an official HawkSoft integration. I was the technical lead and also the one selling it.

Visit letsvoley.com (opens in a new tab)

Role
Co-founder & Technical Lead
Timeline
Feb 2025 – Apr 2026
Team
Me + 5 contract developers
Stack
Next.js, Node.js, PostgreSQL, Twilio
Results
30 agencies signed · $42K in grants · keynote, Insurtech Utah 2025

Problem

Independent insurance agencies had no central place to communicate with clients. Agents texted from personal phones, nobody else in the office could see or pick up the thread, and every conversation had to be logged into HawkSoft, their agency management system, by hand.

What I built

A shared inbox for the whole agency, on the agency’s own business number, where every conversation syncs into the client’s record in HawkSoft automatically through an official two-way API integration.

I owned the architecture and the product roadmap, managed five contract developers, and wrote code alongside them. I also ran carrier A2P 10DLC registration and compliance for every agency.

  • Two-way SMS and MMS on agency numbers, via Twilio
  • Official two-way HawkSoft integration: messages land on the client record, no manual logging
  • Internal team chat, so agents can hand off and discuss a client in context
  • Web chat for agency websites, feeding the same inbox
  • Automated review requests and messaging automations
  • Mobile app for agents on the go
  • VoIP calling, built and tested but never released to users

Architecture

An inbound text arrives through Twilio, is stored, matched to the client in HawkSoft, and shows up in the agency’s shared inbox. Replies travel the same path back.

Hard parts and decisions

Partnering with HawkSoft

The integration itself wasn’t the hardest engineering on the project. The real lesson was working as a small startup alongside a much larger company: earning official partner status, building against production APIs we didn’t control, and meeting their standards for anything that touched agencies’ client records.

Running a team while selling

I broke the roadmap into tasks matched to each developer’s strengths, ran check-ins every two weeks, and reviewed and wrote code myself. The same weeks, I was cold-calling agencies and running demos, so the team needed clear specs that didn’t depend on me being in the room.

Selling it

I built the pipeline myself through cold outreach and technical demos. 54% of cold-call conversations turned into demos, and 45% of demos turned into signed letters of intent. We signed 30 agencies, and 12 committed to onboarding. We won $42K in grants, including $17K across three BYU Miller Grants, and I gave the keynote at Insurtech Utah 2025.

A dependency we didn’t control

Texting from a business number requires carrier approval under A2P 10DLC. Those rules tightened in February 2025, right as we launched, and registrations kept failing. The agencies waiting to migrate were blocked on approvals we never got.

Why we shut it down

We could have kept grinding. But between the compliance wall, lukewarm follow-through after signing, and a ceiling of maybe 50 to 100 agencies, the math didn’t work. Agencies on other management systems didn’t have the same problem, so growing beyond HawkSoft would have meant building a different product. We were running low on money and decided our time was worth more elsewhere.

What I learned

A letter of intent is not demand

People will sign something that costs them nothing. The real signal is someone paying or changing how they work. Our top of funnel looked great, but fewer than 10% of the agencies that signed letters of intent ever actually used the product. A product that asks a team to change how it operates is a much harder sell than it looks, especially in an established industry like insurance.

Know what you don’t control

Our core feature depended on carrier approval. Working around it was possible, but would have cost more time and money than we had. Today I treat any external approval or platform dependency as a day-one risk, before writing code against it.

Validate the pain, not just the gap

Agencies on other management systems had no tool like ours, which looked like an open market. But their systems worked differently, and the problem we solved barely existed for them.