Blog 5 min read
Scoping a custom software project: the questions we ask first
Before estimating anything, we try to understand five things. Here they are, and why they matter more than a feature list.
By the Smile Software team
When someone asks how much a piece of software will cost, the honest answer is 'it depends'. To make that answer useful, we start every project conversation with the same questions.
1. What happens today?
We want to understand the current process in detail — including the workarounds. The spreadsheet someone maintains on the side often reveals the real requirement.
2. Who will use it, and how often?
Software used all day by a small team is designed differently from software used once a month by thousands of customers.
3. What does success look like?
Faster processing, fewer errors, new revenue? A measurable goal helps prioritise ruthlessly.
4. What does it need to connect to?
Integrations are often the largest source of uncertainty. Knowing early which systems are involved, and whether they have usable APIs, changes estimates significantly.
5. What are the constraints?
Deadlines, budget, regulation, data location, existing technology choices. Constraints aren't problems; they're design inputs.
With these answers, we can propose a first release that's small enough to deliver quickly and valuable enough to matter.
