A discovery question bank for Salesforce consultants — built from real implementations, not documentation.

6 clouds · 238 questions · 55 bridge questions for multi-workstream projects

Built from live implementations across Sales Cloud, Service Cloud, CPQ, Agentforce, B2B Commerce, and Experience Cloud. Not theory. Not documentation. Real projects.

Sales Cloud · Service Cloud · CPQ · Agentforce · B2B Commerce · Data Cloud · Field Service · Experience Cloud · Sales Cloud · Service Cloud · CPQ · Agentforce · B2B Commerce · Data Cloud · Field Service · Experience Cloud ·

Scope creep starts in discovery.

0 average cost increase from a missed discovery decision
0 of CRM users can't quantify the business impact of their implementation
0 when most teams discover the architecture decision they should have made in week 1

These packs exist to surface the decisions that, if deferred, become the most expensive conversations on the project. Every question was born from a real implementation — every gotcha from a real mistake.

Every question is built the same way.

01 — The Question

"Do you sell to individual consumers, businesses, or both?"

⚠ Gotcha

Person Accounts is an irreversible org-level setting. Once enabled, it cannot be turned off. Many consultants discover the client sells B2C mid-project — after page layouts and flows are already built for the standard model.

Why This Matters Early

This is the single most consequential data model decision in a Sales Cloud implementation. It must be answered before any object, layout, or automation work begins.

🔗 Bridge Question — Sales Cloud + Agentforce

"If an Agentforce SDR agent is qualifying inbound leads, does the client need Person Accounts enabled for B2C interactions — and has that been communicated to the Agentforce workstream for prompt design?"

Cross-workstream alignment ensures the data model decision propagates to every dependent build.

One pack per cloud. All six in the bundle.

Sales Cloud

  • 55 questions across 14 sections + 12 bridge questions
  • Person Accounts is irreversible. Custom Fiscal Year is irreversible.
  • Einstein Lead Scoring requires 1,000 converted + 1,000 not-converted leads
  • Territory Management locks you into a single active model
Multi-currency activation is largely irreversible. Opportunity Splits must total 100% — Revenue Splits and Overlay Splits are different things.

Service Cloud

  • 53 questions across 13 sections + 10 bridge questions
  • Classic Chat (Live Agent) retired February 2026 — new chat must use MIAW
  • Entitlement Milestones are NOT auto-completed — they require Apex or Flow
  • Omni Supervisor must be explicitly added to Service Console — not there by default
Business Hours must be configured before Entitlement Processes or SLA timers will be wrong from day one. WhatsApp takes 3–7 days, SMS short codes take 6–8 weeks.

CPQ

  • 32 questions across 10 sections + 5 bridge questions
  • CPQ reached End of Sale June 2025 — Revenue Cloud is the successor
  • Amendment quote lines have Additional Discount locked — cannot reprice
  • Standard Data Loader is not safe for CPQ data migration — use Prodly or Gearset
Revenue Cloud is not an upgrade — it's a migration. Required bundle components appear as visible line items on customer-facing quotes.

Agentforce

  • 30 questions across 10 sections + 6 bridge questions
  • Every Action is a development item. Topic instructions are LLM-interpreted.
  • Flex Credits at $2/credit — high-volume agents produce budget surprises
  • UAT must use quality scoring, not binary pass/fail (non-deterministic outputs)
The Einstein Trust Layer masks PII in logs but does NOT prevent sensitive data from appearing in conversational responses. Agentforce Voice requires Amazon Connect.

B2B Commerce

  • 30 questions across 10 sections + 5 bridge questions
  • Aura-to-LWR is a rebuild — no Aura component is reusable
  • Standard checkout supports a single Ship-To address — multi-ship is custom
  • LWR page layouts do not deploy via Change Sets — requires Salesforce CLI
The order-to-ERP integration is the most consistently underestimated workstream. B2B Commerce has no native purchase approval workflow — it's custom dev.

Experience Cloud

  • 38 questions across 12 sections + 6 bridge questions
  • Template selection is irreversible — switching requires rebuilding the site
  • Guest user "API Enabled" permission enables attackers to query CRM data (active exploit)
  • Partner Central is Aura-only — no LWR PRM template exists as of early 2026
CMS Workspace languages must be configured at creation — you cannot add a language retroactively. Mobile Publisher requires 4–6 week App Store lead time.

Real questions. Real gotchas. See for yourself.

