Skip to content
Let's talk

Case study · supporting · 2017-04 to 2020-06

Salesforce Essentials

SMB packaging for Salesforce: decided what to leave out, what to automate, and how much AI a five-person team could actually use on day one.

Role
Senior Product Designer, SMB and Salesforce Essentials
Company
Salesforce
Dates
2017-04 to 2020-06
Bucket
smb packaging
Salesforce Essentials home dashboard with a Welcome Maria hero, funnel report bar chart, handle time line chart, and journeys conversion donut
Salesforce Essentials · HomeThe SMB entry point. One greeting, three role-shaped reports (Sales, Service, Marketing), and a single Let's Go for a customer setting up CRM in their first hour.

TL;DR

  • Role: Senior Product Designer, SMB and Salesforce Essentials
  • Timeframe: Apr 2017 to Jun 2020
  • Business problem: Salesforce had deep enterprise capability but SMB customers needed a simpler first experience to grow into the product instead of bouncing off it.
  • What I changed: Shaped Salesforce Essentials by focusing on onboarding, feature packaging, product adoption, and AI capabilities that delivered immediate value.
  • Proof: Foundational work on Essentials, product adoption, customer learning journeys, and Einstein AI feature packaging. Essentials grew into a standalone business unit.

The problem was not simplifying Salesforce

"Make it simple" is easy to say and usually lazy. The harder question: simple for whom, at what moment, and at what cost to the user's future?

Small businesses did not need a watered-down Salesforce. They needed the right first hour: what to do, what to ignore, how to get value before becoming CRM experts. The work became a series of packaging decisions. What to ship in Essentials. What to leave out. What to explain. What to automate. Where AI could remove setup instead of adding a feature to learn.

The surface decisions mattered, but the upstream question mattered more: which Einstein capabilities actually helped a five-person team make better decisions faster? Engineering asked which ones were buildable. Design kept asking the different question.

What I did

  • Helped shape product strategy and positioning for Essentials, working across design, research, marketing, sales, product, and engineering on the SMB surface.
  • Designed SMB workflows that met users earlier in their maturity curve, packaging the experience around the few jobs they needed to get done on day one.
  • Worked cross-functionally to identify Einstein capabilities delivering immediate value for small teams: automatic data capture, email parsing, smart suggestions. Held back predictive scoring that asked too much of SMB mental models at first use.
  • Rebuilt onboarding as a product with its own users, its own success states, its own design problem, replacing a collection of per-feature modals with a coherent adoption journey.
  • Co-led work to align learning experiences across the Salesforce ecosystem around that frame, shifting from fragmented per-feature tutorials toward coherent cross-product journeys.
  • Aligned external promise with product reality across marketing, research, engineering, and sales.

Selected SMB surfaces

Packaging by sequence, not by feature.

  1. 01 / 04Onboarding intent
    Onboarding intent
    We ask what you want to do, not which features to enable. Six illustrated intents (Support, Sales, Fundraising, Marketing, Project Management, HR) replace a feature checklist, and the product reshapes around the answer.
  2. 02 / 04Trailhead in-context
    Trailhead in-context
    Learning lives inside the app, not next to it. Trailhead modules surface against the workflows they are about to enable.
  3. 03 / 04Conversational tasks
    Conversational tasks
    CRM primitives stay first-class and the chrome gets out of the way. Assignees and related contacts sit one tap from the task, never buried in a settings tab.
  4. 04 / 04Omnichannel messages
    Omnichannel messages
    AI earns a side panel, not the driver's seat. An Einstein cross-sell sits beside the customer conversation as a suggestion the rep can take or ignore, never a forced step.

What changed

Essentials gave SMB customers a more approachable path into Salesforce, shifting from enterprise capability exposed all at once to a guided experience packaged around user readiness.

  • The Einstein capabilities kept inside Essentials shaped how the company thought about AI for SMB beyond this product.
  • Adoption and learning work shifted from fragmented per-feature tutorials into coherent cross-product journeys.
  • The cross-company work produced durable process change, not a one-time deliverable.

The strategic move: reduce cognitive load without reducing ambition. The product could still grow with the customer because the architecture was not capped at simple.

"He's been a trusted colleague through the creation, iteration, and development of Salesforce Essentials. Without his visionary work driving the product forward, the user wouldn't have the tailored onboarding and in-app experience they have today."

Source: LinkedIn recommendation.

Reflection

The strongest version of this work is not "I made Salesforce simpler." It is deciding how much enterprise power a small business should meet at each stage of maturity, and making that call defensibly inside a company that wants to ship everything.