MVP BUILD — SOFTWARE DEVELOPMENT BRIEF
Version/date:
Decision owner:

1. THE PROBLEM
Primary user and situation:
Current workaround and its cost:
Evidence collected (links, dates, limitations):
Outcome this release must deliver:

2. FIRST RELEASE
One complete journey, from trigger to completed result:
User roles and permissions:
In scope:
Explicitly out of scope:
Manual operations and responsible person:

3. ACCEPTANCE EXAMPLES
Given [starting state], when [action], then [observable result].
Failure, duplicate and cancellation cases:
Who accepts the result, in which environment:

4. DATA AND DEPENDENCIES
Data types and sensitivity:
Integrations, access owner and available documentation:
Sample data and migration needs:
Content, branding, legal and operational inputs:
Dependency deadlines:

5. DELIVERY AND COMMERCIALS
Budget envelope, currency and tax treatment:
Target release and reason for date:
Team availability and decision cadence:
Accounts, repository, design files and hosting ownership:
Licences and retained supplier components:
Release, support and handover expectations:

SUPPLIER RESPONSE — USE THIS SAME FORMAT
Recommended scope and what to defer:
Assumptions and unanswered questions:
Named delivery roles and allocation:
Milestones, acceptance process and dependencies:
Price model, total, tax, payment schedule and exclusions:
Change process and spending limit:
Recurring costs at low, expected and high use:
Warranty, support response and exclusions:
Handover and exit arrangements:

Template by MVP Build. Complete with real evidence and scope-specific terms.