How should you price your first startup offer?
Define a specific customer, useful outcome, delivery scope, and cost before choosing a test price. Then offer that package to suitable buyers under clear terms and record what they do. Your first price is a commercial hypothesis you can revise with evidence.
The number on the page is only one part of the decision. A $300 service with unlimited revisions may be harder to deliver sustainably than a $150 service with a precise output and a predictable process. A low monthly software price can also become expensive to support when every customer requires individual setup.
Use this guide when: you can describe the problem and deliver something useful, but are unsure how to package and charge for it. Open the free first-offer pricing worksheet. It is an editable text template with no email requirement.
Write the offer in one paragraph
Complete this sentence: “For [specific buyer], we deliver [defined output or outcome] within [time window], using [required inputs], for [price and billing basis]. The scope includes [limits] and excludes [boundaries].”
Be careful with outcomes you do not control. You can promise a reviewed lead-follow-up workflow, a working integration, or a defined set of deliverables. Promising a particular sales increase requires evidence and control that an early offer often lacks.
Fictional example: a founder offers independent consultants a lead-follow-up setup: one pipeline, three approved email drafts, and a handoff session, delivered within seven business days after receiving the required access. Sending campaigns and ongoing optimization are separate. This is easier to evaluate than “AI growth transformation.”
Estimate the cost of keeping the promise
List setup, delivery, review, revisions, support, transaction costs, and any tools or model usage attributable to the customer. Count founder labor even when you do not yet draw a salary; otherwise your economics can look healthy only because your time is invisible.
Separate incremental delivery costs from business overhead. Rent, general administration, product development, and taxes still matter, even if they are outside the calculation below. A positive amount left after delivery costs is not the same as net profit.
| Fictional delivery item | Assumption | Estimated cost |
|---|---|---|
| Setup and delivery | 4 hours at an internal planning rate of $50 | $200 |
| Review and support | 1 hour at the same planning rate | $50 |
| Direct tool usage | Per engagement | $20 |
| Rework allowance | Expected average per engagement | $30 |
| Total before payment costs | Sum of the items above | $300 |
For illustration, suppose you want 40% of the sale remaining after these delivery costs and an assumed processing cost of 3% plus $0.30. The equation is price = ($300 + $0.30) ÷ (1 − 0.40 − 0.03), or approximately $526.84.
Those fees and targets are invented planning assumptions, not a provider quote or a recommended margin. At that price, the amount remaining is about $211 before overhead, taxes, and other costs. If delivery expands to ten hours, the economics change. Recalculate using your own actual terms and observed effort.
Check value and alternatives as well as cost
Your cost calculation tells you what the offer needs to support. It does not tell you what a customer will buy. Investigate the alternatives: doing nothing, using an existing tool, assigning an employee, hiring a freelancer, or buying a competing service.
Ask which consequence matters to the buyer and how they evaluate improvement. Hours saved can be meaningful without turning into an immediate cash saving. A founder who saves three hours may use them for other work; that does not automatically produce three hours of additional revenue.
Stripe’s guide to pricing new products distinguishes cost-based, competitive, and value-based approaches and recommends considering launch objectives, customer profile, and cost structure. For an early offer, use these as complementary questions rather than selecting a formula and treating it as proof of demand.
Choose a billing basis the buyer can understand
| Billing basis | Useful when | What to define clearly |
|---|---|---|
| Fixed project fee | The deliverable and boundaries are predictable | Inputs, revisions, acceptance, and change requests |
| Monthly subscription | Customers receive recurring access or ongoing value | Included usage, renewal, support, and cancellation |
| Usage-based charge | A measurable unit relates to customer value and costs | Unit definition, reporting, minimums, and spend controls |
| Paid pilot | Both sides need bounded learning before a larger commitment | Duration, deliverables, success review, and continuation terms |
Avoid adding three tiers just to make a pricing page look complete. Start with the smallest set of packages that corresponds to real differences in customer needs. If every buyer needs a custom quote, learn what creates that variation before standardizing it away.
Run a price test you can interpret
Write the package, price, audience, sales process, and review date before outreach. Keep a log of qualified conversations, proposals, purchases, reasons for declining, delivery effort, and requests outside scope. When the offer changes, record the version.
Small sequential tests can provide useful direction, but changing the price, audience, and pitch together makes the result ambiguous. A higher close rate may reflect warmer introductions rather than a better price. For a small sample, inspect individual decisions and objections instead of declaring statistical certainty.
An early-customer discount can be reasonable when its purpose, duration, and future price are explicit. Never present a fictitious original price or invent scarcity. If you exchange a discount for structured feedback, make the feedback expectation clear and allow honest criticism.
Diagnose the objection before cutting the price
“Too expensive” can mean the buyer lacks budget, does not trust the outcome, does not understand the scope, or has a cheaper satisfactory alternative. Ask what comparison or constraint is behind the answer.
If the problem is too small, a discount may not help. If delivery risk worries the buyer, a smaller paid engagement may be appropriate. If your economics require a price that the target audience cannot support, change the package, delivery model, or audience. The next decision should follow the evidence you collected.
Questions founders ask
Should the first customers get everything free?
Free trials can test use and learning. A paid offer tests a different commitment. Choose the arrangement that answers your current question, and describe any limits or future charges clearly.
When should I increase the price?
Review pricing when delivery costs, customer value, demand, or scope change. Honor existing commitments and communicate applicable changes before they take effect. One easy sale alone is not enough to explain what the whole market will support.
Does this calculation work for software?
The principle does, but the inputs differ. Account for hosting, model usage, onboarding, support, payment costs, and expected usage variation. Keep product-development spending and business overhead visible in the wider operating plan.
Make the next offer easier to evaluate
Open the pricing worksheet, write one package, and check its delivery assumptions. Then use the design-partner pilot guide to bound an early engagement or the channel guide to decide where to test it.
Shape your first offer
Get the worksheet now, plus the occasional practical next step by email. No spam, unsubscribe any time.
Need a little help applying this? Explore coaching and implementation.