Salesforce · Training & Playbook

Salesforce training that leaves a Playbook embedded in your org.

Generic Salesforce training fades the week after the workshop because it teaches the platform, not your configuration. Ours doesn't — every engagement produces a custom Playbook authored to your fields, processes, and reports, then embedded inside Salesforce where the work happens. Live training delivers it. The Playbook keeps it.

Schedule a training scoping call

Custom Playbook · embedded in Salesforce · authored to your config.

Playbook open in the Salesforce utility bar

How the engagement works

Four steps. Live training first, embedded Playbook second, group rollout last.

We compress the live work into one to two weeks of training and curriculum, then take another two to three weeks to author and embed the Playbook before the broader rollout.

i

Discovery

We meet your admins and process owners, review the parts of Salesforce that matter to your business, and confirm the team we'll be training.

ii

Custom curriculum & live training

We author a curriculum keyed to your configuration and deliver instructor-led sessions — in-person, virtual, or hybrid, recorded for async replay.

iii

Playbook build & Salesforce embed

Every walkthrough becomes a section in your Playbook — written to your fields, your reports, your automations — and deployed inside Salesforce so every user can reach it.

iv

Group rollout sessions

We run group session(s) anchored on the Playbook to bring the broader team onto the same source of truth — no separate decks, no diverging notes.

The Playbook, section by section

Your org's instruction manual, embedded where the work happens.

Every Playbook follows the same six-section structure so anyone in your org can find what they need in seconds. The contents are custom to your configuration — your objects, your stages, your reports, your automations — and the document lives inside Salesforce, not on a shared drive nobody opens.

§01 · Object & process walkthroughs

Every standard and custom object, every lifecycle, in plain English.

The opening section walks through how records move through your org — Lead to Opportunity to Order, Case lifecycles, Account hierarchies. Each stage is documented with the fields that matter, who owns the transition, and what the downstream effects are. Written so a new hire can read it before their first deal.

Sales lifecycle — sample entry
Stage 4 → Stage 5 requires a signed order form attached to the Opportunity. The transition fires the NetSuite handoff; do not advance until the form is on file.
Lifecycle · Lead → Opportunity → Order
Lead
Key fields
Source · Owner · Status
Stage transition rules
Opportunity
Key fields
Stage · Amount · Close date
Stage transition rules
Order
Key fields
Pricebook · Terms · Renewal date

§02 · Role-based workflows

Day-in-the-life walkthroughs for every role you train.

One section per role — AE, SDR, Sales Manager, CSM, Service Agent, Admin — each with the daily and weekly motions in your Salesforce. Tasks are timestamped, list views are linked, and required fields are called out. Replaces the tribal knowledge that walks out the door when someone leaves.

AE workflow — sample
Morning ritual: open My Pipeline · This Week, log activity on every Opp touched yesterday, advance any stage with the close-date check before the 9:30 standup.
AE · Day-in-the-life
  1. 8:30
    Review pipeline list view
    Opps closing this week, by stage
  2. 9:00
    Log calls + meeting notes
    Activity timeline on Opp + Account
  3. 11:00
    Advance opportunity stages
    Required-fields check before stage 4
  4. 14:00
    Update forecast category
    Commit / Best Case / Pipeline

§03 · Reports & dashboards guide

What every saved report means and when to use it.

An indexed catalog of the reports and dashboards that matter — what each one is measuring, who reads it, what to do with the answer, and which folder it lives in. Eliminates the report sprawl problem where teams build the same view three times because nobody knew it already existed.

Forecast report — sample
Forecast Roll-up reads from the forecast category, not stage. This is the source of truth on the weekly call — if it disagrees with your gut, the data wins or you change the category.
Saved reports · what each one means
Pipeline by Stage
Read by sales leaders Mondays. Excludes Closed Lost.
Aging Open Opps
Anything > 45 days in current stage flagged red.
Forecast Roll-up
Pulled from forecast category, not stage. Source of truth for the call.
Indexed by folder · linked from the Playbook

§04 · Automation reference

Flows, triggers, validation rules — explained for humans.

The automation section translates your declarative and code automation into plain language. Every Flow, trigger, and validation rule gets a human-readable explanation of what it does, when it fires, and what blocks it. So when someone asks “why can’t I save?” the answer is one click away.

Validation rule — sample
Required_Close_Reason blocks save on Closed Lost until a reason is selected. The rule exists to keep the loss-reason report honest; do not work around it with a generic value.
Automation · in plain English
FlowOpportunity_Stage_Notifier
When stage moves to Negotiation, ping the deal channel and the AM.
Validation RuleRequired_Close_Reason
Closed Lost requires a reason picklist. Blocks save until set.
TriggerAuto_Assign_New_Lead
New web leads route to the rep on call for that territory.

§05 · Integration map

Connected systems, what flows where, who owns the connector.

A map of every system Salesforce talks to — ERP, marketing automation, billing, support, custom apps — with the direction of data flow, the trigger, and the owner of the connector. So when a sync breaks, the team knows where to look and who to call instead of opening five tickets.

NetSuite sync — sample
Closed-Won → NetSuite Sales Order fires within five minutes of stage change. Owner: RevOps. If the SO doesn’t appear, check the integration log before re-saving the Opp.
Integration map · what flows where
Salesforce→NetSuiteClosed-Won → Sales Order
NetSuite→SalesforceInvoice status, paid date
Salesforce↔MarketingLead sync + campaign attribution
Salesforce→BillingSubscription start, MRR
Each line links to its connector + owner

§06 · Onboarding tracks

Day-1, Week-1, Month-1 paths for every new hire.

Each role gets a structured ramp — what to log in to on Day 1, what to shadow in Week 1, what to own by the end of Month 1, and what the admin sign-off looks like at each gate. Turns onboarding from a calendar invite into a curriculum, and gives managers a checklist instead of a vibe.

AE ramp — sample
By end of Week 1 a new AE has logged their first ten activities, run the pipeline report unaided, and shadowed three live deals end-to-end. Admin signs off before territory assignment.
New-hire ramp · AE track
Day 1
  • Account login + MFA
  • Lightning tour
  • Read your role section
Week 1
  • Shadow 3 live deals
  • Log first 10 activities
  • Run pipeline report
Month 1
  • Own a territory
  • Pass admin sign-off
  • Lead a forecast call

Frequently asked

What teams ask before they engage

Not sure where to start? A CRM Health Check often surfaces the gaps that seed the first Playbook sections — many engagements start there.

Tell us about your Salesforce training and Playbook needs

We confirm fit, scope the engagement, and send a statement of work — typically within two business days.