Support · User training

User training

Most software rollouts fail not at the build, but at adoption. The system is fine. The training was one 90-minute Zoom on a Tuesday afternoon four months ago. Nobody can find the slides. New joiners are taught by whoever happens to be free, in whatever order they remember.

We treat training as a deliverable, not an afterthought. Recorded sessions per role, written SOPs that survive turnover, an FAQ page indexed by role, and a month of 'office hours' so questions get answered in real time, not buried.

Bundled with build · 2–3 weeks of training material
Inside the build

What's actually included.

Role-based sessions

Separate sessions for sales, finance, ops, admin, and managers, each focused on the parts of the system that role actually touches.

Recorded + transcribed

Every session recorded with chapter markers and an auto-generated transcript. New hires next quarter watch the same thing the original team watched.

Written SOPs

Step-by-step SOPs for the top 10 workflows per role, with screenshots and decision trees. Editable by your team after handover.

Role-indexed FAQ

FAQ page filterable by role: sales sees sales questions, finance sees finance questions. Searchable from inside the app.

Office hours

Weekly drop-in over Teams or Meet for the first month after go-live, answering live questions. Repeats of common questions feed back into the FAQ.

Train-the-trainer

One designated owner per team is trained as the internal champion. They handle quarterly refreshers without us needing to be in the room.

Who this is for

Any team going live on new software where adoption matters and where roles are differentiated (e.g., sales vs. ops vs. finance). Especially valuable when 'we already did training and people still don't use it' has happened before.

How we work

Three stages, no surprises.

01

Discovery

A 30-minute call to map the workflow that's actually broken. We walk you through what we'd build, what we wouldn't, and a written scope with timeline and milestones.

02

Weekly sprints

Working prototype by week 2, MVP in staging by week 4–6. Friday demo every week: you see it before it's done, not after. Slack channel + Linear / Jira board you have access to.

03

Handover + retainer

Go-live with a written playbook, training material per role, and a 30-day office-hours window. Most clients move onto a maintenance retainer for the work that comes after.

Ready to start

Walk us through what's broken.
We'll come back with a plan.

A 30-minute discovery call, free, no deck. We map your workflow, flag what's worth fixing first, and outline a scope with timeline and effort.