Hiding the price feels safe. It postpones an awkward decision and keeps competitors guessing.
It also makes the buyer guess.
A price is part of the product. Ship it with the product.
Price the job, not the code
The customer does not care how many prompts, functions, or databases you used. They care what becomes faster, cheaper, safer, or newly possible.
Name the job. Estimate the present cost in time, money, delay, or risk. Put your price far enough below the value that the decision is intelligible, but high enough that serving the customer does not punish you.
Do not begin with a competitor’s three-column table. Their costs, customers, and strategy are not yours.
Start with one honest offer
Early products rarely need a maze of plans. One paid plan and, when useful, one limited way to try the product are enough.
State what is included, what is limited, when billing repeats, what happens at the limit, and how cancellation works. If the product requires a call or custom setup, say so before asking for an email.
Clarity filters users. That is a benefit. A visitor who cannot afford the product should learn that in thirty seconds, not after three meetings.
Charge earlier than feels comfortable
A compliment measures politeness. A payment measures priority.
You do not need a perfect billing system to test willingness to pay. For a small group, an invoice and manual onboarding may teach more than weeks spent building plan logic. What matters is that the terms are explicit and the work is real.
Ask what budget the customer uses today, who approves it, what they compare you with, and what would make renewal obvious. Avoid asking only, “What would you pay?” People are poor auctioneers of their own future behaviour.
Do not make “free” the default through fear
Free use can help when the product spreads through use, when marginal cost is tiny, or when a limited experience genuinely proves value. It can also fill your week with people who will never face the problem sharply enough to buy.
Use the free trial versus freemium guide to decide whether time, lasting capacity, or a paid pilot creates the most honest path from evaluation to payment.
Choose free because it serves the product, not because charging makes you nervous.
Test the whole promise
Before launch, complete a purchase on the public site. Read the receipt. Cancel. Request a refund. Hit a usage limit. Change plans. Check what support sees.
The pricing page, checkout, invoice, account screen, terms, and sales message should tell the same story. Contradictions look like tricks even when they began as stale copy.
Change it without drama
Your first price is a hypothesis. Record why you chose it, which customers saw it, and what happened. When evidence changes, revise it. Treat existing customers plainly and give notice where the change affects them.
The purpose of early pricing is not to discover the perfect number. It is to discover whether the product creates enough value for a business to stand on.