PRODUCT CONFIGURATOR PROJECT BRIEF
Prepared by:
Date / revision:
Project contact:

Use this worksheet to describe one representative product family. Write
"Unknown" where an answer needs discovery. Do not include credentials,
private customer information or files you do not have permission to share.

1. CUSTOMER AND OUTCOME
Who will use the configurator?
What choice is difficult today?
What evidence shows the problem (for example, repeated sales questions)?
What is the primary next step: basket, quote, saved design or specification?
What should be excluded from the first release?

2. PILOT PRODUCT
Product family / public product URL:
Representative product identifier:
Options the customer can change:
Product owner who can confirm the rules:

3. THREE EXAMPLES TO TEST
Valid selection:
Expected preview, summary and output:

Invalid selection:
Why it is invalid:
What the customer should see:

An earlier choice changes:
Which later choices are affected?
Should the customer confirm a replacement or choose again?

4. DATA AND ASSETS
Existing CAD / 3D models and formats:
Dimensions and approved photographs:
Materials / finishes and reference samples:
Rights and permissions confirmed by:
Pricing source and owner:
Availability source and owner:
Stable product and option identifiers:
Missing files or known quality issues:
Who signs off visual accuracy?

5. CUSTOMER JOURNEY AND HAND-OFF
Where does the visitor start?
Default configuration:
How are choices grouped?
Required final summary:
Which system receives the selection?
Required data fields / quote or basket contract:
Who can provide a safe test environment?
What happens if a model or integration fails?
What happens to saved selections when the catalogue changes?

6. ACCEPTANCE EVIDENCE
Target devices, browsers and connection conditions:
Initial page / 3D loading requirements:
Agreed performance budgets and test method:
Keyboard, focus and assistive-technology checks:
Equivalent route without manipulating the 3D view:
Representative product-rule test cases:
Evidence that the correct selection reaches sales or checkout:
Person responsible for accepting each area:

7. COMMERCIAL EVALUATION
Current baseline and date range:
Primary business outcome:
Measurement and consent requirements:
Pilot review date / minimum useful sample:
What result would lead to continuing, changing or stopping the pilot?
Do not treat launch acceptance as proof of increased conversion or revenue.

8. DELIVERY AND OWNERSHIP
Budget range:
Target date and reason:
Decision-makers and approval availability:
Separate estimates requested for discovery, assets, build, integration,
testing, handover and ongoing support:
Code / asset ownership terms to agree:
Who maintains products, finishes and rules after launch?
Routine update to demonstrate during handover:
Documentation, training and recovery materials required:
Assumptions and exclusions still to resolve:

Prepared by Niall Arnfield
https://niallarnfield.com/product-configurator/