Scope & Statement of Work

Your transformation determines the scope.

No two enterprise communication initiatives are structured exactly the same. Scope is developed around the story that needs to be told, the systems and processes being visualized, the level of customization required, the final runtime, and how the communication will be used.

Use the interactive scope builder below to explore the elements that can shape an engagement. Final deliverables, production timeline, and commercial terms are confirmed after discovery and documented in a formal Statement of Work.

Build Your Scope

Build Your Communication Scope

Explore the elements that can shape a Sync Studio engagement.

The Communication Scope Builder helps you explore scope. It never produces a price, estimate, or quote.

01How should the story be communicated?

02How much communication needs to be delivered?

Runtime is only one component of scope. A shorter project with highly customized system visualization may require more production effort than a longer presenter-led communication.

03What needs to appear?

Select all that apply

04How many distinct environments or major communication moments may be needed?

A scene may represent a location, a system, a major process stage, a presenter environment, or a significant visual transition.

05How many systems or applications need to be represented?

Examples: ERP, CRM, WMS, MDM, AI platform, BI/reporting, custom internal application, database/data platform, external customer/vendor system.

06Will actual software interfaces need to be recreated or represented?

Basic Representation

Detailed Recreation

The amount of interface recreation can significantly affect production scope, particularly when screens must accurately represent a client's real systems and workflows.

07What customized visual elements may be required?

Custom Visual Assets · select all that apply

08How dynamic does the communication need to be?

09Who is the audience?

Select all that apply

How will it be used?

10Additional requirements

Optional

What actually drives scope?

Nine factors shape every engagement.

Runtime

How much information needs to be communicated.

Story Complexity

How many concepts, workflows, decisions, and dependencies must connect.

Systems

How many applications, interfaces, integrations, and data sources are involved.

Custom UI

How much software/interface recreation is required.

Scenes & Environments

How many locations, system states, process stages, or presentation environments must be created.

Custom Visual Assets

Products, equipment, people, data, documents, interfaces, facilities, and company-specific visual elements.

Motion & Transitions

Animation sophistication, camera movement, interface transitions, workflow animation, and data movement.

Review Cycles

Number of stakeholder approvals and iterations.

Rollout

Number of audiences, versions, languages, formats, and distribution contexts.

Same runtime. Very different scope.

Example A

6-Minute Executive Communication

One presenter
One environment
Limited supporting graphics
Existing script
Limited custom UI

Scope Profile

Focused

Example B

6-Minute ERP Transformation

Four systems
Recreated ERP interfaces
Multiple departments
Warehouse environment
Process animation
Data movement
Custom visual assets
Multiple workflow transitions

Scope Profile

Complex

Runtime is only one part of production scope. Visual complexity, technical accuracy, customization, source-material readiness, and stakeholder review can materially change the work required.

From discovery to Statement of Work

Discovery

Understand the initiative, audience, systems, workflows, materials, and communication objective.

Scope Design

Determine runtime, format, scenes, custom assets, system visualization, production requirements, and review assumptions.

Statement of Work

Deliverables
Expected runtime
Production approach
Key visual requirements
Client-provided materials
Assumptions
Review cycles
Estimated schedule
Commercial terms

Production

Production begins only after scope and commercial terms are agreed.

Expanded usage, exclusivity, or intellectual-property terms can be addressed within the Statement of Work when required.

Every transformation has a different story.

Tell us what your teams need to understand. We'll help determine the clearest way to communicate it.

Schedule Consultation View Our Work