Choose what to get done
Compute Viral Coefficient and Loop-Driven User Growth
A founder learns their viral K-factor and the cumulative users a seed cohort generates across viral cycles, so they can judge whether the product can grow on the viral engine alone.
Content distribution checklist
A deduplicated checklist of destinations (communities, forums, groups, syndication spots) to post your content to, each row with a destination name, a well-formed link, an accepted content format, and a posting cadence, spread across at least your minimum of distinct format types.
Core-capability gap register
A structured register comparing required capabilities to current capabilities, flagging each gap with a fill strategy.
Customer lifetime value (simple and discounted)
The customer lifetime in years, the simple LTV, and the discount-adjusted LTV you can put against CAC.
Customer profile
A ranked customer profile for one segment: the jobs your customer is trying to get done, the pains in their way, and the gains they want, every entry carrying a high, medium, or low rank so the profile states priorities instead of listing everything equally.
Cyclomatic complexity with refactor flags
McCabe cyclomatic complexity per function from its control-flow graph, with a refactor flag for any that exceed your threshold.
Decision-rights and single-threaded-owner register
Every critical decision and deliverable has exactly one named accountable owner, with advisers/consulted/informed parties and an escalation path explicitly recorded, eliminating diffused 'chicken' accountability.
Defect density per module with ranked hotspots
Defect density per module against your chosen size unit, the overall density, and a ranking of the most defect-dense modules.
Defect removal efficiency
Defect Removal Efficiency from pre-delivery vs escaped defect counts, with an optional per-phase breakdown.
Deploy pipeline and hosting
The app is deployed and the health endpoint returns 200.
Deploy runbook with rollback
An ordered, role-assigned deploy runbook with preflight checks, deploy steps, verification, and a rollback path that every failure step routes to.
Design a cheap parallel channel-test plan with pass/fail thresholds
I get a parallel channel-test plan where every test names one of the 19 canonical traction channels and carries a metric, a small budget, a duration, and a numeric pass threshold, so I can run several cheap experiments at once and read every result the same way.