Techbanq

Cost guide · engineering capacity

Nobody buys hours. You buy delivered features

Two suppliers at the same rate can differ by a factor of two on cost per delivered feature. The difference is in review overhead, rework, turnover and how long a decision takes to reach the team — and only the first of those is anybody's fault.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
CTO, CIO
Decision
Build a defensible cost model for offshore engineering capacity
Languages
EN · AR

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The model

Six terms, and which way each one moves

A quote that mentions only the first term is not wrong; it is incomplete in a direction that flatters it.

VariableEffect on priceWhy
The rateThe visible termVaries by seniority and location and is the easiest thing to compare, which is why it dominates conversations it should not. Treat it as the starting point of a model rather than the answer.
Management overhead on your sideFrequently underestimatedA product owner, a technical lead reviewing, and the meetings. On a small augmentation arrangement this is easily a fifth of the value of the contract, and it comes out of your senior people's week rather than out of a budget line.
ReworkThe largest hidden termWork built against a misunderstood requirement is paid for twice. It is a function of decision latency and specification quality far more than of engineering skill, which is why the fix is usually on the buying side.
Turnover and onboardingCompounds quietlyEvery departure costs the notice period, the handover and the ramp-up of a replacement. Named individuals with notice periods and a supplier with low attrition are worth a premium on the rate, and the premium is smaller than one unplanned replacement.
Decision latencyA tax on the whole contractA team waiting two days for an answer delivers at a fraction of its capacity, and you pay for the waiting. This is the term most within your control and the one least often measured.
What you keep at the endDecides the second yearDocumented, tested code with the IP assigned to you is an asset. An undocumented system only the supplier understands is a subscription you did not know you signed, and the cost appears when you try to change supplier.

Ask any supplier quoting this

  • What management effort do you assume from our side, in hours per week?
  • What has your attrition been on engagements of this length?
  • Are these named individuals with notice periods, or allocated capacity?
  • What documentation exists on the day the contract ends?

Comparing markets

Compare structure, not stereotypes

Comparisons between offshore markets usually turn into claims about the quality of a country's engineers, which is neither measurable nor true in the aggregate. The properties that do differ structurally are worth comparing: time-zone overlap with your working day, notice-period norms, how contracting and IP assignment work, travel practicality, and the depth of the local market for the specific skills you need.

On those grounds Pakistan is close to the Gulf on time zone and travel, and the working weeks are broadly compatible. Other markets are stronger on other dimensions. The right comparison is against your own constraints, and any supplier presenting a table where their own market wins every row has written marketing rather than analysis.

Budget failures

Three ways the model comes apart

  1. 01

    The overhead was not budgeted

    The contract is approved and the product owner is nobody's day job. Delivery halves, and the conclusion drawn is usually about the supplier rather than about the missing role.

  2. 02

    Cheapest rate, highest total

    A rate discount that comes with junior staff, no review culture and high attrition costs more per delivered feature. The measure to hold is cost per feature over a quarter, not cost per hour.

  3. 03

    Nothing was documented

    The engagement ends and the knowledge leaves with it. Documentation written during delivery costs a few per cent; reconstructed afterwards it costs a project.

Our role

What we put in a proposal

  1. 01

    The overhead, stated

    How many hours a week we assume from your product owner and technical lead, so the number is in the business case rather than discovered in month two.

  2. 02

    Named people and notice periods

    With attrition history available on request, because turnover is a cost term and it belongs in the comparison.

  3. 03

    What exists on the last day

    Documentation standard, IP assignment on creation, and repository access — specified in the contract rather than assumed.

Whether the model is affordable is your finance function's decision; what we owe them is a proposal with the terms they will be asked about already in it.

Common questions

What buyers ask

Can you give a rate before scoping?+

We can give a rate range by seniority in a first conversation, and it will tell you very little. The number worth having is cost per delivered feature over a quarter, and producing that requires knowing what the work is and how quickly your side can answer questions. Both are knowable in a fortnight.

How does this compare with hiring locally?+

Locally hired engineers carry no coordination overhead and are the right answer for roles that need to sit with the business. Offshore capacity is the right answer for scale and for skills that are scarce or expensive to hold permanently. Most organisations that get this right run both, and decide role by role rather than as a policy.

What is the minimum engagement that makes sense?+

Below about three months, onboarding dominates and nobody gets value — the team spends the first weeks learning a system and leaves as it becomes productive. Short pieces of work are better served by a fixed-scope engagement with a specification than by capacity.

Build the cost model with your numbers

A cost model built with your own numbers — including the overhead your team will actually carry — rather than a rate compared against a market average.

Start the conversation