Most software services firms bill by the hour. It is the default, it is simple to explain, and it feels fair: you pay for the time you use. We do not work that way, and the reason is not pricing preference. It is that the hourly model, looked at honestly, points the firm and the client in subtly opposite directions, and we would rather not build a business on that.
What hourly billing quietly rewards
Under hourly billing, the firm's revenue is the number of hours spent. State that plainly and the problem is visible: the firm is paid more when the work takes longer. Nobody has to be cynical for this to matter. It is just that every incentive the model creates, toward efficiency, automation, reuse, solving a problem in two hours instead of ten, reduces the firm's revenue. A firm can act against its own incentives through professionalism, and good ones do, but a model that requires people to constantly act against their own incentives is a badly designed model.
Hourly billing also makes the client the accountant. Every efficiency conversation becomes a billing conversation. The client ends up policing hours instead of judging outcomes, and the relationship acquires a low, permanent friction that has nothing to do with the work.
What a dedicated-team model changes
A dedicated-team model works differently. The client engages a team for a period, and that team is theirs: a known, stable group working on their system. The cost is the team, not the hour count.
This realigns the incentives. The firm is no longer paid by duration, so efficiency stops being self-harm. When the team finds a faster way, automates a task, or reuses something instead of rebuilding it, that is purely good: the same team delivers more within the same engagement. The firm benefits from being effective rather than from being slow.
It also changes the relationship. The conversation moves from "how many hours did this take" to "what did the team deliver this period." That is the conversation that should be happening. It is about outcomes, and it is one both sides can be on the same side of.
The other thing it changes: continuity
There is a second effect that matters as much as the incentives. An hourly model encourages treating people as interchangeable units of time, rotated in and out as utilisation demands. A dedicated team is stable. The same engineers stay with the system, accumulate knowledge of it, and are still there months later when something subtle needs to be understood. For a platform that a business operates for years, that continuity is not a luxury. It is most of the value.
The honest limits
A dedicated-team model is not right for every piece of work. A genuinely tiny, one-off task does not need a dedicated team, and we would not pretend otherwise. The model fits sustained work: an implementation, an ongoing operating relationship, a body of development that unfolds over time. For that, which is most of what serious systems need, it is the model whose incentives we are willing to stand behind.
The position, in one line
Billing by the hour pays a firm to be slow and turns the client into an auditor. A dedicated team is paid to be effective and judged on what it delivers. We chose the second because it is the one where doing good work and doing well are the same thing.