Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Technology Buying Guides 6 min read

Custom software cost planning models compared

Fixed price, time and materials, capped T&M, stage-gated milestones and a dedicated product team compared on budget certainty, change handling and the behaviour each model rewards.

E
EncryptTechBD · 0 comments
Close-up of a computer processor chip
Photo: Tim Sullivan / StockSnap

A custom software budget is not only a number. It is an agreement about who carries the risk when the number changes. A fixed price transfers more risk to the vendor, who then prices it in. Time and materials leave the risk with the buyer, who gains flexibility. Neither is honest or dishonest. They are different instruments, and they fail when used for the wrong job.

This comparison sets out five commercial models used for custom software in Bangladesh and elsewhere, the criteria that distinguish them, and the situations where each one is the better choice. It also covers the estimation methods underneath, because a model cannot rescue an estimate built on optimism.

Six criteria for comparing models

  • Scope certainty: how well the requirement can be described before work starts.
  • Budget predictability: how much the final number can move without a renegotiation.
  • Change handling: the cost and speed of adjusting course when learning changes the plan.
  • Vendor incentive: what the contract rewards: finishing early, adding scope or extending time.
  • Governance overhead: the meetings, documents and approvals needed to keep the model working.
  • Exit and ownership: what the buyer keeps if the relationship ends.

The five models at a glance

ModelBest fitStrengthsLimitsMain risk
Fixed priceStable, well-specified delivery with a known scopeBudget certainty, simple approvalChanges are expensive, specification disputesVendor prices in uncertainty or cuts quality
Time and materialsDiscovery-heavy or evolving product workFlexibility, transparent effortBudget can drift without disciplineBuyer carries all scope risk
Capped time and materialsDefined phase with expected changeFlexibility inside a ceilingCeiling may be hit before valueWork stops mid-outcome when the cap is reached
Stage-gated milestonesMulti-phase delivery with decision pointsFunding follows evidenceMore administration, slower startsGates become paperwork rather than decisions
Dedicated product teamOngoing product development and maintenanceContinuity, fast iteration, shared contextRequires strong internal product ownershipRetainer becomes a standing cost with weak output

Fixed price

The vendor commits to deliver a defined scope for a defined amount. It works when the requirement is stable, the acceptance criteria are testable and both sides accept that changes will be handled through a formal variation.

Choose it when you are buying a well-understood system, a migration or a defined integration, and the specification can survive a review by someone who did not write it. Watch for a low bid that assumes the cheapest interpretation of every ambiguous line. The cheapest fixed price is often the one with the most exclusions.

Time and materials

The buyer pays for actual effort at agreed rates. The model suits discovery, design and product work where the next month depends on what was learned in the last one.

Choose it when you have an engaged product owner, a weekly review rhythm and the ability to stop or redirect work. Watch for teams that report hours without reporting outcomes. A time-and-materials engagement still needs a scope, a priority order and a written definition of done for each increment.

Capped time and materials

A ceiling is agreed, but work inside the ceiling remains flexible. This is a practical compromise for a phase with known boundaries and expected discovery.

Choose it when you can name the outcome for the phase but not every task, and you want a hard limit on exposure. Watch for a cap set so low that the team stops before delivering anything usable. The cap should be tied to an acceptance event, not only to a number.

Stage-gated milestones

Work is divided into phases, each with its own deliverables, acceptance criteria and funding decision. The buyer can stop after any gate without renegotiating the whole programme.

Choose it when the project is large enough to justify governance, or when the business needs evidence before committing the next tranche. Watch for gates that assess documents rather than working software. A gate should require a demonstrable outcome and a named approver.

Dedicated product team

A cross-functional team is retained for a period to build and maintain a product. The buyer pays for capacity rather than a fixed deliverable.

Choose it when the product will continue to evolve and you can supply prioritisation, domain knowledge and decisions at a steady pace. Watch for a retainer with no quarterly outcome review. Capacity without direction becomes an expensive way to keep a backlog warm.

Estimation methods underneath the contract

MethodHow it worksUse it whenWeakness
AnalogousCompare with a similar delivered projectEarly budget range, little detailHidden differences dominate
Bottom-upEstimate each task and sumScope is well understoodMisses integration and coordination work
Three-pointBest, likely and worst case weightedUncertainty is materialCan create false precision
ParametricCost per unit such as screen or integrationRepeated, comparable workUnits hide complexity differences
Reference classUse data from many similar projectsPortfolio planningRequires reliable historical data

Whichever method is used, separate effort from duration and from price. Effort is work. Duration is calendar time, which depends on decisions, availability and dependencies. Price adds commercial margin, risk and overhead. A budget that treats them as one number cannot explain a variance.

Hybrid patterns that work

  • Paid discovery, then fixed price: reduce uncertainty first, then commit to a narrower build.
  • Stage gates with a capped contingency: fund phases, hold a reserve for approved changes only.
  • Retainer with quarterly outcomes: capacity is retained, but each quarter has a named result and a stop option.

Red flags in cost planning

  • An estimate with no assumptions, exclusions or dependency list.
  • A fixed price for a product whose requirements are still being discovered.
  • A change process that exists only after the first dispute.
  • Contingency hidden inside the base estimate.
  • Payment schedules tied to calendar dates rather than accepted deliverables.
  • No named owner on the buyer side for decisions and acceptance.

A decision framework

  1. Can you write testable acceptance criteria for the whole scope? If yes, fixed price is viable. If no, do not pretend.
  2. Is the main uncertainty in the requirement or in the effort? Requirement uncertainty favours discovery and time-based work.
  3. Can your organisation make decisions weekly? If not, a retainer or fixed price will both stall.
  4. What is the cost of stopping? Stage gates and capped phases preserve that option.
  5. Who owns the code and the documentation at exit? Put the answer in the contract, not in a slide.

Budget pressure is not imaginary. Gartner's outlook on IT spending shows organisations balancing growth investments against cost control, which makes the choice of commercial model a board-level decision rather than a procurement detail. The model should match the uncertainty you actually have.

Where our team fits

We scope and deliver custom applications, integrations and MVPs under Custom Software & Integrations, using staged commitments where the requirement is still moving. Scope and starting points are on the pricing page. For the cost components behind these models, read custom software project cost planning in Bangladesh.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes