A great talk, buried in a bad recording.
The talk landed in the room. The recording does not. The slides are unreadable, the pace drags, and the screen share is a blur, so the version that lives online undersells the speaker and the product.
Service · Conference video
Conference talk editing that keeps the room awake.
A 45-minute recording, re-cut into a talk people finish.
// what we do
Lumaris edits developer conference talks, the KubeCon, re:Invent, and GitHub Universe kind, into video people actually finish.
Editors who write code re-cut the recording for pace and accuracy, rebuild unreadable slides and screen captures as clean insets, and return a watchable talk in about five days. From €2,000 per talk.
// who this is for
A conference talk is recorded once and watched, if you are lucky, by the room. The footage then sits on a drive, or goes up as a 45-minute single-angle video that loses most viewers in the first two minutes. The talk was the expensive part. The edit is what makes it pay off.
We turn a recorded developer talk into video people actually finish: the live energy kept, the dead air gone, the slides and terminal readable, and the technical claims still correct.
// the case
The questions you're weighing.
What we do with a raw conference recording.
Re-cut for pace, readable slide and terminal insets, chapter markers, captions, and a clean export, in about five days.
The editor has to know which line of the demo matters.
Cutting a technical talk means knowing which line of the demo carries the point before you can cut around it. Editors who write code read the terminal and the slides and keep the substance intact while making it watchable.
// dev-validation
Your engineers review nothing.
Editors who write production code cut the work, and every command on screen clears a line-by-line check before you ever see it. The accuracy is handled before the review loop starts, so the draft lands right the first time.
- Commands run against current docs
- A receipt names what was verified
- 1 to 2 revision rounds, not 4 to 6
# video: cli-quickstart-v3 · client: [redacted] # checked against docs @ 2026-06-09 ✓ cli flags // 14 commands run, all current ✓ api references // v3 endpoints, no deprecations ✓ architecture diagram // matches running product ! terminology // "cluster" → "node pool" (corrected) ✓ code blocks // compiled, 0 syntax errors
# one in-house technical-video hire build.hire = { salary_loaded: "EUR 60,000 - 120,000 / yr", output: "capped at one person", ramp_gaps: "hiring, onboarding, PTO, churn", }; # the Lumaris floor buy.lumaris = { retainer: "EUR 72,000 / yr", // EUR 6,000 / mo includes: "a team, dev validation, a PM, strategy", output: "a full video arm, ~5-day cadence", };
// build vs buy
What it costs.
The front door is one video from €2,000, a complete purchase you keep. The retainer, from €6,000 a month, is the upgrade once the work earns it, never the gate. We frame cost one way only: build versus buy, never a vendor price match.
€2,000 a video · yours to keep €6,000 a month · the upgrade
What every engagement includes
One scope, not a tier menu.
- Edits of recorded talks and sessions
- Slide and terminal legibility cleanup
- Chapters, captions, and social cut-downs
- Command and code accuracy checks
- About a five-day first draft
- From €2,000 per talk, or inside a retainer
Keep exploring
More from the studio.
Lumaris is a technical-video studio for developer tools, with the mechanism behind the work on the method page and the reasoning in developer retention benchmarks. The fastest way to judge it is a free re-cut on your own video.
FAQ
Conference talk editing, in short.
What does conference talk editing include?
A re-cut for pace, readable slide and terminal insets, chapter markers, captions, and a clean export, plus the short clips that surface the talk to people who were not in the room. The result is one strong asset instead of an hour of single-angle footage nobody finishes.
Can you fix an unreadable screen share?
Yes. A blurry projected slide or a low-contrast screen capture gets rebuilt as a clean inset, legible on a phone. Because the editors write code, the rebuilt terminal and slides stay accurate to what the speaker actually showed, not a guess at it.
How fast is the turnaround?
About five days to a finished talk. The speed is a documented system, not a scramble, so you get the re-cut, the insets, the chapters, and the social clips on a predictable timeline rather than waiting weeks for one editor to find a gap.
See it on your own footage.
On your own footage, not a case study. Nothing filmed yet? Send a topic.