Two proposals land on a founder's desk. Shop A: AED 180/hour. Shop B: AED 320/hour. Shop A wins the spreadsheet — then spends 2,000 hours not shipping. The cheapest hour in software is routinely the most expensive way to buy an outcome.
Why hours mislead
Hourly billing prices the input and leaves every risk with you: estimation risk, rework risk, the perverse incentive where slower work earns more. It also hides seniority games — the blended rate that quietly means juniors learning on your budget while a senior 'oversees'.
The questions that actually predict your outcome: What have you shipped that's still in production? Who exactly will build mine? What happens when scope changes? Show me a project that went wrong and what you did.
We don't sell hours. We sell shipped products that work in production.
What to demand instead
Fixed scope and price for definable work (our MVP Sprint runs AED 95k fixed); transparent re-scoping when reality moves; named senior engineers, not a bench; and references that include the project that went sideways. Any shop that's shipped enough has one — the tell is whether they'll discuss it.
When hourly is honest
Genuine exploration — embedded staff augmentation, research spikes, undefined maintenance — prices fairly by time. The dishonesty is hourly billing for outcomes that could have been scoped.
- Compare portfolios-in-production, not rate cards.
- Fix price on definable scope; re-scope openly when it moves.
- Ask who, by name, writes your code.