What you can hire me to deliver
- An audience, message and distribution brief.
- A reviewed product script and demonstration plan.
- Video assets with captions and supporting written content.
- A version register covering exports, claims and source files.
Decide what the video must help someone understand
A launch film, a software walkthrough and a customer tutorial serve different decisions. Before choosing a visual treatment, define the viewer, their starting knowledge and the action the explanation should support. A prospect may need to understand fit; an existing user may need to complete a task.
I can help write a brief that separates the central message from supporting details. That makes it easier to decide which screens or product actions deserve attention and which belong in a written reference or a separate demonstration.
Show a complete and credible workflow
For software, prepare a demonstration environment with fictional data and reproducible steps. For a physical product, use approved source material or a capture brief that identifies the details the viewer must see. The script should connect the starting problem, the product action and the observable result without implying an outcome the demonstration does not establish.
Configuration, plan restrictions and dependencies should be reflected in the explanation where they affect the claim. A recording is stronger when the team can repeat the workflow and explain its conditions. I can work with your product or technical owner to make that review practical.
Have a specific workflow or content brief in mind? Send the audience, the task and your current material. I can help define the next useful scope.
Discuss product videosChoose production methods after the message
A screen recording may be sufficient for a focused workflow. Another brief may need diagrams, supplied footage, animation or a presenter. I can help define the production approach, and any specialist filming, character work or additional crew can be separately scoped.
AI-assisted production can support parts of the workflow when appropriate, but the final content still needs factual, brand and rights review. Voice, likeness, music and visual assets must have an approved basis for use. Do not create a synthetic endorsement or a customer appearance without permission.
Build versions from a maintained source
A main explanation can support several shorter assets, but each version needs enough context to remain accurate. A cutdown should not remove the condition that made the original claim true. The source register can connect scripts, exports, captions and language variants so the team knows which versions need an update.
Agree distribution formats and the destination before exporting. A video embedded in a help article has different surrounding context from a standalone sales clip. Captions and a written summary can support the audience even when they cannot or prefer not to use audio.
Illustrative product walkthrough scope
An initial engagement could explain how a user completes one important task in a software product. The package might include a reviewed script, a demonstration recording, a caption file and a short written companion. Product reviewers would confirm the setup and claims; a small audience review would test whether the next step is understandable.
Measurement should match the purpose. A viewer completing a tutorial task is different from a buyer deciding to request a demonstration. We can define those events separately and avoid treating views alone as evidence of sales, adoption or product success. The handover includes editable sources and an owner for future product changes.
How delivery and scope are agreed
Start with a representative task and the people who can approve it. We agree the audience, source material, formats, review responsibilities and acceptance check before expanding production. A focused pilot makes it possible to evaluate both the content and the workflow required to use it.
Brief and source review
Confirm the task, available inputs and responsible reviewers. Separate decisions that need your approval from implementation work I can own.
One complete example
Produce a reviewable script, asset or workflow prototype. Test the important assumptions before repeating the approach across a library.
Review and pilot
Check accuracy with the source owner and usability with representative people. Record the agreed revisions and unresolved limits.
Publish and maintain
Deliver the agreed formats, editable sources and ownership notes. Define the publishing destination and the changes that trigger a review.
What shapes the quote
The quote depends on the condition of the source material, subject complexity, number of assets and languages, production method, integrations and review rounds. Specialist filming, language partners, platform licenses and external assets are itemized when needed. A target date and the review schedule are agreed after those dependencies are understood.
Implementation experience behind the service
My career includes Shopify and Webflow operations, subscriptions, analytics and Klaviyo at Nello, and Shopify and Shopify Plus delivery with team leadership at Integriti. That background connects customer-facing explanations with the systems behind them. That practical context helps align scripts, demonstrations and supporting resources with the actual customer workflow.
Explore Nello and Integriti experience →Questions before we start
Can you produce both marketing and tutorial content?
Yes. We should define those as different audience tasks, even if they share a demonstration source. The marketing version explains fit and value; the tutorial supports completion of a specific workflow.
How is the production approach chosen?
The production method is agreed after the brief. Screen capture and content development can be scoped directly; specialist live-action, animation or other production support is specified separately when needed.
Bring me the task you need to explain.
Send the product link, the audience, the workflow to explain and where the video will be used. Include the product reviewer and any footage, brand assets or demonstration environment you already have.
Send your project brief on WhatsAppRelated services
Further reading
W3C guidance on accessible audio and video. A resource for the subject owner’s planning and review.