We make animated videos that explain software products and workflows. Our $899 studio package includes a 30–45-second silent launch film and two 6–10-second edits from the same story, in one agreed aspect ratio. Customers can watch representative work, request a tailored preview, and decide on production after reviewing the proposal. We quote narrated walkthroughs and tutorial series separately.
The production sequence follows concept flow, visuals, narration, then audio. A silent film finishes with the visual sequence: motion, labels, and animated text carry the story. When a project includes narration, we establish what the viewer will see before writing and recording the voice.
You can also make the film yourself with the $99/month creation system. It includes one editable template, two example configurations and their finished films, four written lessons, and five guided prompts. Adapt the words, colors, and product screens, then render your own silent film. Start with the free type-motion project and planning templates to try the process.
Your request defines the task and audience
A product URL and a short description of the intended use give us a starting point. A homepage introduction needs to establish why the product matters to a new visitor. An onboarding lesson can assume more interest and spend more time on a specific task.
Useful source material includes a working demo, current documentation, and a recording of the relevant workflow. We also need to know which details require permission or sanitization before they can appear in a film. The explainer brief helps organize that material.
A request might ask how an unassigned support ticket reaches the right team. That question gives us a task to show and an endpoint to verify. A broader request to explain every feature would need a narrower film or a connected tutorial series.
The preview makes the proposed direction visible
We review the request and prepare a preview that demonstrates the proposed direction. You can assess whether the story answers the right question, whether the screens represent your product, and whether the pacing suits the audience.
The proposal records the scope, price, schedule, and deliverables before you decide to buy. It also specifies review rounds, payment terms, and license. Source files and alternative versions belong in that agreement when the project requires them.
Submitting a request does not place an order. Acceptance selects the direction and scope; payment is a separate step. The preview does not promise instant generation, a fixed turnaround, or a complete free production.
The storyboard establishes the visual explanation
We define the concept and sequence of scenes, then record the starting state, action, and result for each scene. A continuing example helps the viewer connect different product surfaces.
For the support-ticket example, the board could show the request, its matching routing rule, and the team field changing. The ticket ID remains consistent across those steps. Its status stays Open if the product has only assigned the request; the film should not imply that assignment resolved the customer's problem.
We check the board against product evidence and resolve unknown behavior before detailed animation. The storyboard guide explains this process with a completed example.
Stills and motion test different decisions
Still frames let us check layout, product labels, and readable evidence. We inspect the important views at the intended player size because a control that looks clear on an editing monitor may disappear in a small embed.
Motion then shows whether viewers can follow the action and its consequence. We retain useful reading time and adjust transitions that hide the result. A successful render confirms that the file exported; visual review determines whether the explanation works.
Narrated projects add words to the reviewed pictures
For a narrated project, we write about the objects and actions on screen after the visual sequence works. The voice can explain why a routing rule matches while the picture shows the resulting assignment. Narration, music, and sound effects require a separate scope from the silent launch package.
We record or synthesize the audio afterward. Measuring the recording helps set scene durations, and a separate playback pass aligns important phrases with their visual events. A clip can fit within a scene while still naming the result too early or too late.
Music and effects follow those decisions. We review them with the voice so they support the explanation and preserve intelligibility.
Review and delivery follow the agreed scope
You review a version of the commissioned video and provide timestamped notes within the agreed rounds. The launch package includes one consolidated storyboard revision before animation and one consolidated film revision within the agreed story. We correct our own implementation errors without using up those revisions. We check the revised export for product accuracy, continuity, and timing, along with captions and audio when the project includes them.
Delivery includes the files listed in the proposal. A later product change may require updates to screenshots, narration, or captions; the original scope should clarify any planned maintenance.
You can watch examples or request a preview for a task your product helps someone complete.