Contents
If you are planning bespoke software for your business, the useful question is what it will cost to solve your particular problem and keep the system running. Your first budget should cover a usable release, the systems it connects to, launch and ongoing support. Use the worksheet below to ask suppliers for comparable quotes and see which unanswered questions could change the cost. A project-specific estimate needs an agreed scope; a general price band cannot tell you what your build will include.
Define the outcome before the feature list
Write down who needs to do what differently, what gets in their way today and how you will recognise an improvement. A purchasing portal, for example, might need to reduce repeated order entry while preserving approval rules. That is a more useful starting point than asking for a portal with a dashboard.
Separate the first usable release from later ideas. Include the operational work needed for that release: loading existing data, training administrators, supporting users and handling exceptions. A narrow feature list can still describe a substantial project when the surrounding process is complicated.
The GOV.UK Service Manual advises understanding the problem, users and constraints before committing to a build. Its discovery guidance provides a useful starting point for questioning an assumed solution; it does not establish a commercial price or a delivery promise for your project.
Identify the work that changes the estimate
Ask the delivery team to explain the main drivers separately. These may include user journeys, permissions, integration with existing systems, data migration, reporting, testing and release preparation. Two products with similar screens can require very different work behind those screens.
For an integration, establish whether documentation, a test environment and a named technical contact exist. For a migration, inspect representative data and define who resolves duplicates or missing records. For permissions, describe the actual actions each role may take rather than relying on a generic administrator/user distinction.
Record assumptions beside each estimate. If a supplier assumes clean data and an available API while another includes data repair and a bespoke connector, their totals are not directly comparable. Resolve the difference in scope before negotiating the number.
Separate delivery, operation and uncertainty
Build a budget with distinct lines for discovery and design, implementation, migration and launch, and ongoing operation. For ongoing costs, consider hosting, third-party licences, monitoring, maintenance and the support arrangement you actually need. Ask what is included in the quoted period and what is billed separately.
Keep an explicit allowance for unresolved work. Do not choose a contingency percentage simply because it is familiar: identify the assumptions that could change the budget and ask what evidence would narrow the range. A short technical investigation may be more useful than increasing every line indiscriminately.
Include your organisation's contribution. Someone must answer product questions, arrange access, review releases and make decisions about scope. Those responsibilities affect both effort and elapsed time even when they do not appear on the supplier's invoice.
Compare proposals on the same basis
Request a shared statement of scope, exclusions, acceptance criteria and dependencies. Ask how the team handles changes, what triggers a revised estimate and what happens when an assumption proves wrong. Understand whether a price is fixed for a defined scope, an estimate of time and materials, or a capped phase with a separate next decision.
Compare handover and support as well as delivery. Establish who controls repositories and hosting accounts, what documentation you receive and how defects are distinguished from new requirements. Have the relevant commercial terms reviewed by the people responsible for procurement and contracts.
A proposal should make the next commitment understandable. If the problem is not yet well defined, commission a bounded investigation with named outputs and a decision at the end. If the scope is sufficiently understood, ask for a delivery plan that explains how progress and acceptance will be demonstrated.
Build a comparable estimate worksheet
Create one row for each complete user journey, integration, migration, launch activity and recurring service. Give every row the same fields: outcome; included work; excluded work; supplier effort or price basis; your team's responsibilities; dependency; acceptance evidence; and the unresolved question that could change the estimate. Ask every supplier to complete the same worksheet.
For an illustrative order-approval journey, the outcome might be that an authorised manager can approve an order within their own location. Included work could cover access rules, approval history, notifications and rejected orders. A useful acceptance check would show that a manager cannot approve another location's order. The unresolved question might be whether approval limits come from an existing system. This is a synthetic planning example, not a description of a particular customer's implementation.
Summarise one-off delivery and launch costs separately from recurring costs over a stated planning period. Use the same period and assumptions for every proposal, record whether amounts include VAT, and distinguish committed prices from provisional estimates. Calculate the comparable total as delivery plus migration and launch plus operation over that period. Keep risk allowances visible beside that total, with a reason for each allowance rather than an unexplained percentage.
Before committing, give each important unknown an owner and a way to resolve it. If an integration determines feasibility, a technical spike using synthetic data may be the next purchase. If a workflow is well understood and isolated, a bounded first release may be appropriate. The worksheet should lead to a decision about the next phase; it is not evidence that all future work can be priced today.
Synthetic example — order approval journey. This is not a customer project or price quote.
- Outcome
- A manager approves an order for their own location
- Included work
- Access rules, approval history, notifications and rejected orders
- Excluded work
- Changes to approval limits in the existing system
- Supplier effort or price basis
- Supplier to enter their effort or price basis
- Your team’s responsibilities
- Confirm roles and approval rules
- Dependency
- Confirm where approval limits are held
- Acceptance evidence
- A manager cannot approve another location’s order
- Unresolved question
- Do approval limits come from an existing system?
| Outcome | Included work | Excluded work | Supplier effort or price basis | Your team’s responsibilities | Dependency | Acceptance evidence | Unresolved question |
|---|---|---|---|---|---|---|---|
| A manager approves an order for their own location | Access rules, approval history, notifications and rejected orders | Changes to approval limits in the existing system | Supplier to enter their effort or price basis | Confirm roles and approval rules | Confirm where approval limits are held | A manager cannot approve another location’s order | Do approval limits come from an existing system? |
What to send a software company for a useful quote
You do not need a finished technical specification to start a conversation. Bring a short description of the problem, who will use the software, the existing systems it must work with and the outcome you want. Include a deadline and the reason for it, your available budget or funding position, and any work already completed. Use made-up examples when demonstrating records or workflows rather than sharing customer data.
Ask for a proposal that separates the first release from later improvements and explains what your team must provide. If the main uncertainty is whether an existing system can connect, ask for a defined investigation before committing to the full build. If the requirements are understood, ask what you will receive, how you will accept it and who supports it after launch.
An illustrative budget for a request portal
For this fictional planning exercise, assume 30 staff, two approval roles, one documented external API, browser access and no historical migration. Allow 8 person-days for discovery and workflow design, 32 for implementation, 12 for testing and release, and 4 for handover: 56 person-days. At an assumed blended £650 per day, the delivery allowance is £36,400. A separately held 15% contingency adds £5,460, giving a planning total of £41,860 before VAT.
These are invented assumptions for arithmetic, not a Veda quotation, a market average or a promised timeline. Person-days do not translate directly into elapsed days. Exclude subscriptions, hosting, ongoing support and future changes from this delivery figure, then obtain separate allowances for them. If the external API lacks test access, do not hide that uncertainty inside the 32-day build line: commission an investigation and revise the scope.
Try a sensitivity check before requesting proposals. Adding 10 person-days for migration increases the delivery allowance by £6,500 and the 15% contingency by £975. Reducing the first release to one complete workflow may remove scope, but dropping permission checks or recovery work removes protection. Use the existing worksheet to replace these assumptions with your own, and carry the same scope into the build-versus-buy comparison.
How this relates to Veda Software’s work
The Powerleague print portal is relevant to scoping venue roles, ordering and central oversight. Its published account establishes those responsibilities; it supplies no price or effort benchmark for this fictional portal.


