Master Scorecard

Every feature in GrowthOS is scored on four dimensions before it earns a place on the roadmap. This is the complete, unedited scorecard — 36 features we build and 13 we killed.

Scoring Framework

Dimension	Scale	Definition
Pain Severity	1–5	How much does the absence hurt indie/small SaaS teams? (5 = losing money)
Revenue Proximity	1–5	Direct willingness to pay? (5 = clearly monetizable)
Build Complexity	1–5	Engineering effort — inverted: 5 = easy/fast, 1 = months of work
Moat / Defensibility	1–5	Can a competitor clone it quickly? (5 = network effects / data moat)

Maximum score: 20/20.

Phase Assignment Thresholds

Score Range	Assignment
≥ 15/20	Phase 1 — Minimum Lovable Product
12–14/20	Phase 2 — Growth Engine
10–11/20	Phase 3 — Scale & Sophistication
≤ 9/20	Kill / Park

Phase 1 — Minimum Lovable Product

Months 1–4 | Score threshold: ≥ 15/20

#	Feature	Pain	Revenue	Build	Moat	Total
P1-01	Unified Contact Graph	4	3	4	5	16
P1-02	Referral Engine	5	5	4	4	18
P1-03	Lifecycle Emails	5	4	4	4	17
P1-04	Viral Waitlist	4	4	4	4	16
P1-05	Surveys & NPS	5	4	4	4	17

Phase 2 — Growth Engine

Months 5–9 | Score threshold: 12–14/20

#	Feature	Pain	Revenue	Build	Moat	Total
P2-06	Segment Builder	4	3	4	3	14
P2-07	Gated Content	3	4	4	3	14
P2-08	Onboarding Checklist	3	3	4	3	13
P2-09	UTM Attribution	4	3	4	3	14
P2-10	Broadcast Emails	4	4	3	3	14
P2-11	Coupon Engine	3	4	4	3	14
P2-12	Webhook Engine	3	3	4	3	13
P2-13	Employee Amplification	3	4	4	3	14
P2-14	In-App Nudges	3	3	4	3	13
P2-15	Review Prompts	3	4	4	3	14
P2-16	Tiered Referrals	4	4	4	4	16
P2-17	Welcome Sequences	3	3	4	3	13
P2-18	Contact Scoring	3	3	4	3	13
P2-31	Stripe Integration	4	4	3	3	14

Phase 3 — Scale & Sophistication

Months 10–15 | Score threshold: 10–11/20

#	Feature	Pain	Revenue	Build	Moat	Total
P3-19	Social Proof Widget	3	2	4	2	11
P3-20	Cohort Analytics	3	3	3	3	12
P3-21	A/B Testing	3	3	3	3	12
P3-22	Journey Builder	4	4	2	3	13
P3-23	WhatsApp	4	4	2	3	13
P3-24	SMS	3	3	3	2	11
P3-25	Push Notifications	3	3	3	2	11
P3-26	Milestone Cards	2	3	4	2	11
P3-27	Ambassador Program	3	4	3	2	12
P3-28	Testimonial Collector	2	3	4	2	11
P3-29	Landing Pages	2	3	2	3	10
P3-30	Upgrade Prompts	4	5	3	3	13
P3-32	Slack Integration	3	3	4	2	12

Phase 4 — AI Layer

Months 16–20 | Strategic AI features

#	Feature	Pain	Revenue	Build	Moat	Total
P4-33	Send-Time Optimization	3	3	2	3	11
P4-34	Churn Prediction	3	3	2	2	10
P4-35	Auto-Generated Copy	2	2	3	2	9
P4-36	Module Recommendations	2	2	2	2	8

Killed Features

Score ≤ 10/20 — better served by existing tools or webhook integrations

#	Feature	Score	Killed Reason
K-37	Paywalled Feature Gates	10	Stripe + PostHog handle this; too risky in auth layer
K-38	Pricing Page Experiments	7	PostHog experiments already superior
K-39	Community Hub	6	Discourse is free and mature; webhook instead
K-40	Contact Sync & Discovery	9	Privacy/GDPR/DPDPA complexity; wrong audience
K-41	Interactive Product Tours	8	Appcues territory; In-App Nudges covers 80%
K-42	Changelog / What’s New	9	LaunchNotes/Beamer; content, not growth engine
K-43	Gamification	8	Consumer pattern, not B2B SaaS
K-44	Event / Webinar Engine	8	Luma/Zoom own this; webhook instead
K-45	Missed-Call-to-WhatsApp	10	India-specific; webhook enables it
K-46	QR Code Engine	9	Commoditized, zero moat
K-47	Link-in-Bio Page	8	Linktree ($5/mo); no pain, no moat
K-48	Contest / Giveaway Engine	8	Ephemeral, not recurring infrastructure
K-49	Magic Link / Passwordless Auth	8	Auth is tenant’s job; Clerk/Auth0/Firebase

For detailed rationale on each killed feature, see Discounted Ideas.

Score Distribution

How to Read This Scorecard

High Pain + High Revenue = Painkiller. Build first. (Phase 1)
Medium Pain + Medium Revenue = Growth Engine. Build when foundation is solid. (Phase 2)
Low Pain + High Moat = Platform play. Build for defensibility. (Phase 3)
Low Pain + Data-dependent = AI Layer. Build when data exists. (Phase 4)
Low everything = Kill. Integrate via webhook if needed.