Why SaaS onboarding is hard
SaaS companies ship product weekly. By the time a rep finishes the onboarding deck written six months ago, half the positioning is already stale. Engineering wikis suffer the same fate — new hires read a system diagram that no longer matches the production architecture. The result is the most expensive form of onboarding waste: a new employee who spends month one learning things they will have to unlearn in month two.
The fix is not "write better static training." Static training is the problem. The fix is to make onboarding a function of your living source documents — the product wiki, the GTM playbook, the security policy — and regenerate the kit every time those documents change.
What Kompyl reads at SaaS companies
Customers in SaaS most often feed Kompyl four document types:
- Product wiki / handbook — feature catalogue, positioning, ICP definitions
- GTM playbook — discovery questions, objection handling, pricing, competitive battlecards
- Engineering README + RFC archive — repo layout, code review norms, deploy process, on-call runbook
- Security policy — SOC 2 controls, access provisioning, incident response, data classification
Each becomes a slide deck plus a quiz plus flashcards plus a facilitator guide, all aligned to the same source. When the wiki changes, you regenerate; the kit stays in sync without a content-ops headcount.
Ramp metrics SaaS teams actually move
Kompyl customers in SaaS measure four KPIs against onboarding kits:
- Time-to-first-PR for engineers, typically 2–3 weeks shorter when day-one training is generated from the current README rather than a stale Notion page.
- Time-to-first-deal for AEs — proportional to the freshness of the discovery script and battlecards. Auto-regenerating the kit on every product release closes the gap.
- Ramp-to-quota at 90 days. Roleplays and quiz coverage of the ICP move this most.
- 30-day NPS from new hires. Async-friendly kits (slides + study guide + flashcards) score higher than live-session-only onboarding.
Where this fits if you already have a tool
Kompyl is not an LMS. If you use WorkRamp, Lessonly, or Trainual, Kompyl produces the source content — PPTX, CSV quizzes, study guides — that you upload there. If you use Notion or Drive as a knowledge base, Kompyl outputs the same content as embedded slides and downloadable assets. The output works with whatever you already deliver in.
For a deeper walkthrough of the pipeline, see the employee onboarding training generator overview, the new hire training generator, or the remote onboarding guide for distributed engineering teams.