Skip to main content
The Salesforce Guides Collection02 published

The Guides

When you need to actually understand a topic, not just look up a number. 1,500 to 5,000 word guides on AI rollouts, technical debt, automation strategy, and how Salesforce really works in production.

Get new guides in your inbox

Free. No spam. Unsubscribe anytime.

Browse by type

CheatsheetsGuidesPlaybooksTemplatesChecklists

The Collection

All Salesforce guides

Deep-dive guides for the topics a cheatsheet can't compress. Read on page or grab the PDF. Free.

Salesforce Technical DebtMay 7, 2026

Fixing Salesforce Technical Debt With AI: A Complete Guide

A 10-chapter guide for admins and the leadership teams who fund them. Worksheets, AI prompts, and a 90-day plan to audit, prioritize, and fix Salesforce technical debt.

  • 10 chapters covering audit, prioritization, and fix patterns for the most common Salesforce technical debt
  • Worksheets for mapping unused fields, redundant automation, and stale reports
  • AI prompts for org analysis at scale
  • 90-day execution plan with weekly checkpoints
Built forAdminsArchitectsLeaders
Read this guidePDF
Salesforce AI12 min readMay 6, 2026

The AI Automation Guide for Salesforce Admins

A practitioner's guide to using AI to automate the day-to-day Salesforce admin work, flows, data hygiene, user management, and reporting, without rewriting your org.

  • Where AI actually saves time vs. where it adds noise
  • Prompt patterns that work for flow building, data cleaning, and user permissions
  • Guardrails: what to keep human-in-the-loop and why
  • A 30/60/90 plan for rolling AI out across an admin team
Built forAdminsRevops
Read this guide

More guides ship every quarter

Agentforce rollout guide, technical-debt remediation guide, and a managed-services buying guide are next.

See roadmap

Quick answer

What's the difference between a Clientell guide and a generic Salesforce blog post?

Generic blog posts list features. Our guides take a position. Every guide ships with a thesis (what to do and why), real numbers from production orgs, worksheets you fill in, AI prompts you copy, and a 30 to 90 day execution plan. Read once, ship for months.

Length
1,500 to 5,000 words
Includes
Worksheets + prompts
Format
Read on-page or grab the PDF

About these guides

Why these guides exist

The internet is drowning in “Salesforce best practices” SEO chum. Most of it is generic, hedge-everything content built to rank, not to ship. You read 3,000 words and walk away with “it depends” as your strongest takeaway.

These guides take the opposite approach. Each one starts with a specific position (what we think the right answer is, given a real production constraint) and defends it with sourced numbers, frameworks you can actually run, and the AI prompts that compress weeks of work into hours. You can disagree with the position. You can't disagree that it's actually a position.

67% of Salesforce admins say technical debt is their #1 daily challenge. Not reports. Not user requests. Not even Flows. The invisible compounding mess that makes every 'simple change' take three times longer than it should.
Source: Clientell technical debt audit data, 100+ orgs, 2024 to 2026

If you read a guide and think “I already knew that,” we shipped a bad guide. Tell us. The bar is shipping the kind of long-form content that makes you re-think a system or pattern, not the kind that confirms what you already do.

What makes a good Salesforce guide

We have rules for what makes the cut. If a guide doesn't pass all four, it doesn't ship.

  1. #01

    One thesis, defended specifically.

    Every guide has a load-bearing claim in the first 500 words. The rest of the guide defends it with numbers, examples, and counter-arguments addressed head-on. No “it depends” cop-outs.

  2. #02

    Cited numbers, not vibes.

    Every statistic has a source and a year. Every cost range has a methodology note. Every framework has a worked example from a real production org. The reader can verify any claim in under 30 seconds.

  3. #03

    Worksheets, not just prose.

    Most guides include at least one worksheet, prompt library, or execution template you can copy into your work. The reader leaves with an artifact, not just an opinion.

  4. #04

    Updated when the platform shifts.

    Salesforce moves. Pricing changes. APIs deprecate. Each guide shows its updated date and gets re-read when a major release lands. Stale guides are worse than no guides.

How to actually get value from a long-form guide

A 4,000-word guide is only useful if you do something with it. Most readers skim once, bookmark, and forget. The guides are designed to support a different pattern.

