Handling project-based churn, MVP feedback strategy, and hiring thinkers

Executive overview

Project-based SaaS tools face structurally high churn that standard metrics penalise unfairly. Pricing model changes, audience sequencing for MVP feedback, and matching hire type to role complexity are the three core decisions covered.

Churn is a pricing design problem before it is a growth problem.

Project-based churn: pricing model options

• Annual-only pricing forces project users to pay for a full year — removes monthly churn as a metric
• Pay-as-you-go pricing works for irregular usage; price it 3–4x the monthly equivalent to compensate
• Student-specific pricing (e.g. flat annual fee) segments the high-churn cohort without penalising other users
• Segment churn into "project-based" vs "ongoing" buckets to see the real retention picture
• A perpetual licence only makes sense if the product runs locally without your servers
• High churn damages valuation in fundraising or acquisition conversations regardless of the reason

MVP feedback: sequence your audiences

• Start with the audience you already own — they know, like, and trust you
• Mixed feedback from different user segments creates conflicting signals and months of unclear priorities
• Individual coaches (ongoing seasons) and weekend camp coaches (one-off events) likely have different needs — don't conflate them
• Call it "early access", not "beta"; early access users can and should pay
• Low feature velocity (agency or freelancer dev) makes overwhelming feedback especially costly
• Get stable signal from one audience before expanding to the next

Idea theft: worry versus probability

• Idea theft at the concept stage is rare; copying accelerates once a product has visible traction
• Ideas morph substantially between inception and product-market fit — the early version is rarely worth stealing
• Going public with a landing page is a reasonable default; word-of-mouth-only validation is an option but not necessary
• Competition and copying are inevitable at scale — the question is whether the risk is worth the upside

Hiring: task-level vs project-level thinkers

• Individual contributors can often be task-level thinkers; managers and directors must be project-level
• VP and C-level roles require owner-level thinking — strategic horizon, not just project delivery
• Owner-level thinkers are expensive; bootstrappers often only access them via co-founder equity
• Job title signals the level: "director of X" implies project-level — the job description bullets must match
• Exceptional senior ICs combine technical skill with project-level thinking — rare and valuable