Software Outsourcing Pricing Models: Fixed Price, T&M, Dedicated Team

This explainer is for founders, directors and IT heads in India who are about to sign a contract with a software company and want to understand how the money side works before the legal side. After reading you will be able to pick the pricing model that fits your project, know where the risk sits in each one, and check that the contract has the five clauses that actually protect you.

What are the main software outsourcing pricing models

Every outsourcing contract answers three questions: what will be delivered, how you will pay, and who carries the risk if things take longer than planned. The pricing model is just the pattern of answers. Here is each one in plain terms.

Fixed price

You agree a scope, a price and a delivery date up front. The vendor carries the risk of underestimating effort. You carry the risk of having specified the wrong thing, because changes after signing become paid change requests. This model only works when the scope is written down in enough detail that two people would read it the same way.

Time and materials

You pay for the hours or days actually worked, at an agreed rate per role, plus any third-party costs such as cloud hosting or licences. Scope can change at any time. You carry the risk of the total bill growing, and the vendor carries very little. It works well when the vendor reports transparently and you review the work every week.

Dedicated team

You pay a fixed monthly fee for named people who work only on your product: for example two developers, one designer and a part-time project manager. It behaves like having your own team without payroll, office and hiring cost. The commitment is usually 6 to 12 months with a notice period, and you direct the work day to day.

Retainer

A smaller monthly fee that buys a block of hours for support, maintenance, small features and monitoring. Unused hours may or may not roll over, so read that line. Retainers are the normal way to keep a launched product healthy without paying for a full team.

Milestone-based

A fixed-price project split into stages, each with its own deliverable, acceptance test and payment. Typical splits are 30-40-30 or 20-30-30-20. Payment for a stage is released only when you have tested and accepted it. This is the model most first-time buyers should ask for.

Fixed price vs time and materials vs dedicated team: comparison table

The table below is the one we walk clients through before a proposal. Use it to see where each model puts the risk and what you need to do to control it.

Model	Best for	How you pay	Where the risk sits	How you control it
Fixed price	Well-defined projects: a website, a billing app, an MVP with a written SRS	Advance plus balance on delivery, or in stages	Vendor carries effort risk; you carry scope-definition risk	Detailed SRS, clear acceptance criteria, a change request process with unit prices
Time and materials	Discovery phases, evolving products, integrations with unknown legacy systems	Monthly invoice for hours or days worked, plus expenses	You carry budget risk; vendor carries almost none	Weekly timesheets, a monthly cap, sprint reviews, the right to stop at any sprint end
Dedicated team	Products needing 6 months or more of continuous building; SaaS companies; in-house teams that need extension	Fixed monthly fee per person	Shared: you pay even in slow weeks; vendor must keep the same people staffed	Named people in the contract, replacement clause, notice period, monthly output reviews
Retainer	Support and maintenance after launch, small ongoing changes	Fixed monthly fee for a block of hours	You carry unused-hour risk; vendor carries response-time risk	Rollover terms, a response SLA, a monthly usage report
Milestone-based	First projects with a new vendor; anything between ₹3 lakh and ₹30 lakh	3 to 5 payments tied to accepted deliverables	Balanced: vendor is paid as it delivers, you pay only for what you have tested	Written acceptance criteria per milestone, a demo before each payment

How do IT outsourcing prices actually get calculated

Whatever the model, the vendor is doing the same maths underneath: estimated effort in person-days for each role, multiplied by a daily cost per role, plus a margin for risk and profit. The model decides who pays if the estimate is wrong.

• Fixed price adds a contingency of 15-30% to the estimate, because the vendor is absorbing the risk. If your scope is vague, the contingency goes up, and you pay for uncertainty.
• Time and materials has no contingency in the rate, but the total depends on how disciplined both sides are about scope.
• Dedicated team pricing is the monthly cost of each person plus overheads and margin. It is usually the cheapest per hour for long engagements because there is no sales cost per project.

To sanity-check a quote, ask for the person-day breakdown behind it. If a vendor cannot show you how many days of design, development, testing and project management the price contains, the price is a guess. For typical daily and monthly cost bands by role in India, see our guide to developer costs in India.

How to choose the right outsourcing pricing model