Three reading patterns that compound

  1. #01

    Read once cold, mark up the worksheet.

    First pass, read the whole guide. Don't action anything yet. Just mark which framework or worksheet maps to a problem you have right now. The worksheets are calibrated to be the highest-leverage 20%.

  2. #02

    Run the worksheet against your org the next workday.

    Don't let the guide age in your bookmarks for two weeks. Block 30 to 60 minutes the next workday and run the actual exercise (audit, scoring, prompt sequence). Friction kills follow-through; momentum doesn't.

  3. #03

    Re-read the guide quarterly.

    Salesforce releases land in February, June, October. Re-read the guide in the week after each release. Most guides have a 'what changed' callout we update with each refresh.

What not to do

  • ✕Don't share a guide as a Slack link without context. Link to the specific worksheet section. Decision-makers don't read 4,000 words on demand.
  • ✕Don't treat a guide as a substitute for a real audit of your org. The guide gives you frameworks; your org gives you the answers. Use both.
  • ✕Don't memorize the prose. Memorize where the framework lives. Future you will pull up the guide, find the worksheet, and re-run it.

What's coming next

Each guide takes 4 to 8 weeks of writing + production-validation work. The next batch covers the topics our customers keep asking us to write up.

  • Q3 2026

    Salesforce Permission Migration Guide

    End-to-end profile-to-permission-set migration for orgs that have been on profiles since 2018. Includes the audit script and the 90-day rollout.

  • Q3 2026

    Salesforce Data Cleanup at Scale

    The 4-quadrant cleanup framework, the AI prompts that compress dedup work by 5x, and the governance pattern that keeps it clean.

  • Q4 2026

    Salesforce-to-Snowflake Sync Architecture

    When to sync, what to sync, how to keep the sync idempotent, and the 6 patterns we've seen break in production.

  • Q4 2026

    RevOps Forecasting on Salesforce

    The forecast hygiene model that predicts within 8% variance quarter over quarter, plus the dashboards that surface drift.

If a topic you'd value isn't on the roadmap, send it via the contact form. We add 1 to 2 community-requested topics per quarter.

Related06 / 06 resources

More from the library

Six adjacent surfaces inside the Clientell library. Each one shows the same Salesforce topic from a different angle. Pick the format that matches the work you're about to do.

Frequently asked

Questions, answered

How is a guide different from a blog post?

Blog posts run 600 to 1,500 words and cover one specific take or news item. Guides run 1,500 to 5,000 words, ship with worksheets and prompts, and are designed to be re-read quarterly. If you can finish it in one cup of coffee and walk away with a single takeaway, it's a blog post.

Are the guides gated?

The on-page version is free to read. PDFs are available for download in exchange for an email address (work email; we don't accept gmail/yahoo for the gated download). The exact same content lives in both formats.

Who writes the guides?

Clientell engineers and senior consultants who've shipped the pattern in production. Every guide names the author and includes their LinkedIn so you can verify the experience claims.

Can I excerpt a guide on my company blog?

Yes, with attribution back to the original page. Up to 30% of the content is fine to quote. Beyond that, link to the source.

How often are guides updated?

Major guides are reviewed every 3 to 6 months. After each Salesforce major release, the affected guides get a 'what changed' callout. The frontmatter shows the last-updated date.

Are these specific to a Salesforce edition?

Most guides target Enterprise Edition by default and call out where Professional / Unlimited differ. We don't write guides for Essentials because Essentials orgs grow into Enterprise inside 18 months in our data.

Can I get a 1:1 walkthrough of a guide?

Book a 30-minute working session via the demo link. We'll walk through the guide's worksheet against your specific org. Useful when the guide's framework needs adapting to your edge cases.

Do you write guides on competitor tools?

Yes. We've published comparison guides on Sweep, Cirra, Copado, Agentforce, and others. They're framed honestly: when each is the right call, and when it isn't.

Getting Started

Read the guide. Then run the worksheet.

Long-form guides only matter if you ship the work. Hand the actual configuration to Clientell AI and run the worksheet end-to-end in days, not quarters.

Start free trialTalk to Sales

Unlimited messages  ·  No credit card required

SOC 2
HIPAA
GDPR
Salesforce Partner