How to scope a software project before you talk to any agency

Start with five answers

Most estimates vary because the brief leaves the hard parts undefined. Each team fills those gaps with different assumptions. Answer these five questions first.

1. Who uses it on day one?

Name the first real users, not the total market. A dispatcher and three drivers is a scope. Logistics companies is not.

2. What workflow must work end to end?

Write the one loop that matters as numbered steps. Everything outside that loop can wait for a later phase.

3. What data does it touch?

Say where the data lives today and which other systems must stay in sync. Spreadsheets are a valid answer.

4. What already exists?

Include prototypes, designs, failed attempts, and examples. Existing work shortens discovery.

5. What changes after launch?

Choose one observable result for the first ninety days. Hours saved, leads handled, or tickets resolved are better than a broad goal.

Put it on one page

Send the same page to every engineering team you speak with. Ask for a fixed first phase, weekly demos, production delivery, and a written handover.