Every framework here was rebuilt for one person, no team, and fewer customers than the textbook assumes — including the points where each one stops working.
SaaS frameworks were almost all written for companies with teams. The North Star metric assumes a product org. RICE assumes a backlog and a committee to score it. Value-metric guides assume a pricing analyst and a year of billing data.
Pick by bottleneck, not by curiosity. The selection table below tells you which one applies to the problem you have this week.
You have none of those inputs. You have one person, a handful of customers, and a decision you need to make this week. Every framework on this page has been rebuilt for that constraint.
Three failures repeat across nearly every framework written for funded teams.
They assume statistical volume. The Sean Ellis product-market fit test wants roughly 100 responses. With 14 customers the framework does not degrade gracefully — it produces a number that looks authoritative and means nothing.
They assume division of labour. Prioritisation frameworks exist to settle arguments between people who want different things. Alone, you are not resolving a conflict between departments. You are fighting your own preference for building over selling.
They assume parallel experiments. Channel frameworks tell you to test nineteen options and double down on the winner. You can test one at a time, and each test costs you a month.
A framework that ignores those three things gives confident answers to the wrong questions.
Every framework here sits inside one of five pillars. That structure is the Ghost OS, and it exists to answer one question: which decisions actually determine whether a solo subscription product makes money.
| Pillar | The decision it governs | Framework |
|---|---|---|
| Offer Architecture | What you sell, to whom, at what price | Positioning, pricing, value metric, PMF |
| AI Delivery Stack | How value gets delivered without you | Onboarding and activation |
| Acquisition System | Where customers repeatably come from | Channel selection |
| Automation Layer | What runs without your attention | Billing, trial follow-up, churn alerts |
| Revenue Protection | Whether the revenue you win stays | Churn diagnosis, trial conversion |
The order matters more than the contents. Founders who work pillar three before pillar one drive traffic to an offer that does not convert, then blame the channel.
This pillar holds the decisions with the widest reach. A pricing mistake compounds monthly against every customer you have and every customer you add.
Before any of that, it's worth checking the shape of the business itself. The business model canvas, honestly sorted argues four of the standard nine boxes are usually empty for a solo SaaS, and replaces them with four questions that actually apply at this scale.
The positioning framework comes first. Who this is for and what it replaces. Pricing decided before positioning is a guess wearing a spreadsheet.
The SaaS pricing framework covers method selection — cost-plus, competitor-anchored, or value-based — and when each is defensible. For running the actual numbers, use the guide to pricing a SaaS product. Before you commit to a number, it's worth researching willingness to pay directly — five methods, ranked by how much they cost to run. The Van Westendorp survey is the most commonly cited of the five, and also the one this site argues against running at solo scale.
The value metric framework answers a separate question: what unit you charge for. Most solo founders inherit per-seat pricing from software built for teams, then wonder why nobody ever expands.
The product-market fit framework tells you whether any of it is working, using signals that survive a sample size of twenty. It starts one step earlier than most founders realise: with the job your product is hired to do, and Mom Test interview questions that don't let a polite prospect lie to you about it. Once you have real signal, the Sean Ellis test at small scale turns it into a single number instead of a feeling — and once pricing method and value metric are set, how many pricing tiers you need is the decision most solo founders get wrong by defaulting to three.
Not sure which of the four applies to you? Marcus locates the bottleneck first, then gives one recommendation inside it.
Start free →Winning a customer and keeping one are different problems with different frameworks.
The onboarding framework covers the distance between signup and first useful outcome. For a solo founder that distance has to close without a human in the loop, because the human is you and you are asleep.
The churn reduction framework is diagnostic. It sorts churn into five types before you touch a fix, because the tactics that solve onboarding churn actively worsen price churn.
Knowing whether any of this is working starts with choosing a North Star metric — one number, not a dashboard. Below $10k MRR most of what gets tracked is noise; the four metrics that matter under $10k MRR narrows it to what's actually actionable. AARRR for one person gives the fuller funnel view when you need it — which stages to track, and which of the five to ignore entirely at your stage. The standard acquisition benchmark doesn't apply yet either — see why LTV:CAC misleads at solo scale. And with no team to split work across, prioritising features as a team of one needs a different method than RICE or ICE, both of which assume inputs a solo founder doesn't have.
Channel frameworks for funded companies assume parallel testing. The solo version assumes sequential testing and a much higher cost of being wrong.
The working rule: one channel, ninety days, one success metric defined before you start. Most solo founders run three channels badly instead of one properly, then conclude none of them work. Picking one channel and sticking to it is the framework behind that rule; the acquisition system guide covers building the channel once chosen. Before picking, it's worth understanding growth loops vs funnels as two different shapes a channel can take — most solo founders default to funnel thinking without realising a loop was available.
Work in bottleneck order. Find the first row that describes your business and start there.
| Symptom | Start with | Then |
|---|---|---|
| Visitors do not sign up | Positioning | Pricing method |
| Signups never activate | Onboarding | Trial conversion |
| Trials do not convert to paid | Pricing method | Value metric |
| Customers pay, then leave | Churn diagnosis | Onboarding |
| Nothing broken, nothing growing | Channel selection | Value metric |
| Unsure anyone wants this | Product-market fit | Customer interviews |
The common failure is starting at channel selection because acquisition feels like the growth problem. If the rows above it are broken, every new visitor leaks out of the same hole — you are paying to fill a bucket you have not patched.
A framework organises a decision. It does not make one.
Below roughly twenty customers most quantitative frameworks are theatre. You lack the data to populate them and the confidence they produce is false. At that stage, talking to eight customers beats scoring anything, and validating the idea matters more than optimising the model.
Frameworks also cannot choose between two defensible options. That is where a second perspective earns its place — and where an AI coach has real limits too.
Work in bottleneck order. If visitors do not sign up, start with positioning, then pricing method. If signups never activate, use an onboarding framework. If customers pay then leave, diagnose the churn type before applying any fix. Choosing a framework by curiosity rather than bottleneck is the most common mistake.
Most quantitative frameworks need volume solo founders do not have. Below roughly twenty customers, qualitative signals and direct customer interviews are more reliable than any scoring model. Frameworks become useful once you have enough data to populate them honestly.
A framework organises a decision — it tells you what the options are and how to choose between them. A playbook is a sequence of actions for a specific situation. Use a framework when you are stuck on what to do, and a playbook when you know what to do and need the order.
Ghost OS is a five-pillar framework covering offer architecture, AI delivery stack, acquisition system, automation layer, and revenue protection. It organises the five decisions that determine whether a solo subscription product generates revenue, and the pillars are worked in dependency order.
Pricing and positioning, by a wide margin. A pricing mistake compounds monthly against every existing customer and every future one, and most solo founders settle pricing in an afternoon. Onboarding and churn frameworks matter more once you are past roughly twenty customers.
Tell Marcus your product, your stage and where you are stuck. You get one specific recommendation for this week, not a reading list.
Try GhostCoach free →14-day free trial · cancel anytime · 30-day money-back on Lifetime