MonDev / Insights
How to prepare a web development specification that leads to better software
A practical briefing structure for explaining business outcomes, users, workflows, integrations and constraints before requesting a proposal.
MonDev · October 19, 2026
Start with the decision, not the feature list
A useful specification explains why the project exists and which business outcome it supports. A list such as dashboard, API and admin leaves too much room for incompatible assumptions.
Describe the current process, the problem it creates and the change you expect. Features can then be evaluated against that purpose instead of becoming requirements by repetition.
Describe users in terms of responsibility
Name each user group, the information it needs and the decisions it can make. Avoid broad labels such as admin when several teams require different authority.
Include external users, support staff and people who handle exceptions. A permission matrix often exposes hidden scope earlier than a collection of interface mockups.
Write the critical journeys from beginning to end
Explain the few outcomes that must work on day one, including the trigger, decisions, notifications and completion state. Add the exceptions that carry financial, legal or customer consequences.
These journeys give designers and engineers a shared basis for prototypes, estimates and acceptance tests without dictating every implementation detail.
Make integrations and data ownership explicit
For every external system, identify the information exchanged, which side owns each field, how often data changes and what should happen when a service is unavailable.
Include representative samples, current documentation and access constraints where possible. Unknown legacy behavior should be labeled as a discovery risk rather than assumed away.
Separate constraints from preferences
Legal obligations, committed launch dates, required platforms and existing contracts are constraints. A preferred framework, animation style or reporting layout may be negotiable.
Marking the difference lets an engineering partner propose alternatives without accidentally challenging a requirement the business cannot change.
Define acceptance through observable outcomes
Acceptance criteria should describe what an authorized user can complete and what evidence confirms success. Avoid subjective phrases such as modern, intuitive or fully optimized without a measurable context.
Also state who provides content, reviews prototypes, supplies system access and approves releases. A specification is stronger when client responsibilities are as visible as supplier deliverables.
Leave room for informed discovery
A specification should make the problem understandable, not pretend every decision is already correct. Invite suppliers to identify risks, alternatives and assumptions in their response.
For uncertain applications, the best next step may be a paid discovery with reusable outputs rather than a fixed build quote based on guesses.