← BackRRelay
For teams
↗ Share
𝕏XinLinkedInWAWhatsApp
← Back to Discover
AI-seeded question · Simulated personaPublished seed batch · english_alignment_v1

No live Battle or provider API call was used for this content-only seed.

AI-seeded questionStartup & product

NehaGrowth Lead · 33 · BerlinSimulated persona · First growth hire

Our scheduling product has 500 company signups, 42% activation, and only 9% week-4 retention. Paid acquisition is still cheap, and our founder wants to scale it before competitors do. Should we keep buying growth or pause until retention improves?

Reasoning pattern: diagnosis before resource allocation

Relay AnswerEditorial synthesis · independent checking not run

Relay Answer

Pause broad acquisition, not all acquisition. A 9% week-4 rate means new volume will mostly buy faster leakage unless the retained 9% represents a valuable, repeatable segment. Keep a small diagnostic channel running, segment retention by use case and team type, and interview both retained and recently churned accounts around the moment value breaks. Set a retention or repeated-use gate before restoring spend. The exception is a narrow segment with clearly better retention and credible unit economics; acquisition there can continue while the core product is repaired.

Watch out

Aggregate retention may hide one healthy customer segment or a measurement window that does not match the product’s natural usage frequency.

What could change this answer

Cohort-level retention by use case, the true usage cadence, contribution margin, and evidence that a specific acquisition channel produces materially stronger retained users.

Disagreement preview

One view says cheap channels are temporary and should be captured now; another says acquisition before repeat value merely scales noise and obscures the product problem.

What all models may have missed

The team may be calling the wrong event ‘activation.’ Completing setup can look healthy while no user reaches the recurring job that actually predicts retention.

Full Battle

A full underlying Battle is intentionally not included in this content-only seed. Choose “Run with different AIs” to prepare the original question for Relay’s existing Battle flow.

Have a question like this?

Make Relay check your actual situation.

Help improve Relay with privacy-conscious analytics

With your permission, Relay records a small set of product events without question text, answer text, email, passwords, or session replay. Declining does not limit the product.

Privacy & analytics settings →