The decision comes down to three questions. Answer them honestly and the model usually picks itself.

1. How clear is the scope? If you can hand over screens, a feature list and acceptance criteria, choose fixed price or milestone-based. If you have a direction but not a list, start with a short paid discovery phase on time and materials, then convert to fixed price once the scope exists.
2. How long will the work run? Under 4 months: fixed price. 4 to 8 months with changing needs: time and materials with a monthly cap. Beyond 6 to 8 months of continuous work: a dedicated team is cheaper and more stable.
3. How much time can you give it? Time and materials and dedicated teams need someone on your side to make decisions every week. If nobody has that time, a fixed price with a defined scope protects you from drift.

A common and sensible combination for a product company is: a fixed-price discovery and design phase, a milestone-based build of the first version, then a dedicated team or retainer after launch. Each phase has the right model for its level of certainty.

Contract clauses that matter more than the price

Most disputes we hear about have nothing to do with the rate. They come from five clauses that were either missing or vague. Check each of these before signing.

1. Ownership of code and intellectual property

The contract should state that all source code, designs, databases and documentation created for you become your property on payment, and that the vendor will hand over the repository and credentials. Without this, you can end up with a running product you do not legally own. Also check whether the vendor may reuse generic components; that is normal, but it should be stated.

2. Acceptance criteria and the acceptance window

Each deliverable should have a written test list, and you should have a fixed number of working days (7 to 10 is typical) to test and report defects. Defects found in that window are fixed at no cost. Silence after the window usually counts as acceptance, so make sure someone on your side actually tests.

3. Change request process

Changes will happen. The contract should define how a change is requested, estimated, priced and approved before work starts. A per-day or per-feature unit price agreed in advance removes the argument later.

4. Support, warranty and handover

A warranty period after go-live (30 to 90 days is common) during which bugs are fixed free. After that, a retainer or per-incident support rate. The handover clause should list what you receive: code, deployment scripts, admin credentials, documentation and a recorded walkthrough.

5. Payment terms, termination and data

State the payment schedule, what happens if a payment is late, and what happens if either side ends the contract early: you should receive all work paid for to date. Add a confidentiality clause and a line on where your data is hosted and who can access it.

What JK Tech Hub has seen on outsourcing contracts in Gujarat

Most of our clients are manufacturers, traders, clinics, institutes and product founders in Rajkot, Ahmedabad and Surat, and the pattern of what works is quite consistent.

A forging unit near Rajkot came to us for a production tracking system after an earlier fixed-price project with another team had stalled over change requests. The problem was not the vendor's effort. The original scope was two pages long and every clarification became a paid change. We spent three weeks on a written requirements document first, then quoted a milestone-based price in four stages. The project finished with two change requests instead of twenty.

A Surat textile trader wanted an ERP but could not describe the final system. We proposed time and materials for a two-month discovery and pilot, capped in rupees per month, then converted to a fixed price for the rollout. The cap was the part that made the finance head comfortable.

A SaaS founder in Ahmedabad had been paying for features one at a time and was frustrated by the waiting. Switching to a dedicated team of three with a monthly fee cut the per-feature cost noticeably and, more importantly, removed the quoting cycle before every small change.

The recurring lesson: the model that fits the certainty of the scope wins. Forcing a vague idea into a fixed price hurts both sides.

What this means for your business

If you are buying software for the first time, ask for a milestone-based fixed price with a written scope, an acceptance window and a change request rate. If you already have a product and a backlog, a dedicated team or retainer will cost less per feature than repeated quotes. If you cannot yet describe what you want, pay for a short discovery phase rather than letting a vendor guess and pad the price.

In every case, ask for the effort breakdown behind the number and read the five clauses above before you look at the total. A slightly higher price with clear ownership and acceptance terms is cheaper than a low price with neither.

Related reading and next step

• Developer cost in India: daily and monthly bands by role
• How to write a software requirements document that makes fixed price possible
• Software testing types explained for acceptance planning
• Estimate your project cost with our calculator
• JK Tech Hub, software company in Rajkot

Share your requirement list or even a rough idea through the contact page or WhatsApp us on +91 7265004040, and we will recommend a pricing model and send a fixed quote with milestones.