Ramp time is the most expensive thing nobody measures#
Gallup's research estimates it takes around 12 months before a new hire reaches their full performance potential. Bridge Group research on sales roles puts full ramp at about three months, which is why the standard sales measure is 90 days plus the length of the sales cycle.
Both numbers are correct. They just define "ramped" differently, and that gap is worth understanding before you try to shorten anything. Three months is when someone can execute the core loop of the job unsupervised. Twelve months is when they are as good as they are going to get, including the tacit knowledge, the internal network, and the judgment calls. Most organizations quietly optimize for the first definition and then wonder why year-one output disappoints.
Either way, the money involved is significant and rarely appears on a budget line. Here is illustrative arithmetic rather than a benchmark, since the real figure depends entirely on your roles:
Take an employee whose fully loaded cost is 100,000 CHF a year, taking eight months to reach full productivity, and averaging roughly half of full output across that ramp. That is approximately four months of foregone output, around 33,000 CHF per hire. Cutting three weeks off the ramp is worth roughly 3,000 CHF per hire. Hire fifty people a year, and you are looking at about 150,000 CHF of recovered output, from a change that costs almost nothing to make.
Docebo's version of this math for a sales hire is starker: an account executive on a 500,000-dollar quota whose ramp is halved delivers over 60,000 dollars in additional revenue, per salesperson hired.
The point is not the specific number. It is that ramp time is a real, large, recurring cost that most organizations treat as a fact of nature rather than something they can influence.
Preboarding is the cheapest ramp time you will ever buy#
There is a window between offer acceptance and day one that most organizations barely use. During it, the new hire is enthusiastic, curious, has more discretionary time than they will have again for months, and is actively thinking about the job.
What most of them receive during that window is a document pack.
Employment terms, working time rules, safety procedures, IT and security policy, benefits documentation, the code of conduct, site or plant-specific procedures. In industrial, regulated, or unionized environments, this routinely exceeds a hundred pages before someone's first day.
This is a strange allocation. You have your new hire's highest attention and lowest workload, and you spend it on the least engaging material you own. Then day one arrives, and the manager re-explains most of it verbally anyway, because nobody read it.
Why the document pack does not work#
Not because new hires are lazy. Because of how the material is structured relative to the situation.
A hundred-page pack arrives with no triage. Everything looks equally mandatory, so a new person cannot tell which twelve pages actually change what they do on Monday and which eighty are legal boilerplates that exist for compliance reasons. Faced with an undifferentiated wall, most people skim, sign, and hope.
Long documents also have a completion problem regardless of context. Long-form written content typically sees only 20 to 30 percent of readers reach the end. This is the onboarding-specific version of the unread problem: the information you legally distributed is not the information anyone actually received.
And the material arrives without a narrator. A document explains rules. It does not explain why the rule exists, what actually happens in practice, or which parts matter most in the first week. That interpretive layer is exactly what a new person needs and exactly what a PDF cannot supply.
The consequence compounds. The pack fails to land, so the content gets re-explained in person during week one, consuming manager time. And because the pack consumed the preboarding window, the connection and culture work that actually drives retention never got its slot. We cover that trade-off in more detail in our complete guide to employee onboarding.
What a welcome podcast actually is#
A welcome podcast is a short, finite audio series that a new hire receives after accepting the offer, covering the context they need before day one.
It is not a recurring internal show. This distinction matters more than it sounds, because it changes the entire economics. A recurring internal podcast needs new episodes forever, which is why most of them die around episode six when the owner's enthusiasm meets their actual workload. A welcome podcast is built once, covers material that changes maybe annually, and runs for years. If you are considering a recurring show as well, the setup decisions are different and we cover them in our guide to launching an internal podcast.
It is also not an audiobook of your handbook. Reading a policy document aloud produces something with the same structural problems as the document, just slower. The value is in restructuring the material for a listener: adding the context, ordering it by what matters first, and cutting what does not need to be spoken.
A five-episode structure that works#
Here is a concrete starting structure. Total runtime around 45 minutes, which is roughly two commutes.
Episode 1: Welcome and what this company actually does (6 to 8 minutes). Source material: your company overview deck, annual report summary, product pages. Cover what the organization makes or does, who the customers are, and where the new hire's function fits. Most new starters have only a vague sense of this from the interview process. Getting it right early makes everything else make sense.
Episode 2: Your first week, hour by hour (5 to 7 minutes). Source material: your onboarding checklist and first-week schedule. Where to go, what time, who they will meet, what to bring, what the dress code actually is in practice, where to park, what happens at lunch. This is the episode that reduces first-day anxiety more than any other, and it is almost never provided in any format.
Episode 3: How we work here (8 to 10 minutes). Source material: internal comms guidelines, team norms, tooling documentation. Which channel is used for what, meeting culture, what "urgent" means here, how decisions get made, who to ask about what. This is the tacit knowledge that otherwise takes three months to absorb by observation, and it is the single largest ramp accelerator in the set.
Episode 4: Safety, security and the rules that matter most (10 to 12 minutes). Source material: safety procedures, IT and security policy, code of conduct. The critical distinction: this episode covers the twenty percent of compliance content that changes daily behavior, explained with the reasoning behind it. It explicitly does not replace the written documents, and it should say so out loud in the episode.
Episode 5: Benefits, admin and how to actually use them (6 to 8 minutes). Source material: benefits documentation, HR policy, expenses process. What people are entitled to, how to claim it, and the three things everyone gets wrong in their first month. Benefits are routinely under-used simply because nobody knows what exists.
Two structural notes. Keep episodes under twelve minutes, because a single commute or a walk is the natural consumption unit. And put the first-week practical episode second rather than last, since it is the one with the highest immediate anxiety payoff and it earns you attention for the rest.Why audio works for this material in the first place is covered in audio learning: why training sticks better in your ears.
What should not go in it#
Being direct about this, because getting it wrong creates real risk:
- Anything requiring a signature. Contracts and policy acknowledgments stay written, full stop.
- Precise figures people need to reference. Salary bands, contribution rates, notice periods, thresholds. Nobody should be scrubbing through audio to check a number.
- Anything that changes frequently. If it needs updating quarterly, it does not belong in an evergreen asset.
- The complete text of any regulated document. Audio is the comprehension layer that sits alongside the written record, never a replacement for it. Say this explicitly inside the episode so nobody treats listening as having read.
- Anything genuinely confidential. Preboarding audio goes to someone who has not started yet and may not join.
The written pack does not disappear. It gets a companion that makes people actually understand it.
Build once, run for years#
The economics here are the opposite of a recurring show, and this is the argument that usually wins internally.
Your onboarding documents already exist. Someone wrote the safety procedure, the benefits summary, and the first-week checklist. The conversion is a one-time project, not an ongoing content commitment. Once built, the series runs for every hire until the underlying policy changes, which for most of this material is annually at most.
That means the cost is bounded and the return scales with hiring volume. An organization hiring 50 people a year gets 50 uses out of one build. At 200 hires, the per-use cost approaches zero.
It also means the maintenance question is manageable: review it once a year alongside your normal policy review cycle, and regenerate only the episodes whose source documents changed.
How to know whether it worked#
Do not measure downloads. A file delivered is not a file heard.
Completion rate per episode, which tells you both consumption and where people drop. If everyone leaves at four minutes into episode four, your safety episode is too long or too dense.
First-week question volume. Ask managers to note the questions new hires ask in week one, before and after. A drop in questions about material covered in the series is the most direct evidence you have that it landed.
Time to make my first meaningful contribution. The ramp metric that actually connects to the money above. Slower to move and noisier than the others, but it is the one that belongs in a budget conversation.
A two-question comprehension check on day one. Not a quiz. Two questions about the things you most need people to know, which also tells you whether the episodes are covering the right material.
90-day retention. Longer feedback loop, but given that roughly 20 percent of turnover happens in the first 45 days, this is where preboarding quality shows up.
Where Sprep fits#
We build a tool for exactly this, so treat this section as an interested party talking rather than neutral advice.
Sprep converts documents you already have- PDFs, decks, Word files- into short two-host conversational podcasts rather than single-voice narration. For onboarding, the important mechanic is the order of operations: the AI drafts a script, a person reviews and approves every word, and only then is audio generated. That review step exists on every plan, including the free one, and for onboarding content it is not optional. Compliance and safety material has to be accurate, and one-shot generation tends to sound polished while getting small details subtly wrong, which you only catch by reading the script.
An approved master script can then be produced in over 70 languages on Team plans, which matters if you hire across sites or countries, because you are approving the content once rather than reviewing nine independently generated versions. Output distributes to Slack, Microsoft Teams, an LMS, or a private podcast feed, and Audio Intent Templates include an Onboarding setting that calibrates pacing and vocabulary for this use case. It is Swiss-hosted, which tends to matter for HR content and data residency questions.Keeping those language versions current as policies change is its own problem, covered in multilingual training at scale without reshooting content.
Dätwyler uses Sprep for onboarding and internal communications.
Where this is the wrong approach: if what your new hires most need is to hear your founder's actual voice and personality, record your founder. If your onboarding problem is that managers are absent in week one, audio will not fix that, and neither will any other content format. And if your source documents are unclear, converting them produces a clear recording of unclear content. Fix the document first.
FAQ#
What is an onboarding podcast? An onboarding podcast, or welcome podcast, is a short finite audio series given to new hires after they accept an offer, covering company context, first-week practicalities, working norms, key safety and policy points, and benefits. It differs from a recurring internal podcast because it is built once and reused for every new hire rather than requiring ongoing episodes.
How long should an onboarding podcast be? Around 45 minutes total, split into four to six episodes of six to twelve minutes each. Individual episodes should fit a single commute or walk. Total runtime matters less than episode length, since a series of short episodes gets finished far more reliably than one long recording.
Does audio actually reduce ramp time? The mechanism is consumption rather than comprehension. Long documents typically see only 20 to 30 percent of readers reach the end, so a large share of preboarding material is never absorbed and gets re-explained in week one. Audio that is actually finished moves that context earlier, which is where the ramp saving comes from. Measure first-week question volume to verify it in your own organization.
Can an onboarding podcast replace our written onboarding documents? No, and it should not be tried. Anything requiring a signature, precise figures people need to reference, and regulated documents must stay written and searchable. The audio is a comprehension layer alongside the written record. It is good practice to state that explicitly within the episodes.
What should go in the first episode? Company context: what the organization actually does, who its customers are, and where the new hire's function fits. Most new starters have only a vague sense of this from interviews, and it is the frame that makes everything else comprehensible. Put the practical first-week episode second, since it carries the highest immediate anxiety payoff.
How much does it cost to produce an onboarding podcast? The main cost with traditional production is time, several hours per finished episode across scripting, recording, editing, and approvals. Document-to-podcast conversion removes the recording and editing steps for material that already exists as a document. Either way, it is a one-time build rather than an ongoing commitment, so cost per use falls with every hire.
How often does an onboarding podcast need updating? Usually annually, aligned with your normal policy review cycle. Because the series covers stable material such as company overview, working norms, and core policies, it does not need the constant refresh a recurring internal show requires. Regenerate only the episodes whose source documents actually changed.
How do you measure whether an onboarding podcast is working? Completion rate per episode rather than downloads, since a delivered file is not a heard file. Then first-week question volume reported by managers, a short comprehension check on day one, time to first meaningful contribution, and 90-day retention. Question volume is the fastest signal and the easiest to collect.
Can we produce it in multiple languages for international hires? Yes, and the efficient pattern is to approve one master script in a language your team can properly review, then generate the language versions from that approved script rather than producing each independently. This keeps the content consistent across sites and means the review burden does not multiply with each language.
Is an onboarding podcast suitable for frontline or deskless workers? It suits them better than most formats, since they cannot easily read a document pack and audio works during commutes or physical tasks. Frontline hires are also frequently the group receiving the largest compliance packs and the least contextual explanation, so the gap it closes is widest there.
Turn your first onboarding document into an episode#
If you want to test the format before committing to a full series, the free plan turns one document into a complete episode of up to 15 minutes, with the script editor included so you can review and correct every word before any audio is generated.
See it in action