How to Scope a Custom Software Project Before Asking for a Quote
Give vendors the same workflow, release boundary and acceptance cases so their proposals answer the same questions.

Scope a custom software project for a quote by documenting the business outcome, users, first workflow, integrations, release boundary and acceptance tests. Identify what still needs discovery so vendors can estimate the same work.
Key takeaways
- Describe the current workload and the result you need.
- Include one routine case and the exceptions that matter.
- List access, data and vendor dependencies that could change the estimate.
What should a one-page scope brief contain?
| Field | What to write | Fictional example |
|---|---|---|
| Outcome and baseline | One business result and how you measure it today | Reduce time reviewing stock transfers currently emailed by three shops. |
| Users and roles | Who submits, who approves and who resolves exceptions | Store supervisor submits. Operations approves or rejects. |
| First workflow | Starting event, key decisions and output | A supervisor requests a transfer. Operations reviews it. The sending and receiving locations see the decision. |
| Data and integrations | System owners, IDs, formats and access still to confirm | Current SKU catalogue and inventory service. Transfer endpoint is unverified. |
| Release boundary | What this release covers and what is deferred | Internal requests and reporting in scope. Supplier orders deferred. |
| Acceptance | Sample input, actor, expected result and failure behaviour | Approve 12 units. Capture 11 received. Show one unresolved on the original request. |
What should you test beyond the normal path?
Choose two cases that can create downstream work. In the sample, a reviewer should see a transfer that was already approved before authorizing it again. A receiving user should be able to record a short shipment with its reference. Put test data, expected behaviour and the decision-maker in the brief so vendors can discuss the same scenarios.
Call out assumptions with a cost or timeline impact. For example, note whether the inventory vendor grants access to a test environment and how the project changes if only scheduled exports are available. Identify the business owner who can resolve open process decisions during delivery.
How do you make quotes comparable?
Ask vendors to return included work, exclusions, dependencies, commercial assumptions and the boundary between delivery and ongoing support. Ask what would cause a change request and who signs off at each milestone. Use one brief and a consistent set of questions across vendors.
If you can describe the result but still have unresolved data access or exceptions, use the Product Discovery Sprint to test those assumptions and build a prioritised backlog. Discuss your brief with Wizy.
Frequently asked questions
How much detail do you need before requesting a software quote?
Provide enough detail to demonstrate the first workflow, name the affected systems and define what acceptance looks like. Ask vendors to document assumptions and exclusions wherever information is still missing.
Can you get a useful estimate before confirming an integration?
Ask for an estimate that states its assumptions about access, data and interfaces. Separate the work needed to verify the integration from the delivery estimate that depends on it.
What makes a good software acceptance criterion?
Specify the actor, starting data, action and observable result, including what should happen on failure. A useful test lets the team agree whether the workflow passed.
