You are the onboarding, and it does not scale
The questions repeat across every client and every new hire they add. You answer each one personally, and the third time the same one arrives, you answer with a calm you do not feel.
The Same Questions
Where do I log in, who owns this, what happens first. Every onboarding asks them, and the answers do not change.
In Your Name
Each answer comes from you personally, so onboarding stalls whenever you are busy. The knowledge lives in your sent folder, not anywhere a client can reach.
One hub the client can read without asking
Publish onboarding as a hub with the client's brand. New people read it in order instead of waiting on you.
Capture It Once
Record each setup process with the capture extension while you do it. Each click becomes a step with the screenshot attached, and a typed value files as the field name, never the password or card number behind it.
Guides And SOPs
Order the onboarding as guides for the person doing each task and SOPs for the person running the work. Change a guide once and every SOP that embeds it is current.
Their Own Address
The hub carries the client's logo, accent, and wording. Onboarding reads as theirs, not as a document you forwarded.
The question you did not document, handled
Doc AI answers from that hub's published docs, cites the guide and step, and opens a ticket instead of guessing when the docs don't cover it.
Answers In Their Words
A new hire asks in plain language and Doc replies from the onboarding docs, pointing to the exact guide and step.
Gaps Become Tickets
What the docs don't cover becomes a ticket in your Inbox — the strongest signal there is about the next guide to write.
Ready to write it once?
Capture a process, publish it as a help center under your own name or a client's, and answer the repeat questions from what you published.