Skip to content

Entrepreneurship / Essay

Why we use fixed prices

An hourly rate rewards slowness. A fixed price rewards clarity. Why at Stoicera we owe a result, not hours.

The hourly meter creates a conflict of interest

When paid by the hour, I earn more from solving problems slowly. The client carries the risk and I carry none. This is so normal in software that it is rarely questioned.

At Stoicera we chose otherwise. We owe the deliverable, not time: scope, acceptance criteria and price are agreed before work starts. If I misjudge the effort, I bear the cost, not you.

What a fixed price really requires

A fixed price is a discipline, not a marketing promise. It requires three things that hourly work can treat as optional:

  • A clear initial conversation. I need to understand what will be built before quoting a price. Our first conversation is free because it is part of being precise, not a sales hour.
  • A written offer. Scope, timeline and acceptance criteria. What is written is delivered. Anything outside it is discussed beforehand, not billed afterwards.
  • The courage to say no. Some projects are not ready for a fixed price because their outcome is unclear. I say so, and we clarify the scope before starting a meter.

Why this matters for municipalities and businesses

For a municipal manager or executive, price comes first: which budget applies, who is responsible and is procurement needed? A fixed-price deliverable can be approved and accounted for. An open-ended hourly budget leaves only hope.

Another reason is less often stated: fixed pricing forces the provider to build simply. Bearing complexity’s risk discourages unnecessary complexity. Proven technology, clear scope and maintainable systems are practical necessities, because alternatives cost me money.

Not the cheapest

An honest fixed price is seldom the lowest, because it includes what an hourly rate conceals: responsibility for the outcome, warranty and subsequent operation. In return, the final number matches the initial one.

This is not revolutionary. It is the oldest craft model: agree on a work, deliver it and stand behind it. Software is no exception; it was just treated as one for a long time.

Related projects

MealTime (Schulmittag)

Read next

  1. Entrepreneurship / Essay / 3 min.

    A partnership starts with a shared task

    Reach, technology and expertise can complement each other. A lasting collaboration needs a shared result and clear contributions.

  2. Entrepreneurship / Essay / 3 min.

    Who builds, answers

    The sentence we work by, and what it costs. Responsibility in software, teaching and under your own name.

Quick access / The archive

Start here