The kind of show that comes out of Madison is a little different from the kind of show that comes out of a big media city, and I think that difference is exactly why so many of these hosts have a hard time finding the right editor, because the people talking are usually engineers, implementation specialists, clinicians who moved into software, researchers with a lab to run, and they are not trying to become entertainers, they are trying to explain something difficult to people who need to understand it, right, and an editor who cuts for hype will quietly wreck that.
So this post is for those people, the host of a healthcare IT show, the comms person at a research group, the recruiter who wants candidates to hear what the work is actually like, and the question I want to answer honestly is whether an editing team sitting in Dubai is a sensible choice for a show recorded in Madison, Wisconsin, and what it actually looks like day to day when it works.
Is an editor in Dubai a sensible choice for a Madison show?
Yes, for almost every show, because editing is file work and the only thing that has to travel is your footage, which goes into a shared folder from wherever you record. What you need is an editor who understands technical conversation and who returns the work on a schedule you can plan a release around.
I say that as the founder of Pixel Samy, whose editing team works entirely out of Dubai, so obviously I have a bias, but the reasoning stands up without me. A local editor is useful when you want someone in the room on record day, holding a boom or fixing a light, and if that is genuinely what you need then hire locally, that is the better choice for you. For everyone else the edit happens on a computer, and the computer does not care which side of the isthmus it sits on.
Madison is a city on a thin strip of land between Lake Mendota and Lake Monona, which is a nice way of thinking about it, actually, because a good technical podcast lives on a similarly thin strip, between too much jargon and too little substance, and the editor's job is to keep the conversation on that strip without making the experts sound dumbed down. That is a judgment skill, not a location skill, and it is the thing I would test any editor on, local or remote.
I made the full case for why distance matters less than people assume, honest exceptions included, right, in why the editor down the street is not automatically the safer pick.
What kind of shows do Madison hosts actually make?
Most of the shows I would expect from Madison fall into three groups, healthcare software and implementation shows, university research and science communication shows, and recruiting or internal shows built to explain what a workplace is really like.
Epic Systems has its campus in nearby Verona, and whatever you think of the wider healthcare software world, it means the region has a lot of people who understand electronic health records, clinical workflows and hospital IT from the inside, and plenty of them either host shows, appear as guests, or work at smaller companies in the same orbit that want a show of their own. These conversations are dense, right, a guest might spend four minutes on how a go-live weekend actually runs, and the instinct of a careless editor is to trim that down to a soundbite, when the four minutes are the whole reason someone pressed play.
Then there is the University of Wisconsin-Madison, one of the country's big research universities, which means researchers, labs, departments and outreach teams who want to explain their work to the public, to funders, or to students they hope to recruit. I wrote more about that world in podcast editing for universities, but the short version is that a research show lives or dies on clarity, so the edit has to protect the explanation first and the pace second.
And the third group, which people forget, is internal and recruiting shows, where a company records conversations with its own engineers so that candidates and new hires can hear what the job really involves, and those have their own rules, which I covered in internal company podcast editing.
How do you edit a technical conversation without losing the substance?
You edit it by listening to the whole thing first and cutting for understanding, which means removing the false starts, the repeated setup and the dead air while keeping every step of the explanation that a listener needs to follow the argument.
This is where I get a bit stubborn, right, to be very honest. The editors on our team hear every minute of an episode before deciding anything, software gets used to sync the cameras and clean the audio and never to choose a cut, and nothing in our process runs on silence detection, because on an ordinary show those automatic cuts just make the conversation feel jumpy, while on a technical show they do something worse, they remove the half second where the guest was about to add the important qualification, and the sentence ends up meaning something slightly different from what they meant.
So the way we actually work on these shows is, basically, that one, we keep the qualifiers, because in healthcare and research "in most cases" and "in our pilot" are doing real work, secondly, we tighten the setup but leave the reasoning, and on top of that we add lower thirds and on-screen labels so that when a guest says an acronym the audience is not lost for the next two minutes.
On a technical show the cut that hurts you is never the long one, it is the one that quietly removes the qualifier the guest needed.
For healthcare topics there is one more layer, which is that anything touching patients or protected information has to go through your own compliance or communications review before it publishes. We do not give legal or regulatory advice, we just edit and flag anything that sounds like it identifies a person, and the HHS guidance on HIPAA is the place your team will usually start from. If clinicians host your show, my notes on podcast editing for doctors cover the time side of that problem.
How does the time difference between Madison and Dubai work?
If your lab or product team records in the afternoon and someone uploads the files at 6 pm Central, it is 4 am in Dubai during the US winter, when we are 10 hours ahead of Madison, and 3 am in summer, when daylight saving shrinks the gap to 9 hours.
What that means day to day, right, is that the handoff happens while Madison sleeps. The folder takes the full camera originals and the audio however big they are, so nobody in the department has to compress or trim anything first, and by the time our editors start their morning the recording is already sitting there. The first cut reaches you within 48 hours, your one round of notes goes back, and the revised episode follows a business day later. And if you want to see what time it is on our side before you book anything, a live Dubai clock will show you.
The one honest caveat is that a really long episode, one packed with on-screen labels and diagrams, or a four-camera panel can need an extra day, and I would rather you hear that when you book than find out on the morning you planned to publish. The full remote setup is explained in the remote editing guide, and the four steps themselves live in how it works.
What does podcast editing cost for a Madison show?
For a research or healthcare IT show with a lot of on-screen labelling, the plan that usually fits is Studio, where sixty minutes or less on two to four cameras is 299 dollars an episode, with lower thirds and custom graphics part of the price.
The reason is the labels, right, because a guest who mentions three acronyms and a regulation in one answer needs four lower thirds in two minutes, and on that plan the graphics work is simply part of the episode rather than a line item somebody has to approve. If your show is one person on one camera explaining things plainly, the cheaper single camera plan does the job well.
Shorter and longer lengths, the packs for teams who publish on a schedule and the add-ons are all listed in the pricing section, and you pay episode by episode, so a show that goes quiet for a semester is not costing anybody money. To be very honest, though, I would not choose a plan from a blog post, I would choose it from your last episode, which is exactly what I do on the call.
Can you match the look our Madison show already has?
Yes, a few of your published episodes are enough for us to copy your opening sequence, the name cards, the pacing and the grade closely enough that your audience never notices a new editor took over.
This matters a lot for company shows, right, because the people who approve them care about brand consistency far more than any listener does, and a sudden change in fonts or colour is the kind of thing that gets a show paused while someone asks questions. So we copy what exists first and only suggest changes later if you want them.
And the files stay yours, every camera original, the edit project and each finished export, so if you ever move on, the project goes with you and another editor can open it and carry on, which is exactly the question a procurement person at a healthcare company asks, so I would rather answer it plainly here.
Who in Madison is a good fit, and who is not?
The best fit is a Madison team that records regularly, cares about technical accuracy, and wants a predictable 48 hour turnaround without hiring a full-time editor, and the worst fit is a show that needs someone physically present at the recording.
I am pretty sure most software shows look a lot like SaaS shows in general, so if that is you, my notes on podcast editing for SaaS founders are worth a read. If your company is spread across the state, there is a sister post on podcast editing in Milwaukee, which deals with manufacturers and automation shows rather than research and software.
Where I would honestly send you somewhere else, right, is if you want a single in-house hire who also runs your social channels and sits in your Madison office, because that is a different job and an in-house person is better for it, or if your show is a one-off recording and you never plan a second, because a solo freelancer will handle a one-off perfectly well. Does that line up with what you actually need, or is your situation somewhere in between? Either way, fifteen minutes on a call while I look at one recent episode is enough for me to give you a price, or you can write to samy@pixelsamy.com. And if you also want help with the packaging, the thumbnail and the title for each episode, that can come from our packaging studio ClickTheory through its podcast thumbnail service.
Why does any of this matter for a research or healthcare IT show?
It matters because the audience for these shows is small, expert and short on time, so every confusing cut costs you trust with exactly the people you most want to reach.
At the end of the day a show like this is not trying to go viral, right, it is trying to make one hospital administrator, one grad student or one candidate engineer understand something they did not understand before, and that is a really really specific job. Across the more than 400 episodes we edit and curate each month, the technical shows that keep going are, in my experience, the ones where nobody can spot the editing, where the guest comes across as the sharpest version of themselves and the listener never stops to wonder what was taken out. That is what we try to give a Madison host every single week.
So yeah. That's my way of saying it.