GTM Sauce

TalkingParents · B2C · co-parenting communication app

Run your main calling feature on a small startup vendor instead of Twilio

Startup couldn't scale; flagship feature broke and they moved to Twilio

Failedteam-processfeature-development

What they did

For recorded calling (the flagship feature, needing masked locations and phone numbers and stream muxing), chose a startup over Twilio to help them grow, and underestimated long-term video storage costs. The vendor could not scale, so they re-engineered onto Twilio. Similarly, building subscription management in-house was 'a debacle' with every Apple/Google change, until they adopted RevenueCat. Integrations were designed to be swappable, which made switches possible.

What happened

Problems with the flagship feature; had to re-engineer onto Twilio. In-house subscription handling was abandoned for RevenueCat.
35:08
“And we had compared them to Twilio, and we decided we're going to go back with this new startup, and we're going to help them out, we're going to work with us and go forward. But the reality is they couldn't scale with us. And so we ended up making the transition to Twilio.”
Vince Mayfield
34:09
“We tried to build that ourselves, and it was a huge mistake. It was a debacle.”
Vince Mayfield

Related topics

Get tactics like this every Monday

New tactics from the week's founder interviews, each linked to where it was said.

More from this episode