SOFTWARE PROJECT BRIEF

Business and contact:
Who will use the software, and on which devices?
Describe one task from start to finish:
Inputs, required fields and expected output:
Systems, files or APIs involved today:
User roles and who may approve changes:
First-version requirements:
Explicitly out of scope:
Acceptance checks (including missing data and unauthorized users):
Deployment target and who owns the accounts:
Source-code ownership and handoff documentation:
Support, maintenance and recurring costs:
Target date and budget:

The published $500 deposit secures an architecture review and specifications session. Agree build scope, price, ownership and ongoing costs separately.
Use redacted examples. Do not include passwords, private customer data or access keys.