Five stages, five concrete deliverables
A serious software engagement isn't a black box between "we signed a contract" and "here's your app." It follows a structured process, and each stage should produce something concrete you can point to — not just a status update.
01 — Discovery
Requirements, constraints, and success metrics get mapped before any code is written. This stage should end with a scoped requirements document — not a vague understanding, an actual written scope both sides agree to. If a vendor skips straight to a quote without this, that's a red flag: they're guessing, not scoping.
02 — Design
Product flows, data models, and technical architecture get designed before heavy engineering begins. For customer-facing products this includes UI/UX design; for internal tools it may be lighter, but the underlying architecture decisions still need to happen here, not mid-build. This stage should produce a technical architecture plan and, where relevant, design files.
03 — Development
Build happens in focused sprints with frequent demos and deployable increments — not one long silent stretch followed by a single "big reveal." You should be seeing working software regularly through this stage, not just hearing that progress is being made.
04 — Testing
Performance, responsive behavior, edge cases, and integrations get validated before launch. This is where release readiness actually gets confirmed, rather than assumed. A vendor that treats testing as an afterthought squeezed into the last few days is a vendor cutting corners you'll find out about in production.
05 — Launch
Deployment happens with monitoring in place, documentation handed over, and a clear plan for the next iteration — not a deploy-and-disappear. Ask specifically what post-launch support looks like before you sign, not after something breaks.
Timelines by project size
As a rough guide: small internal tools typically run 6-14 weeks depending on scope; larger platforms with more integrations run longer. See Custom Software Development Cost in India for how timeline and cost move together.
What good looks like in practice
This is the process we run on every engagement — see it applied to a real project in our case studies, or read How to Choose a Software Development Company for how to evaluate whether a vendor is actually following a process like this or improvising.
Start with discovery
Tell us what you're building and we'll walk you through exactly how discovery works before anything gets scoped or priced.