GTM Sauce

Practitioner pattern · Thomas Petit (Sells consulting services and runs a paid signal-engineering workshop at App Growth Annual; works with Voyantis)

Report each user's expected value at month 13, not what they paid on day one

Guest's main advanced lever; no numbers given

Workedanalytics-attributionpaid-social

What they did

Default SDK revenue for subscriptions is wrong: trial conversions arrive too late and yearly plans look better than weekly ones that renew for months. Instead send an engineered value per user: predicted value at a fixed day (guest likes month 13, which includes the first yearly renewal and compares monthly vs yearly fairly), set by plan, device, onboarding answers, refund-risk behavior and so on. Find the value drivers with a regression over high/low/zero-value users. Skip this if revenue has little variance across users; go straight to it if variance is extreme (e.g. $1 IAP vs $20/month vs $200/month users).

What happened

Guest says all sophisticated signal engineering happens at the revenue level; no numbers.
50:15
“So, it's not a predicted LTV, is a predicted value at day X, maybe it's month two, maybe it's Personally, I like to use month 13, because I've got the first yearly renewal, and I think it's a better comparison between monthly and yearly.”
Thomas Petit
51:14
“Typically, platforms are going to over-index on yearly because all the revenue comes on day one, but maybe your weekly plan has a higher LTV when people renew a lot.”
Thomas Petit

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