A Small Confusion That Costs Real Money
Ask an inventor who their product is for and the answer usually names one group: "parents of toddlers," "warehouse managers," "people with back pain." That answer collapses several distinct roles into one, and the collapse quietly breaks pricing, packaging, marketing spend, and sometimes the product itself.
The target audience is everyone the product is relevant to. The customer is the specific person or entity that hands over money. Those are frequently different people with different priorities, and the money follows the second one.
A concrete example. A pediatric asthma monitor: the user is a seven-year-old, the buyer is a parent, the decider is a pulmonologist who recommends it, and the payer is an insurer. Four parties, four sets of criteria. The child cares whether it is uncomfortable. The parent cares about anxiety and price. The doctor cares about clinical evidence and whether it generates useful data. The insurer cares about reduced emergency visits. Design and market to only one of them and the product stalls.
The Four Roles Around Every Product
- The user. Physically operates the product. Cares about comfort, ease, reliability, and whether it makes their day better. Determines whether the product is kept, recommended, and reordered.
- The buyer. Executes the transaction. Cares about price, availability, return policy, and how the purchase reflects on them. Determines whether the first sale happens at all.
- The decider. Approves or recommends. A procurement manager, a specifier, a clinician, a contractor, a teacher. Cares about risk, compliance, and precedent. Often invisible in consumer thinking and dominant in B2B.
- The payer. Provides the funds. An employer, an insurer, a grant, a landlord, a parent. Cares about total cost and measurable outcome.
In a simple consumer purchase all four can be the same person, which is why the distinction is easy to miss on a first product. In gifts, children's products, workplace tools, medical devices, and anything institutional, they diverge immediately.
Three Places the Distinction Decides the Outcome
Pricing. Price sensitivity belongs to the payer, not the user. A safety device an employer buys for a crew is evaluated against workers' compensation claims, and the acceptable price is an order of magnitude above what the same worker would pay personally. Selling to the payer's math rather than the user's wallet routinely triples the sustainable price, which is where the margin structures in how to price a product either work or do not.
Messaging and channel. The claim that sells and the claim that satisfies are rarely identical. A grip aid for arthritic hands sells on dignity and independence to the person buying it for a parent, but the user's actual criterion is whether it works with a wet hand at the sink. Both need to exist: the buyer-facing claim on the package and the ad, the user-facing performance in the product. Getting these backwards produces a product people buy once and never recommend, which is the worst commercial outcome available.
Product requirements. Features get specified for the person the team pictures. A commercial kitchen timer designed for the chef gets ignored by the owner who is buying on durability and warranty; designed only for the owner, it gets unplugged by the staff. The requirements document has to name which role each requirement serves, a discipline worth applying when working through how to validate a product idea.
How to Map It for Your Product
Three rules turn this from theory into a working method.
Write the four roles down explicitly. One page, four rows. For each: who they are, what they are actually optimizing for, what would make them say no, and what evidence would convince them. If a row is empty or vague, that is where your next customer conversation should go.
Talk to each role separately. Interviewing only users produces feature ideas and no revenue signal. Interviewing only buyers produces a product nobody enjoys using. In B2B the decider is the one most often skipped and the one most likely to kill a deal at the last step, which is why the stages in the B2B sales process for a physical product map to roles rather than to a single contact. Practical interview technique on a zero budget is covered in market research with no budget.
Follow the money to set priority. When roles conflict, and they will, the payer's objection is the one that stops the sale and the user's objection is the one that stops the second sale. Resolve payer objections in the pitch, user objections in the product. Never resolve a user objection by making the product cheaper to buy and worse to own.
Where Channel Partners Fit
Add a fifth role the moment you sell through anyone else. A distributor or retail buyer is a gatekeeper with their own criteria, and none of them are about how good your product is: margin, turn rate, packaging that survives a warehouse, case pack economics, return risk, and whether you can supply consistently. Founders who pitch retail buyers on product benefits and then lose the meeting are answering the wrong role's question. The structural differences between these partners are set out in sales rep vs distributor.
Personas, Used Correctly
The persona exercise gets a bad reputation because it is usually done as fiction: a name, a stock photo, and a list of hobbies that never informs a decision. A persona is useful only when it is built from actual interviews and only when it changes something specific.
Make one persona per role, not one per product, and keep each to five lines: what they are trying to accomplish, what they use today, what would make them switch, what would make them refuse, and where they can be reached. If a line does not change a design or marketing choice, delete it. Then test the reachability line before spending anything, because an audience you cannot address affordably is not a market. A landing page and a small ad budget answer that question in two weeks, using the method in landing page pre-orders as a demand test.
One caution on early input. Feedback from the wrong role is worse than no feedback, because it feels like validation. Friends who would use the product are not evidence that anyone will buy it, a trap examined in getting honest feedback on a product idea.
Get the Roles Straight Before You Build
Projects House works with inventors to separate user, buyer, decider, and payer early, then aligns requirements and pricing to each, before the money goes into tooling. Send your product idea and who you think it is for through our contact form.