How to Price Your Product for the First Time

Define the customer and the thing you charge for

Before choosing an amount, decide what a customer is purchasing. Consider a tool that helps small businesses prepare quotes. You could charge per company, per user, per quote or according to the volume of work processed. You might also charge for initial setup if every customer needs help connecting data or configuring a workflow.

Each choice changes how customers experience the price. A per-user fee may be familiar but discourage a company from rolling the tool out widely. Usage pricing may reflect your costs but make the bill harder to predict. A flat subscription is easy to understand, yet heavy users may become expensive to serve.

Write down your initial logic: “We help [specific customer] achieve [specific outcome], and we charge per [unit] because it reflects [value received or cost of delivery].” If the sentence is difficult to complete, clarify the offer before refining the number.

Pricing belongs to the business model

The price affects more than revenue per sale. It shapes how you acquire customers, what support they expect and how much work you can afford to do for them. A low-cost monthly product is unlikely to support several sales meetings and a bespoke onboarding process unless another source of revenue covers that work. A large contract may allow for hands-on delivery, but it also requires a stronger case for purchase and often a longer buying process.

Consider how frequently the customer experiences the problem. A one-time outcome may suit a project fee or individual purchase. Continuing access or repeated value may suit a subscription. A digital product does not automatically need a monthly fee.

If the customer, problem and route to revenue are still unclear, start with the broader distinction explored in Having an Idea Is Not Having a Business. Price is one decision within the system that makes the offer viable.

Understand value without inventing a precise number

Find out what changes when the customer uses your product. Perhaps a task takes less time, errors fall, a team can act sooner or the customer can do something that was previously difficult. Those outcomes explain why a purchase might matter.

Be careful with simple value calculations. If your product saves four hours of administrative work each month, multiplying those hours by a wage does not automatically reveal what the customer will pay. They may not be able to recover that time, they may need to change an established process, or the person benefiting may not control the budget.

Ask about recent situations: when did the problem last occur, what did the customer do, what did it cost them and which alternatives have they tried? Identify the user, the buyer and anyone who can block a purchase. Good customer interviews give you context for the price conversation.

Customer value helps you understand what a buyer may accept. Your delivery costs tell you what the business needs. If you cannot find an offer that works on both sides, changing the final digit is unlikely to solve the underlying problem.

Compare the alternatives customers actually use

Your competitors include more than products with similar features. Customers may use a spreadsheet, pay a consultant, combine several tools or keep doing the work manually. They may also decide that solving the problem is not a priority.

When you compare prices, compare the complete offers. Note usage limits, seats, onboarding, support, integrations and contract terms. Two products advertised at the same monthly price can impose very different costs and commitments on a customer.

Look for the logic of each pricing structure. What causes the bill to rise? Which customers are likely to choose a higher tier? What objections appear when people consider switching? Competitor research gives you a reference point, not an instruction to undercut the cheapest option.

Work out what each customer costs to serve

A product can make sales and still lose money on the way it delivers them. Separate costs that grow with customers or usage from costs you incur regardless of monthly sales.

• Variable costs may include payment fees, infrastructure usage, external APIs or AI services, fulfilment and support that grows with customer activity.
• Fixed costs may include software, baseline infrastructure, salaries, a planned founder salary and administration.
• Acquisition costs include sales time, campaigns, commissions and other work required to win customers. Track them separately so you can see which routes to market are viable.

The price minus the variable cost of serving one customer is the contribution from that customer. It helps pay fixed costs and acquisition costs. It is not profit. Use consistent tax treatment in your calculations, and revisit the variable cost as usage grows.

A simple example: €29 versus €49 per month

Suppose a subscription product costs an average of €8 per customer each month to operate. Its monthly fixed costs are €4,100, including the planned founder salary. These are fictional numbers used to demonstrate the calculation.

Divide fixed costs by the contribution per customer and round up. At €29, 195 customers contribute €4,095, just short of the fixed costs. At €49, 100 customers contribute €4,100.

This does not prove that €49 is the right price. Perhaps the target customers will not buy at that level. The calculation also leaves out acquisition costs, failed payments and changes in usage. It does show what you need to investigate: can you win and retain 100 customers at €49, or 196 at €29? How much work will each customer require?

If your model only works when acquisition is free, support takes no time and every customer stays for years, revisit those assumptions before treating the price as viable.

Choose a pricing unit customers can understand

The amount customers pay should change in a way that feels connected to the value they receive, while remaining predictable enough for them to make a decision.