Sales Cloud Discovery

55 questions · 14 sections · 12 bridge patterns

Data model decisions, forecasting architecture, lead routing, territory management, Einstein Activity Capture, Sales Engagement, and the irreversible choices that define every Sales Cloud build.

1Data Model & Account ArchitectureQ1–Q4
2Lead ManagementQ5–Q8
3Opportunity Management & PipelineQ9–Q12
4ForecastingQ13–Q16
5Einstein Activity CaptureQ17–Q19
6Territory ManagementQ20–Q22
7Sales Engagement & CadencesQ23–Q26
8Enablement & CoachingQ27–Q29
9Quota ManagementQ30–Q32
10Reporting & AnalyticsQ33–Q36
11Campaign AttributionQ37–Q39
12Integrations & Tech StackQ40–Q43
13User AdoptionQ44–Q47
14Mobile & Field SalesQ48–Q55
Sample Question Preview Sales Cloud · Q1
Q > Do you sell to individual consumers, businesses, or both?

⚠ GOTCHA: Person Accounts is an irreversible org-level setting. Once enabled, it cannot be turned off. Many consultants discover the client sells B2C mid-project — after page layouts and flows are already built for the standard Contact/Account model.

WHY EARLY: This is the single most consequential data model decision in a Sales Cloud implementation. It must be answered before any object, layout, or automation work begins.

🔗 BRIDGE → Agentforce SDR: If an AI agent is qualifying inbound leads, Person Account status must be communicated to the Agentforce workstream for prompt design and topic classification.
55Discovery Questions
55Gotcha Warnings
12Bridge Patterns
PDF + NotionDelivered As

Service Cloud Discovery

53 questions · 13 sections · 10 bridge patterns

Omni-Channel routing, SLA enforcement, Knowledge taxonomy, Classic Chat retirement, Digital Engagement, telephony, Einstein AI, and the configuration gaps that surface on the first weekend after go-live.

1Case Intake & Channel ArchitectureQ1–Q4
2Omni-Channel RoutingQ5–Q8
3Case Management & WorkflowQ9–Q12
4SLAs, Entitlements & Service ContractsQ13–Q16
5Knowledge ManagementQ17–Q20
6Digital Engagement & ChatQ21–Q24
7Telephony & Service Cloud VoiceQ25–Q28
8Einstein AI for ServiceQ29–Q32
9Service Console & Agent ProductivityQ33–Q36
10Reporting, Analytics & Service KPIsQ37–Q40
11Field Service IntegrationQ41–Q44
12Integrations & Tech StackQ45–Q48
13Adoption, Training & Change ManagementQ49–Q53
Sample Question Preview Service Cloud · Q7
Q > Does the organization have defined SLAs for case resolution, and do those SLAs vary by customer tier, product, or support channel?

⚠ GOTCHA: SLA timers in Entitlement Management do not pause for weekends or holidays unless Business Hours records are explicitly configured and assigned to the entitlement process. A case created Friday at 11 PM will breach its 4-hour milestone by 3 AM Saturday unless Business Hours governs the timer.

WHY EARLY: Entitlement Milestones are the foundation of all SLA reporting. Skipping them means losing the ability to retroactively measure compliance — the data cannot be backfilled.

🔗 BRIDGE → Experience Cloud: If customers submit cases through a portal, entitlement assignment on portal-submitted cases must be tested end-to-end before UAT.
53Discovery Questions
53Gotcha Warnings
10Bridge Patterns
PDF + NotionDelivered As

CPQ Discovery

32 questions · 10 sections · 5 bridge patterns

Product catalog architecture, pricing waterfall, bundle rules, discount governance, Advanced Approvals, subscription amendments, data migration, and Revenue Cloud alignment.

1Product Catalog & Bundle ArchitectureQ1–Q3
2Pricing Strategy & Price WaterfallQ4–Q7
3Discount & Approval GovernanceQ8–Q10
4Quote Document & Template DesignQ11–Q13
5Subscriptions, Renewals & AmendmentsQ14–Q17
6Guided Selling & Product SelectionQ18–Q20
7Data Migration & Historical ContractsQ21–Q23
8Sales Cloud Integration & Quote SyncQ24–Q26
9Permissions, User Experience & AdoptionQ27–Q29
10Revenue Cloud AlignmentQ30–Q32
Sample Question Preview CPQ · Q1
Q > Walk me through how a price is calculated for your most complex product, from list price to the final number on the contract.

