Set up Salesforce for day-zero selling — pipeline, users, email sync, and the first logged activity — before optional marketplace apps.
Set up Salesforce in this order: pick a plan that covers day-one needs, name one admin, configure one pipeline, invite daily users, connect email, then have a non-admin create a deal, log activity, and move a stage. Confirm custom fields (Pro+) and email sequences (Unlimited+) are on the plan you will actually buy. You’re done when that walkthrough works — not when every module is switched on.
Verified captures and vendor tutorials for configuring Salesforce before go-live — pipeline, contacts, and first workflows.
Vendor tutorial for onboarding and configuration. It is not a SoftwareGlimpse rollout plan — use this guide for judgment.
This video is hosted on YouTube
This content is hosted by YouTube. The player loads only after you allow marketing cookies.
Official vendor tutorial
Verified captures from Salesforce's product interface.
Pipeline management UI from the Sales Cloud features page.
Official Sales Cloud features asset
https://www.salesforce.com/products/sales-cloud/features/ · Checked 2026-08-14
Full product screenshots and evidence live on the Salesforce research page.
Bring these questions to every demo
Ask vendors to show the workflow live, not just describe it.
Entry plan
Our snapshot lists no free Salesforce plan — Starter Suite is the floor. Verify on the pricing page.
Qualifying paid plan
Starter Suite upward — stay on the cheapest one that clears every must-have gate.
Quote-only tier
No quote-only tier appears in our Salesforce snapshot; treat any sales-only promise as unconfirmed.
Write five day-one jobs, map each to a researched Salesforce plan, and pick the cheapest tier that covers all five.
Our pricing snapshot records a 30-day trial on Starter Suite, Pro Suite, and Enterprise — confirm current terms on the Salesforce pricing page before you build a schedule around it.
Worked example: a 12-person B2B advisory team needs contact management, lead management, pipeline management, and deal management plus email sync on day one in Salesforce. They start on Starter Suite and note which capabilities would force an upgrade.
Admin owner
Fields, users, integrations, and data hygiene in Salesforce.
Sales champion
Owns stage definitions and what “next step” means.
Executive sponsor
Clears blockers; does not redesign the data model midweek.
Name one admin — not a committee — before you invite sellers.
Worked example: a 12-person B2B advisory team makes ops the Salesforce admin, writes the two-hour commitment into the week, and blocks everyone else from adding fields for 30 days.
One motion first
A second pipeline in Salesforce can wait until the first one is honest.
Required fields
Owner, next step, next-step date, expected close — that is it.
Archive, do not recreate
Legacy fields you will not use belong in an export, not the new workspace.
Research confirms contact management, lead management, pipeline management, and deal management for Salesforce — that is the surface you are configuring here.
Worked example: a 12-person B2B advisory team configures six stages in Salesforce (qualified, scoped, proposal, verbal, won, lost), makes “next step” required, and refuses every other custom field until after go-live.
Daily users in
Anyone who owns a deal or logs activity.
Viewers wait
Read-only curiosity is not worth a paid seat in week one.
Admin rights scarce
One or two admins maximum; everyone else requests changes.
Invite people who touch deals daily. Spectators can wait.
Worked example: a 12-person B2B advisory team invites eight sellers, two managers, and ops into Salesforce; part-time analysts wait until someone proves they need a seat.
Connect now
Email, calendar, and Gmail.
Connect later
Slack after adoption holds.
Document the gap
Anything Salesforce research does not confirm goes on the risk list, not the launch deck.
Worked example: a 12-person B2B advisory team connects mailboxes and Gmail in Salesforce, then postpones accounting and document tools until the 30-day adoption review.
Worked example: a 12-person B2B advisory team's founder completes the loop in Salesforce without ops help, ops writes the one-pager, and only then does the team announce go-live.
Installing integrations before the pipeline works
Connector logos are not a sales process. Get contact management, lead management, pipeline management, and deal management right in Salesforce first.
Copying a 20-stage template
Stages nobody can verify from the buyer's side become noise, then get ignored.
Testing only as an admin
Admin accounts hide the permission and visibility problems sellers hit on day one.
Configuring a capability your plan does not include
Plan-gated in research: custom fields (Pro Suite, Enterprise, Unlimited); email sequences (Unlimited); forecasting (Pro Suite, Enterprise, Unlimited); prospecting (Starter Suite, Pro Suite, Enterprise, Unlimited). Check the Salesforce plans guide before you design around a gated feature.
Inviting everyone at once
Seats and capacity are researched limits, not suggestions. Confirm caps on the pricing page before a bulk invite.
Designing around a known weak spot
Research flags: Steep learning curve and high administration/implementation overhead versus SMB CRMs. Plan for it during setup instead of discovering it in month two.
Qualify the plan, create the workspace with one admin owner, model contact management, lead management, pipeline management, and deal management with a single pipeline, invite daily users, connect email and calendar, then prove the loop as a non-admin. Decision rule: no non-admin loop proof means setup is not finished.
Researched plans are Starter Suite, Pro Suite, Enterprise, Unlimited. Pick the cheapest one that carries every day-one must-have — Plan-gated in research: custom fields (Pro Suite, Enterprise, Unlimited); email sequences (Unlimited); forecasting (Pro Suite, Enterprise, Unlimited); prospecting (Starter Suite, Pro Suite, Enterprise, Unlimited). See the Salesforce plans guide for the full selection algorithm.
Email sync is researched across every Salesforce plan we snapshot. Confirm current packaging on the pricing page before go-live.
A focused small team can finish this six-step path in days, not quarters — the delay is usually agreeing stage definitions, not clicking. Our pricing snapshot records a 30-day trial on Starter Suite, Pro Suite, and Enterprise — confirm current terms on the Salesforce pricing page before you build a schedule around it.
No. Start with a small clean working set so you can prove the loop, then run the Salesforce migration guide's pilot before bulk import.
Research names Gmail, Outlook, and Slack on the Salesforce side — confirm the ones your daily loop actually depends on. Connect email and calendar, plus the one tool sellers already open daily. Everything else waits for the 30-day review.
Research lists AI assistant, AI email drafting, AI summaries, and AI forecasting for Salesforce. Research places AI assistance on Starter Suite, Pro Suite, Enterprise, and Unlimited. Leave assistance off until the manual loop is reliable — otherwise you cannot tell whether the AI or the process caused a result.
Continue with the Salesforce implementation guide for the 30/60/90 adoption gates, or the migration guide if you are moving history from another system.
Have more questions? Contact our support team.
Want clearer software shortlists? Get buying guides and comparisons by email.
Newsletter coming soon.