How to price professional software - your buyer already has a price for this

At some point in every product build there is an afternoon where somebody has to type a number into a pricing page. Nothing in the preceding months prepares you for it. You have specifications, architecture decisions and user feedback, and then you have a blank field where the price goes, and the only honest answer to "how did you arrive at that?" is that it felt about right.

Most founders resolve that afternoon by picking a number they would feel comfortable defending, which is almost always too low. It is an expensive way to be modest. Every later decision inherits it - how much support you can afford, how fast you can develop, which customers you attract and how seriously they take you - and of all the things you can revise after launch, price is the one that costs you goodwill to change. Features can be added and onboarding can be rewritten. Telling a professional customer their renewal has gone up forty per cent is a different kind of conversation.

In this blog, Elliott Prince, Managing Director at Ferrous Labs, explains why the number you are looking for already exists before you set it, where to find it in your customer's business, and what the evidence actually says about pricing high.

Your buyer already has a price for this

The blank field is misleading, because it implies you are inventing something. You are not. Whatever problem your software solves, your customer is solving it today by some other means, and that means has a cost. They are paying for it in salaried hours, in rework when something is done wrong, in the senior person who checks the junior person's output, in the client work they turn down because capacity is spoken for. Nobody has written that figure down, which is why the problem feels unpriced. It is not unpriced. It is just unmeasured.

That distinction changes what kind of task this is. You are not searching your conscience for a defensible number; you are trying to establish one that already exists in somebody else's business, and then deciding what share of it is reasonable to ask for. The ceiling is the cost they carry today. Where you sit under that ceiling is a genuine commercial decision, and one you can make deliberately - but you cannot make it at all until you know roughly where the ceiling is.

This is also why professional buyers behave so differently from consumers, and why comparing yourself to consumer software pricing leads you astray within about a minute. A professional evaluating a tool is not asking whether it is cheap. They are asking whether it is cheaper than what they are doing now, and they can usually work that out, because their own time is already denominated in money.

Where to find the number they pay today

There are four places that cost tends to hide, and it is worth going after all of them, because most founders find only the first and price against a quarter of the real figure.

The most obvious is the manual process: the hours somebody spends doing by hand what your product would do. Count them honestly, including the checking, and put the fully loaded cost of that person against them rather than their salary. Then there is the software they already pay for and do not fit into, which is usually a subscription plus a set of workarounds that exist only to make it survivable; both halves are yours to displace. Third is the hire they would otherwise make, which is the comparison that most often gets your price accepted without much argument, because the alternative comes with recruitment, onboarding and employment risk attached.

The fourth is the one people skip, and it is frequently the largest: what going wrong costs them. In regulated or accredited work an error is not merely rework, it is exposure - a report that has to be reissued, a finding that has to be disclosed, a client relationship that becomes careful. You will not get a tidy number for this and you should not pretend to, but a customer who has lived through one of those incidents will supply a figure readily enough if you ask, and it will be larger than anything else on the list.

You find all four the same way, which is by asking customers what happens today rather than what they would pay. People are unreliable witnesses to their own willingness to pay and extremely reliable witnesses to how their week goes.

Does a premium price really signal quality?

Here is where I want to be careful, because there is a piece of received wisdom in this area that gets repeated more confidently than the evidence supports. The folklore says that a high price signals quality, so pricing low actively damages you by making buyers assume the product is flimsy.

The research is more equivocal. Völckner and Hofmann's meta-analysis in Marketing Letters, reviewing studies published between 1989 and 2006, found that the effect of price on perceived quality had weakened over that period, and that it was weaker still in three particular conditions: for services, for durable goods, and for respondents already familiar with the product category. Read that list against your own buyer. Software sold to specialists is service-like, bought repeatedly, by people who know the category extremely well. Those are close to the exact conditions under which the price-quality inference is least reliable, and the research is now old enough that the trend it identified has had another two decades to run.

So I would not price high in the hope that the number does your credibility work for you. What survives scrutiny is more prosaic and more useful. A low price constrains what you can afford to provide, and professional customers need responsive support and documentation rather more than consumer ones do. It constrains what you can afford to develop, which matters in fields where regulation and integrations move underneath you. And it shapes who arrives: a cheap tool attracts buyers who are shopping on price, which is a poor description of the customer you actually want and an accurate description of the customer who will cost you the most to support.

What to do with the number once you have it

Price against the value you can point at, not the cost of building the thing. Your development cost is a fact about you and of no interest whatsoever to a buyer weighing your product against a hire, and pricing off it produces the odd result that a product which was efficient to build must apparently be worth less.

Tiering works in professional markets when the tiers describe genuinely different customers rather than artificial restrictions on the same one: a sole practitioner really does need less than a twelve-person team, and a large business really does need permissions, audit trails and an invoice rather than a card payment. What does not work is removing something essential from the lower tier so it is unusable, because a professional buyer will read that correctly as a negotiating position rather than a product.

An annual option with a modest discount is worth having, and it is worth being clear about why: it suits how these businesses actually budget. A company that plans on an annual cycle finds a single line easier to approve than a recurring monthly one, so the discount is buying something real for both sides rather than simply lowering your price.

You are not setting a price, you are finding one

If pricing feels uncomfortable, that is usually a signal about the evidence rather than about your nerve. A founder who can describe precisely what the current process costs their customer does not agonise over the pricing page for an afternoon, because the range has already narrowed to something arguable. A founder who cannot is being asked to make an aesthetic judgement about their own worth, which is a miserable task and one nobody is good at.

So before you fill in the field, go and get the number. Three or four conversations with customers about what their week looks like, what it costs when the work has to be done twice, and what they would have to do if your product did not exist, will tell you more than any pricing framework. You will probably find that the figure is larger than you assumed, and that your instinct was to ask for a fraction of it.

That is worth knowing early, because the price is not just what you get paid. It decides what sort of company you can afford to be for the customers who trust you with the work.