Pricing your first product without a finance team

Business · 2026-05-21 · 9 min read · 1963 words

By ESPYCRUX, Studio

Most first prices are set by finding a competitor and picking a number nearby. That method quietly imports someone else's costs and someone else's customers. Here is how to arrive at a number from what you actually deliver, why the first one is a guess, and the mechanics of changing it later.

Pricing is the decision small teams put off longest, because it is the only one that cannot be made privately. You can rewrite the landing page at midnight and nobody notices. Publish a price and you have made a public claim about what your work is worth, and every change to it afterwards is public too.

So the number tends to get chosen badly — late, quickly, and by copying. What follows is how to arrive at one deliberately when nobody in the building has money as their job. It is reasoning rather than a track record; the section near the end says exactly what we have and have not done.

The two default methods, and why both fail

Cost-plus. Add up what it costs to run, add a margin, publish. This is how physical goods are priced and it is close to useless for software, because it captures the wrong costs. Your marginal cost of serving one more user is near zero, so the method produces an absurdly low number, and your real costs are months of work already spent, which are sunk. Worse, it makes price a function of your inefficiency: build slowly and badly, and the arithmetic says charge more. Nobody outside your company cares what it cost you to make.

Competitor-matching. Find the nearest comparable product, undercut it slightly, done. This is the more seductive error because it looks like research. It inherits two things belonging to somebody else.

Their cost structure is the first. A competitor charging $29 a month may carry a support team, a sales function, a compliance burden and investors expecting a growth rate. Their price is partly a description of those obligations, and copying its output without their inputs gives a number that says nothing about your business.

Their customers are the second. Price is a filter, and it sorts for a kind of buyer. A price set for procurement departments attracts people expecting invoicing, security questionnaires and a named contact. A price set for individuals attracts people who expect none of that and leave without ceremony. Match a competitor and you take on their customers' expectations without the apparatus to meet them.

Undercutting adds damage: a slightly cheaper version of an established product concedes that you are the same thing, then competes on the one axis where deeper pockets win.

Working from the value delivered instead

The usable question is not what it cost you or what they charge. It is: what does the person on the other side stop doing, or stop paying for, when they start paying you?

That is a substitution question, and it has a concrete answer. What are they doing instead — manually, in a spreadsheet, across three other tools, by paying somebody? How long does it take, and how often? What breaks when it goes wrong?

You do not need precise figures, only the shape of the answer. Something that saves a freelancer two hours a month is a different order of magnitude from something that prevents an error in a company's invoicing run. Those are not five per cent apart. Order of magnitude matters far more than digits, and value is the only one of the three methods that produces one.

One price cannot fit everyone. This is what tiers are for — not feature-hoarding, but recognising that the same tool is worth $5 to one buyer and $200 to another. Good tier boundaries track something that grows with the value received: seats, volume, environments. Bad ones withhold a feature that costs you nothing to provide, which reads as punitive.

Value framing points higher than instinct. A founder's first price is almost always low, because they are pricing against their own discomfort rather than the buyer's alternative. If the number is slightly uneasy to say out loud, you are probably close.

The first price is a hypothesis

Treat the first number as an experiment with a review date, not a commitment. Write the date down. That changes what you watch for: a price is not only revenue, it is an instrument that returns information, provided you can read what comes back.

The trap in the middle rows is treating price as the fix for everything. Most early silence is a distribution problem wearing a pricing costume, and cutting the price when nobody has heard of you turns one problem into two.

Raising a price later, mechanically

Founders postpone a needed increase for months because they imagine the reaction. It is almost always smaller than the anticipation, for a plain reason: a customer getting value compares the new price to their alternative, not to your old price. Only you are attached to the old number. The mechanics matter more than the message.

Grandfather existing customers, and say so first. They keep their current price; the new one applies to new signups. This single decision turns the email from bad news into an announcement, because for most recipients it contains no cost at all. It also repays early customers for the risk they took on an unproven product.

Give a date, not a vague warning. If you are moving existing customers too, name the billing cycle it takes effect from, give at least a full cycle, and make cancelling easy. Hiding the exit turns a price rise into a grievance.

