RAPIDITERATION — SOFTWARE PROJECT BRIEF
Version: 2026-10-31
Guide: https://rapiditeration.com/insights/choosing-software-development-company-bc/

Copy this worksheet into your own document. It is a planning aid, not a quote.
Use the same completed brief with each supplier. Do not include passwords,
client records or sensitive personal information.

1. THE OUTCOME
Organization / project:
Decision owner and day-to-day contact:
Who needs to do what, and why does it matter?
What happens today? Include a real exception as well as the usual path.
What observable change would make the project worthwhile?
How will you measure that change, and who owns the baseline?

2. THE FIRST COMPLETE JOURNEY
User / role:
Starting condition:
Steps to completion:
Approval or review required:
What the user sees at the end:
What happens with missing information, an error or duplicate submission?
Accessibility and device requirements:

3. THE BOUNDARY
Must work in the first release:
Explicitly out of scope:
Possible later additions:
Existing tools that must remain:
Data sources and owners:
Integration access / documentation available:
Migration sample and data-quality questions:
Hosting, security, privacy and procurement requirements:

4. THE WORKING AGREEMENT
Budget boundary and currency (including or excluding taxes):
Deadline and the reason behind it:
Client staff availability:
Decision/review cadence:
Who owns code, hosting accounts, data and third-party subscriptions?
Who approves scope and cost changes?
What documentation and handover must be included?
What support coverage is needed after launch?

5. ACCEPTANCE EXAMPLE
Given [a role and starting data], when [a person completes the workflow],
then [an observable result], including [an exception or permission boundary].
How will this be demonstrated, and who accepts it?

6. COMPARE SUPPLIERS
For each topic, record: demonstrated / explained but unverified / unanswered.
Keep the evidence or reference, owner of follow-up and decision consequence.

Topic: comparable delivery and exact responsibility
Topic: assigned team and availability
Topic: scope, exclusions and acceptance
Topic: budget assumptions and change control
Topic: code, account and data ownership
Topic: permission, migration, recovery and release checks
Topic: support and exit/handover

7. DECISION
Proceed / investigate a named uncertainty / stop:
Evidence behind the decision:
Unresolved questions, owners and dates:
Next agreed deliverable:

RapidIteration — Vancouver, BC — hello@rapiditeration.com