Scope & Statement of Work

Build the scope for your rollout.

Choose what is changing, who it reaches, and how presenters, animation, and hands-on practice should work together. A live blueprint shows how each choice shapes the work, and you can send the finished scope straight into a consultation request.

The builder never produces a price, estimate, or quote. Final deliverables, timeline, and commercial terms are confirmed after discovery in a formal Statement of Work.

Start building

Scope Builder

Start from an example or a blank scope. Each answer updates the blueprint, and you can move between steps at any time.

What is changing?

Start from an example rollout and adjust it, or answer from scratch.

Start from an exampleEach example fills in every step. You can change any answer afterwards.
Which kind of initiative is it?
Where is the initiative today?
When do people need to be ready?
What actually drives scope?

Ten factors shape every engagement.

Runtime and length

How much needs to be communicated, and how long each video or practice session runs.

Story complexity

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

Systems

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

Screen recreation

How much of the real software is recreated, and how faithfully.

Scenes and environments

Locations, system states, process stages, and presenter settings.

Practice depth

How many tasks people rehearse, how the simulation responds, and how results are tracked.

Custom visual assets

Products, equipment, facilities, documents, and other company-specific elements.

Motion and transitions

Camera movement, interface transitions, workflow animation, and data movement.

Reach

Audiences, sites, languages, versions, and formats.

Review and approvals

How many rounds, and who signs off, including legal and compliance.

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, practice depth, source-material readiness, and stakeholder review can materially change the work required.

From discovery to Statement of Work
  1. 01
    Map it

    Discovery, scope and SOW.

    This page
  2. 02
    Explain it

    Scripts, storyboards, films.

  3. 03
    Do it

    Build, review, pilot.

  4. 04
    Prove it

    Rollout, readiness, after go-live.

See how we work

What the Statement of Work sets out

  • Deliverables and formats
  • Review rounds
  • Hosting and sign-in
  • Data handling and retention
  • Your team's involvement
  • Rollout approach and dates
  • Go-live support window
  • Estimated schedule
  • Commercial terms

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.