Playbooks
Step-by-step playbooks built around real Salesforce roles. Not theory. The exact moves admins, developers, RevOps leads, and architects use to ship outcomes that compound. Each playbook is a calendar, not a treatise.
Get new playbooks in your inbox
Free. No spam. Unsubscribe anytime.
Browse by type
Quick answer
What's the difference between a playbook and a guide?
A guide explains a topic. A playbook gives you a calendar. Open week 1, run the moves, hit the checkpoint, advance to week 2. Playbooks ship around roles (admin, developer, RevOps) and outcomes (becoming AI-enabled, fixing technical debt, leading a migration). They expire when the playbook completes.
- Format
- Week-by-week calendar
- Length
- 8 to 12 chapters per playbook
- Built for
- One specific role + outcome
Origin
Why these playbooks exist
Most career advice in Salesforce is opinion, not playbook. “Get certified.” “Learn AI.” “Network on LinkedIn.” All true, none operational. You finish reading and have no idea what to do this week.
These playbooks fix that. Each one is a 12-week (or 90-day, or quarterly) calendar for a specific role and outcome. Week 1 has specific moves. So does week 8. So does week 12. You can pick up the playbook on a Monday morning and know exactly what to do that day.
71% of admins use AI tools. Only 32.4% feel confident doing it. The 38.6-point gap is where careers get made or broken in 2026, and it closes in 90 days when you have a calendar instead of a syllabus.
If you read a playbook and walk away thinking “I'd need to figure out what to actually do tomorrow,” we shipped a bad playbook. Tell us. The bar is operational, not inspirational.
Quality bar
What makes a good Salesforce playbook
We have rules for what makes the cut. If a playbook doesn't pass all four, it doesn't ship.
- #01
One role, one outcome.
Each playbook targets a specific role (admin, developer, RevOps lead, architect) and a specific outcome (becoming AI-enabled, leading a migration, fixing technical debt). No multi-role, multi-outcome generalities.
- #02
Calendar, not chapter.
Every playbook is structured as week-by-week or phase-by-phase moves. The reader can tell you what to do on a specific day, not just what to “think about over time.”
- #03
Checkpoints between phases.
Each phase ends with a measurable checkpoint (skill demonstrated, artifact built, milestone hit). If you can't pass the checkpoint, you re-run the phase. No “move on regardless.”
- #04
Assumes you have a job to do.
Playbooks are written for working professionals, not students. Phases respect 8-hour workdays and 40-hour weeks. No “spend 20 hours this week reading documentation.”
State of the library
What's published today
Each playbook takes 6 to 10 weeks to write because we run them on real cohorts before publishing. We publish 1 to 2 per quarter.
| Title | Best for | Format |
|---|---|---|
| The 2026 Playbook for Becoming an AI-Enabled Salesforce Admin | Admins | PDF + on-page |
| The Salesforce Developer's AI Playbook | Developers, Architects | On-page |
Want a playbook for a specific role or outcome? Tell us via the contact form. The next playbook usually goes to whichever role asks for it most.
Workflow
How to actually run a playbook
Playbooks fail when readers treat them as inspiration. They work when readers treat them as a calendar.
Three patterns that compound
- #01
Block calendar time before you start.
Open the playbook. Look at the week-by-week structure. Block the time on your calendar (2 to 5 hours per week is typical). Make it recurring. The playbook only works if the time exists.
- #02
Run the checkpoints honestly.
Each phase ends with a measurable checkpoint. If you can't demonstrate the skill or produce the artifact, you didn't finish that phase. Re-running a phase isn't failure; skipping it and pretending you did is.
- #03
Pair up if you can.
Playbooks are 2x more likely to finish when run with a peer. Find a colleague (or a friend in another company) running the same playbook and check in weekly. The accountability does most of the work.
What not to do
- ✕Don't speed-read the playbook in one sitting and call it done. The whole point is the calendar. Speed-reading is the same as not reading.
- ✕Don't skip phases that look easy. The “easy” phases usually contain the foundational work the later phases assume. Skipping costs you more time downstream.
- ✕Don't run multiple playbooks simultaneously. One playbook at a time, finish it, then start the next. Multitasking playbooks is multitasking learning, which doesn't work.
Roadmap
What's coming next
The next batch covers the role-and-outcome combinations our customers keep asking for.
- Q3 2026
RevOps Lead Playbook
12-week playbook for RevOps leaders integrating AI into the forecast cadence, pipeline hygiene, and quota planning.
- Q3 2026
Salesforce Architect AI Playbook
10-week playbook for architects scoping multi-org AI rollouts, including the security review framework and the cross-org governance pattern.
- Q4 2026
Solo Admin Survival Playbook
Specific playbook for admins running 100+ user orgs alone. The triage system, the AI agent setup, the upward-management script that gets you a second admin.
- Q4 2026
Agentforce Rollout Playbook
90-day playbook for org-wide Agentforce deployment, including the user-acceptance gates and the credit-budget thresholds.
If a role-outcome combination you'd value isn't here, send it via the contact form. The first 5 to 10 community requests for the same combination move it to the front.
Related
More from the library
Salesforce guides library
Long-form learning, not calendarized
Salesforce cheatsheets
Single-page references during a playbook run
Salesforce templates
The artifacts the playbooks reference
Clientell blog
Shorter takes between playbooks
Free Salesforce health check
Diagnostic to run before starting a playbook
Customer stories
Teams who ran the playbooks and shipped
Frequently asked
Questions, answered
How long does a typical playbook take?
Most playbooks are 8 to 12 weeks of part-time work (2 to 5 hours per week). The fastest is 30 days, the longest is 90. Each playbook tells you the time commitment up front.
Can I run a playbook on my own without coaching?
Yes. Every playbook is self-paced and includes the worksheets, prompts, and checkpoints needed to run solo. About 30% of readers run with a peer; the rest run alone.
Are playbooks gated?
On-page reading is free. PDF download requires a work email. Everything in the PDF is also on-page; the PDF exists for offline / printable use.
How are playbooks updated?
Quarterly. After each Salesforce major release we re-run the playbook against the new platform behavior and update affected phases.
Do you offer playbook coaching?
Yes, paid. Book a 30-minute scoping call via the demo link. Coaching is hourly, optional, and only useful if you've already run the playbook self-paced for 2+ weeks and hit a specific blocker.
What if I need to skip a phase?
Read the phase description carefully. Some phases have prerequisite work the later phases assume; others are optional. The playbook calls out which is which.
Can I share a playbook with my team?
Yes. Share the on-page URL. For team-wide print distribution, get the PDF via the email-gated download.
Do you sell playbooks for specific industries?
Most playbooks are industry-neutral. Where industry matters (healthcare for HIPAA, financial services for SEC), we call out the variations inline. Custom industry playbooks are available as a paid engagement.
Run the playbook. Ship the outcome.
Playbooks only work if the time exists. Hand the routine config work to Clientell AI so the calendar slots stay open for the work that needs your judgment.
Unlimited messages · No credit card required