Accelerate technical video production without putting your engineers on camera

I focus on technical videos used for developer onboarding, enablement, product demos, and customer success.

This includes documentation walkthroughs, feature demos, getting-started series, integration guides, and internal or external enablement libraries.

Sorry, but I don't do purely promotional or marketing videos (e.g., animated explainer videos or ads).

Yes. Existing documentation, tutorials, demos, or support articles that have been vetted and approved are required as a starting point.

If you need help revising existing materials or creating new content for video specifically, I can be hired at an hourly or daily rate for scripting and content creation.

In most cases, involvement is limited to async Slack questions when I need clarification on technical details not covered in the source, plus a final script review for technical accuracy.

The goal is to remove engineers from the production process as much as possible and to only involve them when absolutely necessary.

Most projects are scoped and priced as a fixed engagement based on the length and complexity of the resource.

If there are significant unknowns, such as incomplete documentation or complex technical setups, I may need a short discovery phase billed at an hourly rate before providing a scope and price.

Timelines depend on scope, availability, and familiarity with your products and domain, but most videos are delivered within one to two weeks of starting production.

The more robust your docs and environments are, the faster I can ship.

Scripts allow for three revisions before filming begins, and the final video allows for a single review with non-piece-to-camera edits only, e.g., screen captures, b-roll, and motion graphics.

Additional revisions can be accommodated at an hourly rate.

The key to minimizing revisions is ensuring all stakeholders have signed off on the source materials and script before filming.

I typically use Slack for async communication via a private channel with the required stakeholders and technical staff.

As a general rule, I'm happy to use precise messaging about your product features and functionality and am open to feedback on tone and style as long as I can still present authentically.

Where I'll push back is on unverifiable claims or marketing language that would be unnatural for me to say or doesn't resonate with developers. If it's not something I would say, I won't say it, as then my trust and credibility with the audience is compromised.

In these cases, I won't just reject that part of the script, but will provide alternatives that aim to get the same point across.

For piece-to-camera sections and parts where I'm explaining concepts or workflows, I generally stick closely to the script to ensure accuracy with your messaging.

For screen recordings and demos, I may improvise slightly to maintain a natural flow, but I'll always ensure that the key points and steps are accurately represented as per the script.

Yes, and I often end up working in a consultative capacity once teams are ready to scale-up video production by leveraging internal staff and resources.

Whether it's advice on gear to purchase or coaching staff to be comfortable on camera, I'm happy to share my knowledge and experience to help you be self-sufficient.

My goal is not to make you dependent on me — but to quickly get you up and running with a repeatable process that your team can own and eventually scale internally.