• One-time price: works for a defined deliverable or purchase. Specify the scope and any additional charges.
• Subscription: fits continuing access or recurring value. You will need to earn renewals, not just initial sales.
• Per user or team: can reflect adoption, but may discourage a customer from sharing the product across the organisation.
• Usage-based price: can align revenue with your costs and the customer's activity. Clear limits and visibility matter.
• Project or setup fee: can cover meaningful initial work and sit alongside a continuing fee.
• Outcome-based price: connects payment to a result, provided that both sides can define and measure that result fairly.

You do not need several tiers on day one. Start with a structure you can explain and deliver consistently. Add tiers when actual customer groups show different needs, usage patterns or service costs.

Make the first offer specific

A customer cannot assess an isolated number. Explain what the price includes, its limits, when payment starts and what happens if they need more. If you offer a trial, describe its duration and conditions. If setup requires significant work, make the one-time and recurring elements clear.

“€49 a month per company” still leaves questions unanswered. A useful offer explains what the company can do, who can use the product, what level of activity is included, what support is available and how the customer can change or cancel the plan.

A simple offer does not hide conditions. It lets someone understand the expected cost and decide whether the expected outcome is worth it.

Test the price through real buying decisions

“Would you pay €49?” can start a discussion, but a hypothetical answer is weak evidence. Present a specific offer when the customer can make an actual decision: a paid pilot, a preorder, an available first version or a proposal with defined terms.

Pay attention to the whole decision. Does the buyer understand the outcome? Can they approve the spend? Do they need an essential feature? Are they concerned about the price, the effort of switching or the risk that the product will not work for them? If they buy, do they use it and continue paying?

A refusal does not automatically mean the price is too high. Lowering the amount will not solve an unclear proposition, a missing integration or a problem the customer does not consider urgent. Ask what prevents the purchase before offering a discount.

If you compare two offers, keep track of which customers received each one and what was included. An offer with unlimited personal support is different from a self-service purchase at the same price. An introductory discount can help secure early customers, but it measures demand for that particular deal; you still need to learn what happens at the standard price.

Look beyond the first payment

A payment is a meaningful signal because it requires a real choice. It does not show, by itself, that the price works over time. Watch whether customers use the product, achieve the promised outcome, require more support than expected and renew or buy again.

For early sales, record the customer segment, offer, final price, objections, sales effort, delivery costs and subsequent use. Compare customers in similar circumstances. An independent professional and a large company might pay the same amount for very different reasons and require different levels of service.

Also examine who each offer attracts. A lower price may bring more sign-ups and heavier support demand. A higher price may produce fewer conversations but a clearer buying decision. Sales, usage and costs together tell you which pattern you can sustain.

Know when to revise the price

Revisit pricing when evidence changes your understanding of the customer, value or cost of delivery. You may find a segment that gets substantially more value, discover that onboarding takes longer than expected or see that some customers use far more resources than others.

Decide what actually needs changing. The answer might be a setup fee, different usage limits, a new customer segment, a clearer explanation or a different pricing unit. Raising or lowering the same number is only one possible response.

For existing customers, explain whom a change affects, when it takes effect, what the new offer includes and what options they have. The terms agreed with early buyers are part of the relationship you are building.

Common mistakes with a first price

• Copying a competitor: their costs, scale, customers and strategy may differ from yours.
• Stopping at cost plus a markup: costs matter, but you still need a customer who understands and values the offer.
• Charging less to avoid a difficult conversation: a low price may require more customers than you can realistically acquire and support.
• Pricing according to development effort alone: customers buy an expected outcome, not the hours already spent building the product.
• Confusing interest with willingness to pay: praise, sign-ups and requests for updates do not equal purchases.
• Forgetting sales and support time: a seemingly healthy margin can disappear when you account for the work each customer requires.
• Creating too many plans too early: tiers are useful when they reflect observed differences between customers.

Where Foundeia fits

Foundeia treats pricing as part of the business model, connected to the customer, value proposition, market alternatives and costs. Change one of those assumptions and the price may need another look.

The process continues beyond choosing a figure. The founder still needs to test the riskiest assumptions, decide what the MVP must include, present the offer during launch and review sales, usage and costs once the business is operating. Founder OS helps keep those decisions visible after launch. Foundeia can help structure the reasoning; customers provide the evidence through their purchasing and continued use.

If you are still deciding what to build, read about the minimum viable product. If you have an offer ready to sell, focus on finding your first customers and learning from the decisions they actually make.

Your first price should help you learn

You do not need a final answer before your first sale. You need a defined customer, a clear offer, a pricing unit you can explain and an economic model you can check. Then you need to see what happens when real people have the chance to buy.

Set a price that you can defend with what you currently know. Record the objections, purchases, usage, renewals and delivery work that follow. Those observations will tell you whether to change the amount, the offer, the customer you serve or the way you charge.