Salesforce setup for small businesses: a 12-step checklist

A good Salesforce setup for a small business takes two to four weeks, and most of that time goes into decisions, not clicks. Below is the order we follow on real projects. If you follow it, you avoid the two problems we fix most often: a pipeline nobody trusts and a pile of fields nobody fills in.

1. Write down how you sell today

Before opening Setup, write one page that answers:

• Where do leads come from (website, ads, referrals, events)?
• Who follows up, and how fast?
• What has to be true before a deal moves to the next step?
• What do you need to report on every week?

This page becomes your requirements. Everything below is built from it.

2. Choose the edition for your next two years, not your next two months

Starter and Pro Suite cover many small teams. Enterprise is worth it when you need more automation, API access for integrations, or several sandboxes. Look at your integration plans first: an edition without API access can make a simple website or accounting integration expensive later.

We also check how many people really need a full license. Some only need to view records or log cases, and a lighter license may be enough.

3. Set up the company, users and security

• Company information, currency and fiscal year.
• Roles that match your reporting lines, not your org chart wish list.
• Profiles kept minimal, with permission sets for anything extra.
• Multi-factor authentication switched on for everyone.

Keep sharing simple at the start. Opening data up later is easy; locking it down after people are used to seeing everything is not.

4. Decide what a lead, an account and a contact mean for you

Most small B2B teams use leads for unqualified interest and convert them to accounts, contacts and opportunities once there is a real conversation. Some teams skip leads entirely. Either is fine, but pick one and write it down, or your data splits in two.

5. Build the opportunity stages with exit criteria

Five to seven stages is usually enough. For each one, agree on what must be true to move forward, for example "budget confirmed" or "proposal sent". Make the key fields required at the right stage with validation rules, so the forecast is based on facts rather than optimism.

6. Add only the fields you will report on

A field nobody reports on is a field nobody fills in. For every custom field, ask: which report or automation uses this? If there is no answer, leave it out. You can always add it later.

7. Capture leads automatically

Connect your website forms with Web-to-Lead or a form tool, and add assignment rules so every new lead has an owner within minutes. Add basic spam protection (reCAPTCHA or a hidden field) from day one, because one spam wave can bury real leads.

8. Automate the follow-up with Flow

Start with three automations that save time immediately:

• A task for the owner when a new lead arrives.
• A reminder when an opportunity has not moved for a set number of days.
• An alert to the manager when a large deal reaches the final stages.

Build them in Flow. Workflow Rules and Process Builder are retired for new automation.

9. Import your data, cleaned

Clean the spreadsheet before you import it: remove duplicates, fix company names, split full names into first and last name, and standardise countries and states. Turn on duplicate and matching rules before the import, not after. Import accounts first, then contacts, then opportunities, so the relationships link correctly.

10. Connect email and calendar

Einstein Activity Capture or the Outlook and Gmail integrations log emails and meetings against the right records. Without this, activity history depends on people remembering to log calls, which they will not.

11. Build the first three dashboards

• Pipeline: open opportunities by stage and owner.
• Activity: new leads, response time and meetings booked.
• Results: won revenue this month and quarter against target.

Show them in your weekly sales meeting from the first week. Teams keep data clean when they see it being used.

12. Train by role, then review after 30 days

Run short training sessions per role, with screen recordings people can rewatch. After 30 days, review what is actually being used, remove fields and steps that nobody needs, and fix whatever people found annoying. This review is where adoption is won or lost.

Mistakes that cost the most to undo

• Copying every column from the old spreadsheet into Salesforce.
• Building complex automation before the process is agreed.
• Giving everyone the System Administrator profile "for now".
• Skipping the sandbox for changes once people are live.

Summary

Decide how you sell, keep the data model small, automate the follow-up, and review after a month. If you would like a second pair of eyes on your plan or an existing org, see our Sales Cloud setup service or book a free call.