GTM Sauce

Once · B2C · disposable camera app for events

Don't write app code until 10 hosts commit to using it at a real, dated event

Got 12 events booked in one month, built the app, and hit $20K/month 83 days after launch

Workedvalidation

What they did

Define a 'commitment metric' for yourself and for users. For yourself: a specific date and a number (customers, clients, etc.) you must hit by then, so validation has a fixed time box. For users: the signal doesn't need to be payment, but must represent real usage; for Once it was event hosts agreeing to use the product at an actual dated event in front of friends and family, treated as nearly a proxy for payment. Their bar: 10 events with a real date and commitment before writing a single line of code.

What happened

Hit the bar (4 friends' events plus ~12 from cold outreach in a month), then built and launched; $20K monthly revenue 83 days after launch.
Stage
pre-launch
8:37
“Step one would be to define your commitment metric.”
Brian Shin
10:14
“For us internally, the goal was simple: before writing a single line of code, I needed 10 events with an actual date with an actual commitment that they would like to try using all the product.”
Brian Shin
“we thought that was already a big enough commitment that it was almost proxy to a payment.”
Brian Shin

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