How to write a custom software brief before asking for a quote
Custom business programs
The short answer
A useful custom software brief describes the business problem, who needs to do what, the information involved, and how you will know the work is complete. Include the current process, one ordinary example, one exception, existing tools, access rules and launch essentials. You do not need to select a programming language or draw every screen before talking to us. Clear boundaries matter more than technical vocabulary.
The brief gives everyone the same starting point. It should reduce assumptions about the job, not become a document so elaborate that nobody who performs the work has time to check it.
Start with the change you need in the working day
Describe the problem as an observable event. For example, staff cannot tell whether a request has been approved without asking the owner. That is more useful than asking for a modern dashboard. Explain who experiences the problem, how work is handled now and what information is missing.
If you know how often it happens or how long it takes, include the source of your estimate. Label a rough estimate as such. Do not turn an unmeasured frustration into a savings claim. Name someone who understands the process and someone authorized to decide scope. They may be the same person, but the responsibilities should be explicit.
List the people, records and boundaries
Identify each user type in plain language: customer, coordinator, reviewer or administrator. For each, say which records they need to see, what they may change and which actions require someone else's approval. Include temporary staff, departing users and people representing a customer company if relevant.
List the information the tool must hold and where it originates. Customer details, jobs, quote versions and approval notes may be related without being the same record. Note sensitive information that should not be collected at all. Describe the permitted business use rather than sending live records, passwords or account recovery codes with an initial inquiry.
Write the workflow as steps, including the awkward branch
- What starts the process?
- What details must be available before the next step?
- Who checks them and what rule do they apply?
- What can be approved, returned for correction or rejected?
- Where does the approved result go?
- What happens if the user changes their mind or a connection fails?
Keep the first version focused on one complete path. A list of disconnected features leaves the important handoffs unclear. You can attach a simple diagram, but write out rules that a diagram might hide, such as whether an approved price may be edited and who can reopen a closed request.
An illustrative brief you can adapt
Illustrative example: a small team needs an internal exception-review tool. The coordinator enters a request; a manager decides whether the unusual service conditions can be accepted.
- Problem
- Review decisions are scattered across messages and cannot be found reliably by another staff member.
- First-release task
- Create a request, assign a reviewer, record a decision and let the coordinator see the current status.
- Required information
- Request ID, service type, exception reason, assigned reviewer, decision and decision time.
- Approval rule
- Only a reviewer may approve. Returned requests need a reason and can be corrected and resubmitted.
- Not in this release
- Customer logins, payment collection, automatic pricing and changes to accounting records.
A redacted normal request and a returned request would help explain this brief. The team would first check whether its existing task tool can support the required review process.
Replace vague wishes with acceptance checks
Write what you will observe when the task works. In the example, a coordinator must not be able to approve their own request; a returned request must display the reviewer's reason; a second authorized colleague must be able to find the current decision. Include incorrect input and an unavailable connection, not only the successful path.
GOV.UK's user-story guidance explains the relationship between the person, their goal and acceptance criteria. You can use ordinary sentences rather than a formal template. Avoid requirements such as easy to use without identifying the task and the person who will test it. Include keyboard access, phone use and readable error states where relevant.
State dependencies and unknowns without solving them yourself
Name the existing tools, who administers them and what the new system needs to read or update. If integration access has not been checked, say so. Record migration needs, attachment types, known data-quality issues and whether history must remain editable or just readable.
Separate a genuine deadline from a preferred date and explain what drives it. List available content, reviewers and access arrangements. Confirm who will answer questions and approve changes during the build. Unknowns are acceptable at the beginning; hiding them makes quotes harder to compare. A brief can explicitly ask for an initial investigation of a connection before its implementation is priced.
Review the brief with the people doing the work
Walk through the draft using the ordinary example and the exception. Ask staff what they would do if the owner were absent or an input were wrong. Remove features that nobody can connect to a real task. Mark remaining ideas as essential for launch, useful later or still uncertain.
Send the brief with a redacted example and the outcome you want to discuss. Our custom-program work starts with agreed needs, including internal tools and customer-facing flows. The brief is a starting point for scope, not a promise that every requested feature or connection is feasible or included.
A few follow-up questions
Do I need wireframes before asking for a quote?
No. A workflow and representative inputs and outputs can be enough to start. Sketches help when a particular interaction matters, but do not let screen layout substitute for explaining the business rules.
Should I include my budget?
Include a real constraint if you have one. It helps frame a smaller first release or a product-based alternative. It does not replace scope or establish a guaranteed price.
What if two staff members disagree about the process?
Record the disagreement and assign a decision owner. Software should not silently settle an unresolved business policy merely because one person wrote the brief first.
Sources and further reading
Bring the rough brief
Share the process, users, examples and the parts you have not resolved. We can discuss what belongs in a first release and what needs checking before a quote.
Discuss your project brief See what our custom business programs service includes