Positioning Before You Have a Product: A Framework for Early-Stage Founders
The Problem with Traditional Positioning Frameworks
Most positioning frameworks assume you've already built something. April Dunford's Obviously Awesome — one of the best books on the subject — lays out a clear process: start with competitive alternatives, identify your unique attributes (features), map those to value (benefits), determine who cares most (target customers), and choose a market category that makes your value obvious.
It's a rigorous and effective framework. But it requires inputs that early-stage founders don't have.
You need existing customers to reference. You need features you can compare against competitors. You need enough traction to identify patterns in who loves your product and why.
If you're starting from zero — or starting from a gut feeling, some skills, and a vague sense of who you might want to serve — those inputs don't exist yet. And this creates a real gap. The founders who most need positioning clarity are the ones least equipped to use the frameworks designed to provide it.
Two Failure Modes
Without a workable early-stage positioning process, founders tend to fall into one of two traps.
Trap 1: Build first, position later. The founder has an idea — usually framed as a set of features — and goes straight to building. Months later they have a product but no clear articulation of who it's for, what problem it solves, or why anyone should care. They try to retrofit positioning onto something that was never grounded in customer understanding. This is the scenario Dunford's framework is designed to rescue, but by this point significant time and resources have been spent.
Trap 2: Analysis paralysis. The founder tries to do positioning work before building, but can't answer the fundamental questions. They don't have competitive alternatives to analyze because they haven't committed to a market. They don't have features to map because they haven't built anything. They don't have best-fit customers to study because they don't have customers. The positioning exercise stalls, and so does the business.
Both traps share a common root: the assumption that positioning starts with the product. It doesn't. For early-stage founders, positioning starts with the customer.
The Distribution Problem Comes First
There's an even more fundamental issue that traditional positioning frameworks don't address: distribution.
Before you worry about how to position your product, you need to answer a prior question — can you reach the customers you want to serve? A product built for a customer you can't reach is useless, no matter how well-positioned it is.
For established companies, distribution is largely solved. They have sales teams, marketing channels, brand recognition, and existing customer relationships. Positioning work happens in the context of distribution that already exists.
For early-stage founders, distribution is the first problem to solve. You don't have channels. You don't have an audience. You don't have a brand. You need to figure out how to get in front of the right people before anything else matters.
This is another reason the offer is the right starting point. An offer isn't just a positioning tool — it's a distribution test. When you write an offer and put it in front of people, you're testing two things simultaneously: does the message resonate (positioning), and can you actually reach people who care (distribution). If you run an ad and nobody clicks, it might be a messaging problem. But it might also be that you're in the wrong channel, targeting the wrong audience, or trying to reach people who simply aren't accessible to you.
A founder who discovers early that they can't reach their intended customer has learned something invaluable — before they've spent months building a product for an unreachable market.
A Different Starting Point: The Customer's Dream
Traditional positioning asks: "Given what we've built, how do we make its value obvious?"
Early-stage positioning should ask: "Given who we want to serve, what value can we deliver that moves them toward their dream?"
This reframe matters because it keeps the founder free. When you start with features and attributes, you're anchored to a specific product idea. You might reposition it, but you're still working within the constraints of what you've already built or imagined. This is Dunford's own critique of default positioning — founders get locked into an initial framing — but I'd argue that any process anchored to existing features carries this risk.
When you start with the customer, nothing is locked down. You're free to discover that the right product is a PDF, a webinar, a consulting engagement, a piece of software, or something you haven't imagined yet. The product format becomes a variable, not a given. It emerges from customer understanding rather than preceding it.
The concept I use with my clients is this: customers are always pursuing a dream — something they want, sometimes not fully rational or explainable, but real to them. Along the way, they encounter problems. Your job as an entrepreneur is to be a guide who helps smooth out those problems. You don't need to solve everything. Even helping a customer take one step closer to their dream has real value.
This framework has practical implications for product design. Tiny steps toward the dream command lower prices. Bigger steps command higher prices. A 3-page PDF and an expensive consulting engagement can address the same customer dream — they're just different-sized steps along the same path. And critically, they can use the same offer, because the offer is about the customer's problem and dream, not the delivery format.
The Offer as a Positioning Tool
This is where the methodology gets concrete. If you can't start with competitive alternatives, features, or existing customers — where do you actually start?
You start by writing an offer.
An offer is not a product description. It's an invitation. It says to a specific person: "You have this problem, I understand why it matters, and here's how I can help you take a step toward solving it."
Writing an offer forces you to make a series of decisions that traditional positioning frameworks arrive at much later in the process:
Who is this for? You can't write a compelling offer for "everyone." The act of writing forces specificity — a particular kind of person in a particular situation with a particular problem.
What value are you delivering? Not what features you're building, but what outcome the customer gets. What changes in their life or business after working with you?
Why should they trust you? What makes you a credible guide for this specific problem?
What's the next step? An offer has a call to action. It asks someone to do something — sign up, book a call, download, pay. This makes it testable in a way that a positioning statement is not.
Once the offer is written, you have something you can put in front of real people and measure their response. Do they click? Do they sign up? Do they say "yes, that's exactly my problem"? Or do they look confused?
This is where the offer does double duty. It tests your positioning — does the message resonate? — and it tests your distribution — can you actually reach the people who care? Both questions need answers before you invest in building a product.
A founder who runs an offer through LinkedIn ads and gets strong engagement from career counselors has learned that the message works and that LinkedIn is a viable channel for reaching that audience. A founder who gets zero response has learned something equally valuable — and can adjust the message, the channel, or the target customer before they've built anything.
The positioning elements that Dunford maps out — competitive alternatives, unique attributes, value themes, target customer characteristics, market category — all emerge through the process of writing and testing offers. You don't need to know them upfront. You discover them by doing.
Why Founders Get Stuck Writing Offers: The Feature-Benefit Problem
In practice, writing an offer is harder than it sounds. The most common failure mode I see is that founders write offers about their solution rather than about the customer's problem and desired outcome.
This is the feature-benefit gap. Founders — especially technical ones and creators — naturally think in features. They describe the process, the tools, the methodology, the technology. Because that's what they build. That's what they're close to. That's what they're proud of.
But customers don't buy features. They buy outcomes. They buy the feeling of a problem going away. They buy the promise of one step closer to their dream.
One of my clients, an AI expert with 3,000+ followers, kept writing offers about his AI image generation process. "Learn how to go from zero to one with AI." The problem was that his ideal customer — a business owner who needs on-brand promotional images — doesn't care about learning AI. They care about getting great-looking images quickly and easily. He was writing about the solution when he needed to be writing about the outcome.
This is not a surface-level copywriting issue. It reflects a fundamental orientation. The founder is facing inward — toward their product, their process, their expertise. The offer needs to face outward — toward the customer's world, the customer's problem, the customer's dream.
It typically takes multiple drafts and at least one real customer conversation before this reframe clicks. That's not a sign the process is broken. That's the process working.
The Offer Writing Process: A Four-Step Framework
Based on working with early-stage founders, I've developed a process for writing offers that addresses the feature-benefit gap head-on. The process has four steps, and it's designed to be cycled through multiple times — each pass creating tighter alignment between what you can do and what the customer needs.
Step 1: What Can You Do? (Features & Capabilities)
Start where founders naturally live. List everything your product or service could do. Features, capabilities, tools, processes, deliverables. Don't filter. Don't try to make it customer-facing yet. Just get the raw material on paper.
This step matters because it grounds the offer in reality. Skipping it leads to offers that sound great but promise things you can't deliver. Starting here ensures the offer is connected to your actual capabilities.
Step 2: So What? (Translate Features to Benefits)
For each feature, ask: "So what? What does this let the customer do, feel, or avoid?"
This is the translation layer that most founders skip. A feature is what the product does. A benefit is what the customer gets. They are not the same thing.
Some features will map to clear, compelling benefits. Others won't — and that's valuable information. It tells you which features actually matter to the customer and which are just things you find interesting or technically impressive.
A useful test: if you can't explain why a customer would care about a feature, it probably shouldn't be in the offer.
The "so what?" question can be laddered. The first answer is usually a functional benefit ("saves time"). Ask again and you get a deeper benefit ("lets you focus on the creative work you actually enjoy"). Ask again and you may reach the dream level ("you can run your business without feeling overwhelmed by production work"). The deeper you go, the more compelling the offer becomes — but every level must remain credible and connected to the feature you started with.
Step 3: Why Does This Matter? (Connect to the Customer's Dream)
Now zoom out. What is the overall problem or aspiration that ties these benefits together? What dream is the customer pursuing, and what's standing in their way?
This is where the offer gets its emotional power. You're not selling a list of benefits — you're telling the customer "I understand what you're trying to achieve and what's making it hard, and here's how I can help."
This step also serves as an alignment check. If your benefits (Step 2) don't connect to a coherent customer problem or dream, something is off. Either you're targeting the wrong customer, or your features don't actually serve the problem you think they serve. This is a signal to cycle back through earlier steps.
Step 4: Why You? (Credibility & Guide Positioning)
Finally, establish why you are a credible guide for this specific customer and this specific problem. What experience, expertise, results, or perspective makes you trustworthy?
This is not a general bio. It's a specific answer to the question: "Why should I believe that you can deliver what you're promising?" It should connect directly to the benefits and the customer's problem.
The Cycling Principle
These four steps are not strictly linear. In practice, founders cycle through them multiple times. You might start with features, realize the benefits don't map to a clear customer problem, go back and reconsider which features actually matter, re-map the benefits, and arrive at a tighter, more coherent offer.
Each pass creates more alignment between the layers. The cycling is not a sign of failure — it is the process. Typically it takes two to four cycles before all the pieces click into place. The moment of clarity often comes not from internal analysis but from putting the offer in front of a real customer and hearing their response.
Positioning Emerges from Offers, Not the Other Way Around
Here's the key insight that distinguishes this approach from traditional positioning frameworks: for early-stage founders, positioning is not an input to the process. It's an output.
You don't figure out your positioning and then write your offer. You write your offer — grounded in customer understanding and your real capabilities — and positioning emerges from the offers that work.
After testing multiple offers, you begin to see patterns. Certain types of customers respond most strongly. Certain benefits resonate more than others. Certain framings of the problem land better. Competitive alternatives become obvious because customers tell you what they were doing before they found you.
At that point — when you have real data from real offers tested with real people — traditional positioning frameworks become incredibly useful. You now have the inputs they require. You can map competitive alternatives, identify unique attributes, define your market category, and sharpen your positioning with precision.
But you had to start somewhere. And for founders starting from zero, the starting point is not the product. It's the customer, their dream, and an offer that invites them to take one step forward.
A Business Is Not a Single Product
One more insight that's worth capturing, because it changes how founders think about all of this.
Many founders think of a business as a single product. Find the right product and you win. Find the wrong one and you've wasted everything. This belief makes every decision feel enormous and every offer feel like a permanent commitment.
In reality, a business is positioned around a particular group of customers — not around a single product. A successful business has a collection of products at different price points, all serving the same group of people. Some products might be free — a blog post, a guide, a webinar — and their job is simply to get the customer in the door. Others might be premium services, software, or consulting that command real money.
The value of a business comes from the synergies that arise around this collection of products. Each product leads to the next. Each customer interaction deepens the relationship. Each offer teaches you more about what your customers need.
This means you don't need to find "the right product." You need to find the right customer — and then build a series of offers around their needs, starting with the smallest and simplest one. Each offer is an experiment that teaches you something. Over time, the experiments compound into a business.
The offer writing process described above is how you run those experiments. Write an offer, test it, learn from the response, write a better offer, test again. The business emerges from the accumulated learning, not from a single brilliant product idea.
Summary
For early-stage founders, the traditional positioning sequence — competitive alternatives → features → value → target customer → market category — requires inputs you don't have yet. And it skips the most fundamental question: can you reach the customers you want to serve?
An alternative approach:
Start with the customer. Understand their dream and the problems they encounter pursuing it.
Write an offer using the four-step process: features → benefits → customer dream/problem → why you. Cycle through these until they align.
Test the offer by putting it in front of real people — testing both the message (positioning) and the channel (distribution) simultaneously.
Let positioning emerge from the offers that work. When you have real data from real customers, apply traditional positioning frameworks to sharpen and scale.
The offer is the bridge between "I have skills and a vague idea" and "I have a positioned, testable business." It forces specificity, grounds the business in real capabilities, faces outward toward the customer, and produces something you can test immediately — for both market resonance and distribution viability.
You don't need a product to start positioning. You need a customer you can reach, a dream you can help with, and an offer that invites them to take the first step.
