Notes for owners · Business growth
Pricing a software or IT service: fixed, subscription or time-and-materials
Fixed price, subscription and time-and-materials move risk between you and the buyer in different ways. Here is how to choose the model that matches how your buyer budgets, with the points a proposal should settle whichever you pick.
The GullySales team · Updated 17 Oct 2026 · 6 min read
On this page
- What does each model actually do with risk?
- How does your buyer budget?
- When should you quote a fixed price?
- When does a subscription fit?
- When is time-and-materials the honest answer?
- For example: a Kochi firm building a booking app for a clinic group
- What should a proposal say whichever model you choose?
- Match the model to your last five deals
Choose the price model by asking how your buyer budgets. A buyer who must get a number approved before work starts is usually best served by a fixed price. A buyer who uses the thing every day and pays from running costs suits a subscription. A buyer who cannot yet say what they want suits time-and-materials, with a limit. Each model moves risk. Give it to whoever can control it.
What does each model actually do with risk?
A price is a way of deciding who pays when something goes differently from the plan.
- Fixed price. You carry the risk of the work taking longer. The buyer carries the risk of the scope being wrong, because change costs more.
- Subscription. You carry the risk of building something people stop using. The buyer carries the risk of paying for something they use less than they thought.
- Time-and-materials. The buyer carries the risk of the work taking longer. You carry the risk of being seen as having no accountability.
None of these is risk-free. Ask which risk your side can manage better, and which your buyer is willing to hold.
How does your buyer budget?
How a buyer budgets can decide the model, and it is easy to forget to ask. Find out in the first meeting.
| If the buyer says... | They budget as... | Model that fits |
|---|---|---|
| "I need to get a number approved by the director or partners" | A one-off item with a cap | Fixed price, in stages |
| "We pay for tools monthly, from running expenses" | A running cost | Subscription |
| "We have a team and need extra hands" | Capacity | Time-and-materials, with a ceiling |
| "We are not sure what we need yet" | Exploration | A small paid discovery, then choose |
| "We want it maintained once it is live" | Support cost | Annual maintenance or retainer |
If the finance person cares about a clean capital item, a fixed price with milestones is easier for them to explain internally. If the user cares about starting small, a subscription is easier to say yes to.
When should you quote a fixed price?
A fixed price works when you can answer yes to these four:
- Can you list what is included, screen by screen or module by module?
- Does the buyer have one person who can say "this is accepted"?
- Have you built something similar before, so that your estimate is based on experience?
- Are the change rules written down, with a price or rate for extra work?
If any is a no, either narrow the scope until all four are yes, or use another model. A fixed price for a vague scope looks generous and ends in an argument.
Split the price into stages tied to something the buyer can see. A payment that depends on "completion" can wait indefinitely. A payment tied to a signed-off design, a working test version and a go-live is easier to collect.
When does a subscription fit?
A subscription is right when the buyer gets value each period, not once, and you keep working on it. It suits software the team uses daily, and managed services such as backup, monitoring and helpdesk. It lowers the first decision from a big sum to a small one, which helps with an owner who is wary.
It fits poorly when the thing is built once and left alone, or when the buyer's finance person wants an asset instead of an expense. Also, write down what happens when they stop: how they get their data out, and how long you hold it. A buyer who can see the exit may find it easier to enter.
When is time-and-materials the honest answer?
When the work is real but the shape is not. Maintenance, integration with an old system, a product still finding its features. Be straight with the buyer: say that an estimate is not a promise, and show how you will keep them informed.
Make it safe for them with four habits. Write an estimate for each piece of work. Set a monthly ceiling that needs their word to cross. Keep a log of hours they can read. Check in on what is left. For the buyer this sits closer to a fixed price, while you are still paid for the hours worked.
For example: a Kochi firm building a booking app for a clinic group
Take an invented small app firm in Kochi that quotes a single fixed price for a booking app for a group of diagnostic centres. The group's operations head kept adding report-delivery and WhatsApp reminder features after the quote. The firm said no to each, the head felt ignored, and the project stalled before go-live.
On the next project the firm starts with a short, paid discovery for a fixed fee and writes the result as a numbered scope. It then quotes the build at a fixed price in three stages, each ending in a demonstration that the head signs. Requests outside the numbered scope go on a list with an estimate beside each, and the head chooses which to buy. Quarrels now have a document to point to. Not all of them go away: the head still wants WhatsApp reminders in stage one, and the firm agrees to put them in at a price that leaves its margin thin. Charging for discovery, even a small fee, also gives the buyer a reason to read what comes out of it.
What should a proposal say whichever model you choose?
- What is included and what is not, in words the buyer can repeat.
- What drives the price, so that a change is understood, not resented.
- How change requests are priced and approved.
- What the buyer must provide, and what happens if it is late.
- Who owns the code, the data and the accounts at the end. Ask your lawyer to draft this clause.
- How and when the buyer can stop.
How managed IT providers write a proposal covers how the finance head reads these points.
Match the model to your last five deals
List your last five deals. Beside each, write how the buyer budgeted and which model you quoted. The mismatches show where deals stalled. Once a pattern appears, set a default model for each type of buyer. Setting those defaults is pricing and packaging strategy, and other work for software and IT firms is under technology. When you are ready, tell us what you need.
