Quotes for the same scope routinely come back three times apart, and nobody in the room can explain why. For the buyer, a fixed fee looks like certainty; for the studio, it is a bet placed before the riskiest work has been done. That gap is where custom software projects go wrong — usually around month four, when the integration nobody scoped starts eating the margin.
Why fixed-fee estimates fail on Indian B2B projects
Fixed-fee estimates fail because they get built from a feature list instead of from the work that list implies. Counting screens and forms tells you nothing about the four decisions hiding inside each one: whose credit limit applies, what happens to an order when Tally is down, whether a credit note needs an e-invoice IRN, and who approves a discount above 5%.
In our experience, the riskiest line items on an Indian mid-market project are rarely the UI. They are Tally, SAP or Busy sync, GST invoicing edge cases, dealer and distributor hierarchies, data migration out of a twelve-year-old Excel habit, and the client's own availability for UAT during their busy season. None of those show up in a screen count.
How to price custom software projects on a fixed fee
Price from person-days and a blended rate, then add a risk buffer sized to the specific unknowns — not a flat percentage sprayed across the whole estimate.
Work through five steps:
- Break the scope into work packages (discovery, design, backend, integration, frontend, QA, release) and estimate each in person-days by role.
- Multiply by a blended day rate. For a mid-size Indian studio, ₹6,000 to ₹9,000 per day covers a mix of senior and mid-level people, before GST.
- Add contingency only to the packages you are least sure about — integrations and data migration usually take 20-30% extra, screens take 5%.
- Load project management at 15-20% of delivery effort. It is real work, not overhead you absorb quietly.
- Round up to a clean number last. A ₹16.5 lakh quote reads as a considered estimate; ₹16,43,750 reads as a spreadsheet.
Rates move with stack and seniority — our pricing page shows how we break a day rate down.
Worked example: a dealer portal for a ₹300 crore distributor
Take an illustrative Gurgaon distributor of industrial components — ₹300 crore turnover, 120 active dealers, orders taken by phone and WhatsApp. They want a dealer portal: login, order placement against sanctioned credit limit, Tally Prime sync, dispatch tracking, GST invoice download and WhatsApp status updates. Quoted at ₹16.5 lakh before GST, delivered in 18 weeks.
The estimate behind it: 199 person-days at a blended ₹7,000.
- Discovery, BA and solution design: 20 days
- UI/UX: 16 days
- Backend and Tally integration: 62 days
- Frontend: 45 days
- QA: 26 days
- DevOps and release: 9 days
- Project management: 21 days
That is ₹13.93 lakh of effort. Tally sync and credit-limit logic carried 18% contingency — about ₹1.9 lakh — taking it to roughly ₹15.8 lakh, rounded to ₹16.5 lakh to cover a 60-day support window. With 18% GST the billing is ₹19.47 lakh. Milestones: 15% on signing, 25% on design sign-off, 30% at UAT start, 20% on go-live, 10% after 60 days. We have written up similar builds in our case studies.
What the fixed-fee contract must contain
The contract, not the estimate, is what actually protects a fixed fee. Attach a numbered assumptions list ('Tally Prime 4.x, one company, one-way sync, dealer master supplied as CSV') and an exclusions list: licences, hardware, WhatsApp BSP fees, third-party API costs, data cleanup beyond two passes.
Then pin down four things:
- A change request rate card — a fixed day rate, a two-day minimum, and a 48-hour approval window written into the agreement.
- Acceptance criteria the client can test themselves, with 10 working days of silence counting as acceptance.
- A revision cap: two rounds per screen, after which it becomes a change request.
- A warranty period of 60 or 90 days of bug fixes, kept separate from paid support.
Where the risk buffer goes
The buffer is money you hold, not padding you refund at the end. On a ₹16.5 lakh project, roughly 10% — about ₹1.6 lakh — should sit as internal contingency that never appears in the client's scope. If the project runs clean, that is margin. If Tally's API behaves in an undocumented way in week nine, it is the difference between a difficult project and a loss-making one.
Two habits make this work. When a client pushes for a lower number, cut scope, never the day rate — a discounted rate follows you into every change request. And keep a written estimate behind every quote you send; when the same client asks for phase two in eight months, the person-days are already there.
Where to start
Before you quote anything, write the assumptions list. It is a 40-minute exercise and it will move your number more than any pricing model. If you have a project in front of you and want a second pair of eyes on the estimate, or want to see how we scope before we price, get in touch — Maysan Labs builds B2B portals, dashboards and internal tools for Indian mid-market companies from Gurgaon and Cardiff.
Buying software or a website?
Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.
Get the free checklistRelated case study
Storefront we build and run ourselves
We needed a storefront we could sell and run, not only build: stock, orders, payments and customers in one place.
Written by Sanjay Mandal at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn