Name the six objects
Company, Contact, Lead, Deal, Line Items, Quote — what each one is, and which one a given situation belongs in.
We train in the seller's own portal, on their own records — six objects, one daily rhythm, and a written minimum standard everyone is held to.
Training is scoped to behaviour, not features. If a screen does not change what a rep does on Monday, it is not in the session.
Company, Contact, Lead, Deal, Line Items, Quote — what each one is, and which one a given situation belongs in.
Notification to lead record, activity logged, qualified, deal created, line items added, quote sent, stage moved, closed won.
Five steps, same order every morning, so nothing sits and nothing gets rediscovered a week late.
The written behaviours managers inspect — follow-up windows, stage movement, next steps, amounts and close dates.
Select an object to see how we teach it — the definition, the example, and the rule that stops it being confused with the one next to it.
The organisation you are selling to. Contacts work at companies, and every deal ultimately belongs to one.
This is the slide reps quote back weeks later. Their real deal on the left, the object it creates on the right.
Not a script to follow — just a few of the moments from the session, in the rep's own portal. Pick a screen.
Adoption is not a feelings problem. Both halves get published in writing on the day of training.
"Can I reasonably estimate revenue right now?"
HubSpot's Playbooks Analyze tab reports licensed users against active users, so a week after training you can name who is running the call guide and who is not.
The headline number, reviewed weekly by team. Under 50% two weeks after launch triggers a manager conversation, not another training invite.
Total views tells you reps found it. Total logs tells you they completed it on a live call. The gap between the two names the fix.
The User Data drill-down lists usage per rep, so the weekly coaching agenda starts with people rather than percentages.
We hand this dashboard to managers on day one of the rollout, with a named owner and a weekly slot. A playbook nobody inspects gets used for about two weeks.
So the mobile app gets its own module: creating and completing tasks, reviewing leads, and logging a call in the car park before the detail fades.
Create from the + button, set type and due date, associate the record, save. Complete with the checkmark from the Due tasks tab. Filter by type, sort by due date or priority.
The same views as desktop, so nothing waits for the drive home. Walkthrough videos ship with the deck for navigation and task management.
One page for the six objects, one for the daily rhythm, one for the minimum standard, plus step-by-step cards for creating contacts, leads, deals and line items.
One page per task, written in the order the clicks happen. Six of the set, previewed below.
Reps get the full set plus the session recording — so nobody has to remember what was said in the room, and the next hire starts from the same page.
A pre-training checklist goes out with instructions and video. Reps arrive with a working portal.
Every rep verifies they can log in and holds the right seat before the invite is accepted.
Connected inbox plus inbox automation switched on, so email logs itself against the record instead of relying on memory.
Calling integration connected and demonstrated live, so a logged call is one click rather than a form.
We build the deck against your pipeline, your stages and your products, run it live with your reps, and hand over the cheat sheets and recordings so the next hire gets the same session. Managers get their own version — inspection, not features.
Contact us Screens above are from a live training portal. Records and names are demonstration data.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.
