Custom Software Development India: A Checklist

Most custom software projects in India do not fail because the code is bad. They fail before the first commit: a two-line brief, three quotes that differ by 4x, and no agreed definition of done. If you are a founder, finance lead or CTO at an Indian SMB commissioning your first serious dashboard, internal tool or B2B portal, this is the part nobody hands you.

Write the brief before you ask for quotes

A brief that says we need a CRM will get you five quotes that have nothing in common, and every one of them will be wrong. Spend two hours on one page:

• Who uses it, and in what role? Admin, sales rep, auditor, dealer, customer.
• What are the five to eight jobs it must do? Write them as sentences, not feature names.
• What must it connect to? Tally, Zoho Books, Razorpay, GST e-invoicing through an IRP, WhatsApp Business API, an existing ERP.
• Rough volumes: 200 orders a day or 200 a month? Five users or 500?
• What must not change? Invoice formats, approval chains, audit trails.
• Who signs off acceptance, and by when?

One page turns a negotiation into a scoping conversation, and it settles most later arguments about cost, because nearly every one of them traces back to an assumption nobody wrote down.

What custom software development India projects get wrong, phase by phase

Ten steps, in the order they actually happen. The order matters more than the steps.

• Discovery (1-2 weeks). Get a written scope document with every screen listed and every flow drawn. Pay for this stage separately if you have to; it is the cheapest money in the project.
• Phasing. Force a v1 that ships in 8-12 weeks. Write down explicitly what v1 will not include.
• Architecture and hosting. Decide now whether this runs on managed cloud, your own server, or the vendor's. Read up on how we approach architecture before anyone locks you in.
• Quote and assumptions. Ask for a line-item breakdown: design, backend, frontend, integrations, QA, deployment, and the bug-fix window after launch.
• Contract. IP assignment in writing, source code in a repository you own from day one, milestone payments (a common split is 30/30/30/10), and a real exit clause.
• Weekly demos. You should be clicking through working software on a staging URL by week three. If you are not, the project is slipping already.
• Data migration. Dry-run with a copy of your real data two weeks before go-live. It always surfaces duplicate customers and invalid GSTINs. If the work is mostly customer-facing, web platform builds have their own rhythm.
• QA and UAT. Three to five real users, real data, two full working days. Not a demo on the vendor's laptop.
• Handover. A runbook, every credential in accounts you own, and a backup restore you have personally watched succeed.
• Support. Expect 30-60 days of included bug fixes. An annual maintenance contract after that typically runs 15-20% of build cost.

What it costs and how long it takes

Ranges below are what we see for Indian SMB and mid-market projects, quoted in rupees and exclusive of GST. They move with integrations and roles.

• Internal dashboard or operations tool: typically 4-8 weeks, ₹3-8 lakh.
• B2B portal with logins, roles, negotiated pricing and payments: typically 10-16 weeks, ₹12-30 lakh.
• Multi-tenant SaaS product: typically 4-7 months, ₹35 lakh and up.

A worked example: a 40-person distribution business wants its 300 dealers to place orders themselves. Scope is three roles, dealer-specific pricing, Razorpay collection, order push to Tally, and a WhatsApp confirmation. Realistic build: about 11 weeks with a team of four, roughly ₹16-20 lakh including design and QA. Two mid-project change requests — dealer credit limits and a second price list — added about nine working days. That is normal. Discovering them in month four because nobody demoed anything is not.

Two things move the number more than anything else: each integration is effectively a small project of its own, and role and permission logic can add weeks on its own. If what you actually need is a storefront, the build-versus-buy maths changes; headless commerce ROI is worth ten minutes before you commit to a custom build.

The India-specific items people forget

• GST at 18% applies to software services on top of the quoted build cost. Budget for it from the start.
• TDS under section 194J at 10% on professional or technical fees. You deduct it, the vendor claims it. Plan their cash flow and yours.
• DPDP Act, 2023. If the software touches customer KYC, health or financial data, you need consent flows, a stated retention period and a breach-notification process. Ask where the data physically sits.
• Data residency and latency. For India-only users, an India region or your own machine is often faster and simpler. Self-hosting and server setup covers what that involves.
• Collections. UPI and cards are straightforward. Recurring mandates, international cards and refunds are not.

Where to start

Start with the one-page brief, this week, before you talk to anyone. Two hours of writing will sharpen your quotes, your timeline and your contract. If you want a second pair of eyes on it — or you would rather have a scope document and a fixed, line-item quote written against it — Maysan Labs does exactly that from Gurgaon, for teams across India and the UK.