GTM Sauce

Monarch Money · B2C · personal finance and budgeting app

Show clickable prototypes to the users who voted for a feature before building

Slower up front but fewer release cycles; founder's claim

Workedfeature-development

What they did

Every feature kickoff starts from customer input (interviews, surveys, roadmap comments), written as jobs to be done ('what am I hiring this feature to do?') and stack-ranked by the team. Then specs, designs and clickable prototypes, which are run by the customers who voted for that feature, iterating before code. Example: bill due dates, requested by ex-Mint users, turned out to serve people with ADD wanting one view and people making sure cash covers upcoming bills.

What happened

Takes longer up front but needs fewer post-launch iterations than ship-measure-repeat cycles of ~3 months each.
Stage
growth
16:50
“So we typically create clickable prototypes. And then we'll actually run those by the customers that voted on a particular feature.”
Val Agostino
17:11
“You know, honestly, it takes longer than probably the traditional approach, but we feel like you have to do fewer iterations.”
Val Agostino
15:57
“But also, another job to be done is ensuring that you have enough cash set aside to cover your upcoming bills, right?”
Val Agostino

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