Step 1
Say what needs to happen
One sentence, in your own words.
- Describe the outcome, not a topic
- Drop in help docs, tickets, a recording — mess is fine
- Or start from one of the four common jobs
What do you need your team to do?
Tell us the outcome. We read your material and build the knowledge base that gets you there.
You'll get: A 3-week onboarding playbook, built from how your team already works.
Free until you send something to a colleague — then per team, not per person. What it costs
How it works in 3 steps
The knowledge base is the middle step — the part everything else is built on.
Step 2
Check the knowledge base
What your team must be able to do, drawn from your material.
- Skill sets, then skills underneath — never a flat list
- A real example from your own work on each skill
- Gaps stated plainly, never padded out
Step 3
Hand out a playbook
You judge the draft. You never have to write it.
- Several shapes per job — thorough or fast, you choose
- Corrections become house rules for everything after
- Results come back for the group, never per person
One knowledge base, every use case
The same material, pointed at whatever you're trying to get done this month.
Employee onboarding
Get a new hire useful in days, not months
One structured path per role, built from how your team already works — not from a template someone downloaded.
- A playbook drafted from your own tickets and docs
- Thorough or fast-track — you pick the trade-off
- Real examples, so they can see what good looks like
- Progress reported for the group, never as a ranking
The knowledge base your team will actually use
Four things it does that a folder of documents cannot.
Everything your team knows, in one structured place
Help docs, tickets, recordings and the doc nobody updated go in. Skill sets and skills come out — grouped, ordered, and traceable.
Knowledge base · 4 sourcesExample
Diagnosing integration problems3/4
Talking about money1/3
Setting expectations3/3
Knowing when to escalate2/4
Why this skill set matters
Nearly half of everything your team touches, and where almost all the escalations come from.
40% of your tickets are sync failures. The October meeting names this as the bottleneck.
from zendesk-resolved-oct.csv · team-meeting-oct.vtt
Frequently asked questions
Someone starts Monday.
Ten minutes now, and they have a playbook built from how your team actually works.
Free until you send something to a colleague — then per team, not per person.