POC Builder
A reference blueprint for scoping a four-week proof of concept. Nothing you select is stored - placeholders in square brackets are filled in by you before sharing.
POC status: Not started
Step 1 of 8: Industry
Selections autosave to the opportunity.
Default POC structure (administrator-editable)
Applied to every generated proposal unless changed.
Scope
- - Up to 2 data sources
- - Up to 100,000 customer records
- - Identity resolution
- - Unified customer profile
- - Up to 3 agreed use cases
- - 1 audience or activation output per use case
- - Results presentation and scale-up roadmap
Out of scope
- - Replacement of existing CRM, POS or campaign systems
- - Production-grade integrations or real-time streaming
- - Custom model development beyond the agreed use cases
- - Campaign execution, creative or media spend
- - Data remediation at source
- - More than two data sources or three use cases
Client responsibilities
- - Provide agreed data extracts and a data dictionary
- - Confirm identifiers available for identity resolution
- - Nominate business and technical contacts
- - Complete security and data-sharing approvals
- - Attend weekly reviews and validate outputs
- - Confirm the channel that will receive the activation output
Fusion360 responsibilities
- - Configure the Fusion360 environment for the pilot
- - Ingest and map the agreed data sources
- - Run identity resolution and build unified profiles
- - Configure the agreed use cases and produce audience outputs
- - Report against the agreed success criteria
- - Present results and a production scale-up roadmap
Assumptions
- - Data is provided in an agreed format within the first week
- - Identifiers are present on a workable share of records
- - Client contacts are available for weekly reviews
- - Volumes stay within the agreed record limit
- - No source-system changes are required during the pilot
Risks
- - Delayed data access shifts the timeline week for week
- - Low identifier coverage limits identity resolution results
- - Absent activation channel ownership limits the measurable outcome
- - Changing use cases mid-pilot reduces comparability of results
Prerequisites
- - Named business sponsor
- - Named technical contact
- - Access to agreed data sources
- - Data dictionary and sample files
- - Historical transaction data where applicable
- - Customer identifiers such as email, phone number or loyalty ID
- - Defined success metrics
- - Security and data-sharing approvals
- - Weekly review availability
Next steps after the POC
- - Results review with the business sponsor
- - Agree production scope, sources and use-case roadmap
- - Confirm commercial model and implementation timeline
- - Plan data-governance and security requirements for production
Commercial - all values administrator-defined
- POC fee: [ADMIN-DEFINED]
- Applicable taxes: [ADMIN-DEFINED]
- Payment terms: [ADMIN-DEFINED]
- Travel or third-party costs: Excluded unless specified
- Fee adjustment against production: [YES/NO, ADMIN-DEFINED]
- Offer validity: [ADMIN-DEFINED]