State the price and the reason together, briefly. A paragraph on what the product now does that it did not before, one on the new price, one on what happens to them. Do not apologise. A long justification reads as guilt and invites a negotiation you did not offer.

Answer the replies individually. Some are cancellations you were going to get anyway; one or two are people for whom the increase is genuinely painful, and quietly keeping them at the old rate costs almost nothing.

Raise it before you desperately need to. An increase made from stability reads as confidence. The same increase made while visibly struggling reads as extracting money from the people who stayed.

Free tiers are a cost centre with a boundary problem

A free tier is not marketing that happens to be free. It costs infrastructure, support, the feature requests of people who will never pay, and the standing engineering tax of keeping a second product working.

Bound it on the axis that drives your costs — storage, compute, volume, retention — rather than on features, and decide in advance what it is for. There are two honest answers: a trial that converts, or a distribution channel that produces signups, links and word of mouth. If it is doing neither, it is not a strategy, it is a subsidy you forgot you were paying.

The bound has to exist from day one. Tightening a free tier later is unpopular in a way that raising a paid price is not: free users have agreed to nothing and owe you nothing, so a restriction lands as a broken promise rather than a commercial decision.

Charging early filters for real demand

Free things collect encouragement. People sign up, say kind things, and never think about the product again — none of it a lie, just cheap. Interest that costs nothing to express says nothing about whether the problem was ever painful. A payment, at any amount, is the first signal that survives contact with somebody's actual priorities.

It changes feedback too. A paying customer's complaint describes a real workflow. A free user's feature request is frequently a description of a product they would like to exist, not one they would use.

How profitability changes which decisions are available

Funding a business from its own revenue is not mainly ideological. Capital has become expensive, and a business that covers its costs keeps its options. What profitability changes is the set of decisions available to you.

None of these are about money directly. They are about who is entitled to an explanation from you, and every unprofitable month transfers a little of that entitlement to somebody else.

We think this is the right trade for a small team. But it is a trade: revenue-funded growth is slower, and being slower in a market where speed genuinely matters is a real way to lose.

What we have not done

We have not charged for anything.

Everything ESPYCRUX runs is free. The tools site is twenty-six utilities with no accounts, no paid tier and no upgrade path. The games are free to play. The blog is a blog. There is no billing system anywhere in the network, no pricing page, and no customer who has ever paid us.

That is deliberate, and it has a cost worth stating plainly: we have never received the one signal only a price produces. We have visit counts and people using things, and neither tells us what anyone would pay. The reasoning above about value framing, tier boundaries and the arithmetic of an increase is exactly that — reasoning, drawn from watching how it goes for others. We have not tested it.

The parts we would stand behind most firmly are structural rather than behavioural: that cost-plus measures the wrong thing, that a competitor's price encodes obligations you do not have, that an unbounded free tier is an unfunded liability, and that profitability changes who is owed an explanation. The parts about how customers react to an increase are secondhand, and you should weigh them accordingly.

A checklist before you set the first number

If you cannot answer one of these, that is the thing to go and find out.

1. What is the buyer doing instead? Name the alternative — a tool, a spreadsheet, a person, an afternoon. If there is none, they are not experiencing the problem.
2. What does that alternative cost them, in money or hours? An order of magnitude is enough.
3. Which axis does value scale on? Seats, volume, time saved, risk avoided. That is your tier boundary.
4. What are your fixed monthly costs? Not to set the price, but to know how many customers make you break even. That number should be small enough to say out loud.
5. Does the price make you slightly uncomfortable? If not, go up one increment.
6. If there is a free tier, what is it for and where does it stop? Write both down before launch.
7. When will you review this? Put a date in the calendar; ninety days is reasonable.
8. What would raise it, and what would lower it? Decide the triggers while you are calm, not in the week when sales are slow.

The first price will be wrong. That is fine, and far less consequential than the time usually spent avoiding it. What matters is that you can say where the number came from, and that you have already decided how you will change it.

Tags: pricing, business

ESPYCRUX — ESPYCRUX is a small product studio based in India, building focused web applications and writing about the engineering behind them. Articles are written by whoever did the work, and published under the studio name. Reach the studio at admin@espycrux.com.