The deliberate decision about what your product is, who it's for, and why someone should pick it over the alternatives — made visible on your homepage, not hidden in a deck.
Research-based overview. This article synthesizes April Dunford's positioning framework, public homepage examples, and patterns we've seen across solo SaaS launches. How we research.
The cleanest definition of positioning comes from April Dunford's 2019 book Obviously Awesome, where she argues that positioning is not branding, not messaging, and not a tagline. It is the strategic decision about what your product is — what category it competes in, who it's best for, and what unique value it delivers — and everything else (your homepage, your ads, your demo) is just an expression of that decision. Dunford breaks the work into a 5+1 components framework: competitive alternatives, unique attributes, value, target customer characteristics, market category, and (the +1) relevant trends. Get those right and your messaging writes itself; get them wrong and no amount of clever copy will save you.
For a solo SaaS founder this matters because you cannot brute-force distribution. You don't have a sales team to qualify leads or a marketing budget to repeat the message until it lands. The homepage has to do the qualifying for you, in the first scroll, with no help. That's a positioning problem before it's a copywriting problem.
You can ship a product without positioning. You probably already have. The MVP exists, a few friends use it, the homepage says "the easiest way to manage your X" in 48px text and you call it done. Revenue trickles in from people who already knew what they wanted. The product works.
What you cannot do without positioning is scale — meaning, sell to anyone who didn't already know what they were looking for. Cold visitors hit your homepage, fail to map your product to a problem they recognize, and bounce. Conversion rates stay below 1%. You assume the problem is the headline, you A/B test verbs, and the needle doesn't move. The problem isn't the headline. The problem is that you never decided what you were.
This is why most solo founders confront positioning around the same time: somewhere between $1,000 and $5,000 in MRR, when growth flattens and the next 100 customers don't come in by accident. At that point, the founder either does the positioning work and breaks through, or stays at that revenue level for two years and quits.
Dunford's framework only makes sense in context. Let's apply it to a fictional — but plausible — solo SaaS: a CRM built specifically for yoga studios. Call it StudioFlow. Most generic CRMs (HubSpot, Pipedrive) work for yoga studios in theory. None of them are designed around the specific workflow: members on monthly memberships, drop-in students, intro pack conversions, teacher payroll, weather-cancelled classes. StudioFlow exists because of that gap.
Not just the obvious competitors. Dunford asks: what would the customer use if you didn't exist? For StudioFlow, the alternatives are: a generic CRM like HubSpot (overkill, doesn't know what a class pack is), a class-booking tool like Mindbody (industry-specific but not CRM-shaped), a spreadsheet (free, what most studios actually use), or a paper appointment book (still common at single-owner studios). Each alternative has weaknesses, and your unique attributes have to map to those weaknesses.
Features your alternatives don't have. For StudioFlow: native concept of class packs and unlimited memberships, automatic intro-pack-to-membership conversion sequences, teacher-payroll calculation built in, weather-cancellation member-credit automation. Each one is a thing you have that HubSpot and Mindbody don't.
Why the unique attributes matter to the customer. The class-pack-to-membership conversion sequence might add 12% to a studio's monthly recurring revenue because it catches drop-offs that a generic CRM never sees. The teacher-payroll feature saves the owner four hours a month. These are the value points; the unique attributes are how you deliver them.
Not "yoga studios" broadly. Specifically: independently-owned studios with 1–3 locations, between 100 and 800 active members, where the owner is also a teacher and runs the back office. That description excludes corporate gym chains (too big), home practitioners (no business), and Mindbody power users (already locked in). The exclusion is the whole point — you're telling the wrong customer that you're not for them, so the right customer immediately knows you are.
The category frames everything that follows. "CRM for yoga studios" positions you against HubSpot. "Studio operations platform" positions you against Mindbody. The choice changes the comparison the buyer runs in their head, and therefore changes which features matter. For StudioFlow, "the CRM built for independent yoga studios" is sharper than "studio software" because it specifies what kind of software and for whom. Picking your category is the highest-leverage positioning decision; everything else flows from it. Our piece on when to niche down vs broaden covers when to lean harder into category specificity.
Why now? For StudioFlow: post-2024 boutique fitness rebound, the rise of small-studio independence after Mindbody's 2023 price hike, the AI-cancellation prevention trend in fitness. Trends are the "why this product, why this year" layer that makes the product feel inevitable rather than arbitrary.
Founders treat positioning as an internal artifact — a one-pager, a deck, a Notion doc. It's not. Dunford is explicit: positioning is invisible to your customer if it doesn't make it onto the homepage, into the demo, into the pricing page. The point of doing the work is to change the visible surface of your product.
For StudioFlow, here's how the framework translates to a homepage:
If your homepage doesn't name a target customer specifically enough that someone outside the target self-selects out, you have a positioning problem, not a copy problem. April Dunford's site has worked examples; her book Obviously Awesome is the canonical reference.
Across hundreds of indie SaaS launches, three positioning patterns recur because they're defensible without a marketing budget.
Pick a vertical or use case so narrow that incumbents can't economically chase it. StudioFlow above is this pattern. The niche has to be (a) large enough to support the business you want, (b) small enough that HubSpot won't build it, and (c) painful enough that the customer will pay above-average rates. Pattern 1 works because Dunford's research shows that buyers value specificity: a tool built for them beats a general tool with their use case as one tab.
Take a position on how the work should be done that's explicitly different from the dominant alternative. Linear took the position that project management should be fast and keyboard-driven, against Jira's slow web UI. Plausible took the position that analytics should be cookieless and privacy-first, against Google Analytics. The product's shape comes from the stance; the marketing writes itself because the customer either agrees with the stance or doesn't. Solo founders can take stances larger companies can't because there's no internal politics to dilute the message.
Position around the tool you live inside. A Notion AI summarizer, a Slack standup bot, a Linear sprint reporter. The integration is the category. You inherit distribution from the parent platform, and your unique value is "the best [thing] for [platform]." This pattern has a ceiling — the parent platform can clone you — but it gets to first revenue fastest. Several products in our micro SaaS examples roundup follow this pattern.
Here's the part founders miss: when you change positioning, the product mostly stays the same. The code doesn't change. The features don't change. What changes is the homepage, the pricing page copy, the target customer you spend acquisition dollars on, and which features you prioritize on the roadmap going forward.
If StudioFlow above started as "a CRM for boutique fitness" and got 5% conversion, it could reposition to "the CRM for independent yoga studios" without writing any new code. Same product, sharper position, narrower target, higher conversion among the people the homepage now speaks to. The cost is the people who would've bought the broader version — pilates studios, barre studios — but that loss is usually smaller than the gain from the sharper message.
Repositioning is high-leverage precisely because it's cheap. A week of work on the homepage, pricing page, and onboarding can move conversion from 1% to 4% on the same traffic. Compare that to the cost of finding 4x more traffic. The single most common positioning move we see solo founders make in their first two years: starting broad ("the easiest CRM") and narrowing to a vertical ("the CRM for yoga studios") once they see which customers stick around. That signal — which customers retain — is also a useful proxy for product-market fit.
The watch-out: don't reposition more than once a year. Each repositioning resets your SEO, your inbound link equity, and your customer's mental model of you. Pick a position, run it for at least 12 months, measure conversion and retention, and only then reposition if the data demands it. Founders who reposition every quarter never give any single position enough time to compound. For more on translating positioning into ongoing distribution, see our solo founder content marketing playbook.
SaaS positioning is the strategic decision — using Dunford's 5+1 framework: competitive alternatives, unique attributes, value, target customer, market category, trends — about what your product is and who it's for. For solo founders, it's the thing that turns a working product into a product that grows from cold traffic. The work is mostly cheap (a week of homepage rewrites, not a quarter of engineering), but the leverage is enormous: the same product can convert 4x better with sharper positioning. Read Dunford's book, do the 5+1 worksheet on your own product, and ship a homepage that speaks to one specific customer rather than everyone.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.