Designed for saas founders explaining a feature, workflow or empty state.
A polished dashboard loop often becomes outdated quickly. Isolate the underlying interaction so the animation explains the feature without relying on exact production screens.
What we can build
- Abstract product walkthrough.
- Empty and processing states.
- Reusable interface motion components.
The final deliverables are agreed during discovery. Source files, implementation support and additional platform variants are included only when explicitly scoped.
A clear control contract
Plan the animation’s public controls before producing a full motion library. A starting specification might include:
- stage: workflow milestone.
- progress: known completion value.
- result: confirmed outcome.
These are proposed control names and behaviors, not an existing Rive asset. The final file determines the actual property and state names.
Integration considerations
Distinguish illustrative marketing motion from live product status. For in-product use, bind to actual events and scope asset updates alongside UI changes.
Review the behavior
Review whether the story makes sense without exact labels or sample data. Verify that a live progress control never implies invented progress.
From brief to handoff
- Define. Review your audience, key events, platform and asset requirements.
- Design. Approve the visual direction, key poses and transition rules.
- Build. Rig the artwork and author the agreed state system.
- Validate. Review an export against the acceptance sequence and target runtime.
- Handoff. Deliver the scoped assets, control map and integration notes.
Questions before we start
Can this be used on a landing page?
Yes. Marketing scenes can be authored for the web with a static fallback; in-product scenes need a separate event and accessibility review.
What should I include in the brief?
Share the target platform, screen dimensions, existing artwork, desired states and any runtime restrictions. A short recording of the current product is useful.
How are timing and cost agreed?
Scope depends on the artwork, state count, platform validation and revision needs. A defined brief comes before a project estimate.