⚠ GOTCHA: The CPQ pricing waterfall — the sequence of List Price → Price Rules → Discount Schedules → Contracted Prices → Partner Discount → Distributor Discount — cannot be re-sequenced after Price Rules are built. Changing the order of pricing operations requires deleting and rebuilding every existing Price Rule.

WHY EARLY: The pricing waterfall is the architectural blueprint for CPQ. Every Price Rule, Discount Schedule, and Contracted Price is dependent on where it sits in the waterfall. Design this on a whiteboard before opening Setup.

🔗 BRIDGE → B2B Commerce: CPQ Discount Schedules and B2B Commerce Promotions have no native sync. If both are in scope, the pricing governance model must define which system is the source of truth for discounts.
32Discovery Questions
32Gotcha Warnings
5Bridge Patterns
PDF + NotionDelivered As

Agentforce Discovery

30 questions · 10 sections · 6 bridge patterns

Use case scoping, data grounding, Topic and Action design, escalation architecture, Trust Layer security, Flex Credits pricing, SDR Agent, and non-deterministic UAT.

1Use Case Scoping & Agent Type SelectionQ1–Q3
2Data Grounding & Knowledge FoundationQ4–Q6
3Agent Design: Topics, Actions & InstructionsQ7–Q9
4Channel & Escalation ArchitectureQ10–Q12
5Security, Guardrails & Trust LayerQ13–Q15
6Licensing, Editions & Flex CreditsQ16–Q18
7Testing, UAT & Human OversightQ19–Q21
8Integration with Sales & Service WorkflowsQ22–Q24
9Change Management & Organizational ReadinessQ25–Q27
10Agentforce for Sales (SDR Agent)Q28–Q30
Sample Question Preview Agentforce · Q6
Q > What content will the agent use to answer questions — Knowledge articles, external documents, CRM record data, or a combination?

⚠ GOTCHA: An agent grounded in poor Knowledge is worse than no agent — it actively misleads customers with confidently wrong answers. Data Cloud is required for grounding in unstructured external content (PDFs, web pages). Without Data Cloud, the agent can only ground on Knowledge articles and CRM records.

WHY EARLY: The grounding source determines the Data Cloud dependency, which determines both the licensing cost and the data pipeline architecture. Audit the Knowledge base quality before committing to agent grounding.

🔗 BRIDGE → Service Cloud: If Knowledge is shared between human agents and the AI agent, data category visibility and article quality standards must be aligned across both workstreams.
30Discovery Questions
30Gotcha Warnings
6Bridge Patterns
PDF + NotionDelivered As

B2B Commerce Discovery

30 questions · 10 sections · 5 bridge patterns

Store architecture, buyer hierarchy, catalog pricing, checkout limitations, ERP integration, search, deployment complexity, and the Aura-to-LWR rebuild conversation.

1Store Architecture & Site DesignQ1–Q3
2Buyer Management & Account HierarchyQ4–Q6
3Product Catalog & CategorizationQ7–Q9
4Pricing ArchitectureQ10–Q12
5Order Management & CheckoutQ13–Q15
6Search & MerchandisingQ16–Q18
7ERP & Systems IntegrationQ19–Q21
8Reorder, Self-Service & Account ManagementQ22–Q24
9Performance, SEO & DeploymentQ25–Q27
10Adoption, Analytics & Post-LaunchQ28–Q30
Sample Question Preview B2B Commerce · Q5
Q > How are buyers assigned access to products — by account, by contract, by custom entitlement, or open catalog?

⚠ GOTCHA: Buyers log in to a fully configured storefront and see nothing. This is the most common launch-day failure in B2B Commerce. Buyer Group enrollment — the junction between a buyer account, a product catalog, and a price book — must be explicitly configured. It is not inherited, not automatic, and not visible from the Account page layout by default.

WHY EARLY: The Buyer Group enrollment model must be designed before catalog configuration begins. Every product, price book, and entitlement rule depends on how buyers are grouped.

🔗 BRIDGE → CPQ: If CPQ manages pricing and B2B Commerce manages the storefront, which system is the source of truth for price books? Define governance before building either.
30Discovery Questions
30Gotcha Warnings
5Bridge Patterns
PDF + NotionDelivered As

Experience Cloud Discovery

38 questions · 12 sections · 6 bridge patterns

