OSPIVIA STUDIO — WEBSITE / WEB APP BRIEF
Reusable template, version 10 September 2026
Guide: https://www.ospivia.it/en/guides/website-app-project-brief
Keep a copy. Do not include passwords or real customer records.

1. OUTCOME
The project lets [user] perform [action] to achieve [outcome].
Current situation:
Why a change is needed:
How we will check that it works:

2. USERS AND DEVICES
Roles:
Approximate user count:
Computers / phones / browsers:
Usage frequency:
Connection availability and required offline activities:

3. FIRST COMPLETE WORKFLOW
Starting action:
Intermediate steps:
Final outcome:
Error behaviour:
Who may view / edit data:

4. FIRST RELEASE AND LATER
Essential at first delivery (up to 5 priorities):
-
-
-
Desirable in a later phase:
-

5. CONTENT AND 3D
Pages / screens:
Available text and translations:
Images and usage rights:
Available 3D models and formats:
Main interaction (rotation, details, variants...):
Visual references and what matters about them:
Materials to produce:
Who approves the visual direction:

6. DATA AND INTEGRATIONS
Data sources (description or synthetic examples only):
External systems and required functions:
Imports / exports:
Accounts and permissions:

7. FIVE ACCEPTANCE CHECKS
For each: device, action, expected result.
1.
2.
3.
4.
5.
Include errors, keyboard, reduced motion and offline where relevant.

8. TIMING AND BUDGET
Budget or indicative limit:
Deadline and reason:
When materials and access will be ready:
Approval owner:
Time available to test delivery:

9. QUOTE COMPONENTS TO REQUEST
Development / assets / content / integrations / acceptance:
Included revisions and out-of-scope changes:
Total including applicable taxes:
Hosting, licences and other recurring costs:
Ownership of accounts, assets and source code:
Backups, recovery, updates and support:

This brief prepares a proposal; it is not an order or contract.
Contact: https://www.ospivia.it/en/contact#custom-project