Pricing for Software House without Breaking the Margin

Pricing is where most software houses win or lose the game, and almost no one treats it with the seriousness it deserves. The owner sets an hourly rate based on what the competitor charges, multiplies it by an optimistic estimate and sends the proposal. When the project blows up, he discovers that he has been working for free since halfway through.

Price is not a table. It is an expression of how you understand your own business: how much it actually costs to deliver, how much risk you are absorbing and how much value you are generating for the customer. Making mistakes here doesn't show up right away. It appears at the end of the year, when you have made a lot of money and have nothing left.

I will break down the charging models and where each one protects or exposes you.

Before you model, know your real hourly cost

You can't price without knowing how much an hour of your operation costs, and almost every beginner calculates this wrong. He takes the developer's salary, divides it by the hours per month and finds the cost. It does not have.

The actual cost per hour includes what is not billable: meeting, rework, vacation, ramp-up, time between projects, your own management and selling time. It includes taxes, tools, infrastructure and the margin that sustains the company in the bad months. When you add it all up, the hour that seemed to cost a lot costs much more.

Without this number, any charging model is a guess. With it, you know the floor below which no project can go, and this in itself already avoids a large part of the losses.

Closed price: higher margin, higher risk

The closed price, in which you assume to deliver a scope for a defined value, is the model with the highest margin potential and the highest risk. If you deliver in less time than estimated, the gain is yours. If it explodes, so does the damage.

The problem with closed pricing isn't the price, it's the scope. It only works with a truly closed scope, and software scope is almost never truly closed in the beginning. The customer discovers what they want while watching the product be born, and each discovery is a change.

Therefore, a closed price requires two non-negotiable defenses. The first is a paid discovery phase before finalizing the construction price, because you cannot give full value to what you do not yet understand. The second is a clear scope change clause, which turns each change into a priced addendum rather than a favor. Without these two, closed pricing is a trap you set for yourself.

Time and allocated team: predictable, but with low ceiling

Charging by the hour or allocating a monthly team, the squad or body shop model, transfers the scope risk to the client. He pays for the time he consumes, so changing scope doesn't hurt his margin, it hurts his budget.

The advantage is cash predictability and simplicity of management. The customer knows how much they will spend per month, you know how much they will receive. For long relationships and continually evolving products, it is an honest and healthy model.

The downside is the ceiling. When you sell hours, your revenue is limited by the number of hours your team can produce, and your value is compared to that of any other hour seller. You compete on hourly rate, which is a race to the bottom. The model pays the bills, but it's rarely where the high margin lives.

Pricing value means selling results, not time

The most profitable model, and the most difficult to execute, is pricing by value. Here you don't charge for the hours you spend, you charge for a fraction of the value the software will generate for the customer.

The logic is simple to understand and uncomfortable to apply. If a system is going to save or generate a significant amount of money for the customer, the fair price has no relationship to how many hours it took you to build it. Two software houses can take very different times to deliver the same result, and the customer buys the result, not the effort.

To charge for value, you need to understand your client's business well enough to quantify the impact, and you need proof that you deliver these types of results. This is why value and positioning go together: only those who are recognized for generating it can charge for value. The generalist without proof is immediately arrested.

The clause that separates profit from loss

If I could change just one thing in the proposal of most software houses, it would be scope change management. This is where profitable projects turn into losses, regardless of the model chosen.

Open scope without clause is the silent margin killer. The client asks for an adjustment, you do it to maintain a good relationship, another comes along, you do it again, and the next thing you know, you've delivered a third more without charging anything. You didn't lose in a big negotiation, you lost in ten small kindnesses.

The solution is not to say no to changes, it is to price them. Every relevant change becomes an addendum with scope and price, approved before execution. This does not alienate the customer, it organizes the relationship. The serious client prefers predictability over surprise, and the clause gives predictability to both sides.

Readjustment and the courage to charge what it’s worth

Two last points that seem like details and are structural. Adjustment: a long contract without an annual adjustment clause silently erodes your margin, because your cost rises and your price is frozen. Leave the adjustment planned from the beginning, so you don't have to negotiate from scratch later.

And the courage to charge. Most software house owners charge below what they are worth due to insecurity, not strategy. They fear losing the customer on price, so they discount before even hearing an objection. This preventive discount is what destroys the margin of the entire sector.

Price is a conversation about value, not a number to defend. Those who understand their own costs, choose the right model for each project and protect the scope with a clear clause do not need to be the cheapest. It needs to be the most reliable, and trust pays better than discounts.

If you are reviewing your table or tired of closing a project that doesn't make a profit, it's also worth looking at how positioning and social proof change the price conversation. The other articles in this series cover this.