Template irreversibility, guest user security (active exploitation pattern), SSO ACS URL traps, sharing model by license tier, PRM limitations, CMS translation, deployment complexity, and Mobile Publisher lead times.

1Site Purpose, Use Case & Template SelectionQ1–Q3
2Licensing, User Types & Access ModelQ4–Q6
3Guest User Security & Public AccessQ7–Q9
4Identity, SSO & Self-RegistrationQ10–Q12
5Data Security & Sharing ModelQ13–Q15
6Site Performance & Custom DomainQ16–Q18
7Content, CMS & Multilingual SitesQ19–Q21
8Partner Relationship Management (PRM)Q22–Q24
9Agentforce, AI & Embedded ChatQ25–Q27
10Deployment, DevOps & GovernanceQ28–Q30
11B2C and Consumer Experience SitesQ31–Q34
12Adoption, Analytics & Post-LaunchQ35–Q38
Sample Question Preview Experience Cloud · Q1
Q > What is the primary purpose of this site, and who are its users — customers, partners, employees, or the general public?

⚠ GOTCHA: Template selection is an architectural commitment. The five available templates (Customer Service, Help Center, Partner Central, Build Your Own LWR, Microsite) are not interchangeable — each has different default components, page structures, and intended use cases. Choosing the wrong template forces a site rebuild, not a configuration change.

WHY EARLY: Template selection locks in the foundational page structure and the component library. Discovering mid-project that Customer Service was selected but Partner Central was needed requires a new site, re-migration of all configuration, and a sprint reset.

🔗 BRIDGE → Agentforce: If Agentforce Enhanced Chat is in scope, Legacy Chat must be removed first — they cannot coexist on the same page. Enhanced Chat requires the Digital Engagement add-on license.
38Discovery Questions
38Gotcha Warnings
6Bridge Patterns
PDF + NotionDelivered As

Multi-cloud projects need multi-cloud questions.

Every pack includes Bridge Questions — cross-workstream alignment questions that flag dependencies before they become change orders. 55 bridge questions across 18 cloud combination patterns.

Sales Cloud + Agentforce SDRSales Cloud Q6
Service Cloud + Field ServiceService Cloud Q14
CPQ + B2B CommerceCPQ Q3
Agentforce + Data CloudAgentforce Q6, Q12
B2B Commerce + CPQB2B Commerce Q9
Sales Cloud + CPQSales Cloud Q11
Service Cloud + AgentforceService Cloud Q8
Sales Cloud + Data CloudSales Cloud Q4
CPQ + Revenue CloudCPQ Q7
B2B Commerce + Experience CloudB2B Commerce Q2
Agentforce + Sales CloudAgentforce Q3
Service Cloud + Data CloudService Cloud Q12

Built for the people who run discovery.

The Freelance Consultant

You're about to run your first Service Cloud discovery for a new client. You know the platform. You don't want to miss the gotcha that costs you a change order.

The Boutique SI Partner

Your team runs discovery every week. You want every consultant asking the same high-quality questions with the same rigor you bring.

The In-House Architect

You're scoping a new cloud internally and don't want to find out mid-build what you should have asked in week one.

One purchase. Yours to keep.

Individual Pack
$29
per cloud
  • 30–55 questions per cloud
  • Gotcha + Why Early for every question
  • Bridge questions for multi-cloud projects
  • PDF + Notion template
Buy Single Pack — $29

Common questions.

Each pack includes a PDF (print-ready, branded with section banners and color-coded callout blocks) and a Markdown file optimized for Notion import. Import the Markdown to Notion and it becomes a live discovery tracker with colored callout blocks matching the PDF design.
No. The PDF is fully self-contained. The Notion template is a bonus for those who want a live tracker during discovery sessions.
Yes. These are practitioner tools. Use them on every engagement you run.
Buy the individual packs for those clouds. The bundle is for people who work across multiple clouds regularly.
This is not a training course. It's a practitioner question bank. It assumes you already know Salesforce — it helps you ask the right questions faster and catch gotchas before they become problems. All content is based on current Lightning Experience and LWR architecture as of early 2026.
Significant updates (major product retirements, architecture changes, new product launches) are published as new versions. Buyers get updates at no charge.
A Salesforce Architect with 10+ years of hands-on implementation experience across Sales Cloud, Service Cloud, CPQ, Agentforce, B2B Commerce, and Experience Cloud. Every question comes from a real engagement. Every gotcha comes from a real project. Find more Salesforce resources at sfdxhub.com.