Salesforce Setup for Beginners: A First-Week Plan

Updated May 2026. Rewritten as a first-week setup plan with concrete decisions, opinionated defaults, and the configuration items that bite later if you skip them.

Most Salesforce setup guides for beginners list every feature in Sales Cloud, Service Cloud, and Marketing Cloud. That is not what you need on day one. You need the first-week setup decisions, in order, with notes on which ones come back to bite you when revenue starts running through the system.

We are a Brisbane consultancy that has set up Salesforce orgs from scratch for clients in recruitment, professional services, finance, and SaaS, and we have inherited a fair share of poorly-configured orgs that needed cleaning up. The setup decisions that matter on day one are the ones that are expensive to reverse: how you structure accounts and contacts, how you name your stages, who you give admin permissions to, and what you write down before you start clicking around.

This is the Salesforce setup plan for beginners we would follow if we were starting a new org tomorrow. Five days, eight decisions, and a list of what to defer.

Before You Touch Salesforce Setup, Write Three Things Down

The mistake most new Salesforce admins make is starting in Setup before they have answered the three questions every configuration decision rests on:

1. What is your sales process? Write the stages from initial enquiry to closed-won, with the exit criteria for each. Five to seven stages is the sweet spot. If you have more than ten, the team will skip ones in real life.
2. Who are you tracking, and at what level? Are you primarily B2B (Accounts and Contacts) or B2C (just Person Accounts)? Mixing both inside one org without a clear rule is the single most expensive mistake to unwind.
3. What questions will the team ask the data? “How many qualified leads did marketing send us last month?” “What’s the pipeline by stage?” “Which deals went dark in the last 14 days?” The fields you create should answer those questions, not be a kitchen sink.

If you cannot write these down in a single page, do not start clicking. Spend half a day with the sales lead first. The Salesforce setup decisions get easier when the business questions are clear.

Day 1: Pick an Edition and Set Up Your Salesforce Org

Salesforce sells five main editions for Sales Cloud, ranging from Starter (entry level) to Unlimited. For a beginner Salesforce setup in 2026, the practical choice is between three:

• Starter (around $35 AUD per user per month). Stripped-down. Suits a 1-5 person team that needs basic contact, deal, and activity tracking without customisation. No custom objects, limited workflow.
• Professional (around $115 AUD per user per month). The most common starting point for B2B teams of 5-30 users. Custom objects, basic workflow, more reporting.
• Enterprise (around $250 AUD per user per month). The realistic floor for serious customisation, profiles, permission sets, advanced workflows. Most of our mid-market clients live here.

Pick the lowest edition that includes the features you actually need. Upgrading later is straightforward. Downgrading is a project. If you are unsure between Professional and Enterprise, take the 30-day Enterprise trial and use the trial period to validate your need for the Enterprise-only features (profiles, sharing rules, advanced reporting).

Once you have signed up, do these four things in your new Salesforce org on day one:

• Set the org default time zone, locale, and currency in Company Information. For Australian businesses, set the default currency to AUD and time zone to Australia/Sydney (or your local). Changing currency after data has been loaded is painful.
• Enable Multi-Currency only if you need it. If your customers will only ever pay in AUD, leave it off. Multi-Currency cannot be disabled once enabled.
• Enable My Domain if not already. Salesforce now does this for all new orgs but verify the subdomain matches what you want.
• Set up Lightning Experience (it is the default now) and turn off Salesforce Classic access if anyone tries to swap back. Train on one interface, not two.

Day 2: Users, Profiles, and Permission Sets

The single most common mess we inherit is a Salesforce org where everyone has the System Administrator profile because giving them anything less broke something. Get the user model right on day two, before you start handing out logins.

The practical Salesforce permission model for beginners:

• Profile sets the baseline (object-level read/edit/delete, field-level access). One profile per role. Start with three: Sales User, Sales Manager, System Administrator.
• Permission set grants additional access on top of a profile (a single user who needs to import data once gets a “Data Importer” permission set, not a profile change).
• Role determines record visibility through the role hierarchy. Sales reps see their own records and their team’s. Managers see their team’s. The CRO sees everything. Build the role tree before you create users.

Limit System Administrator access to two people maximum, even for a 50-person org. Anyone who needs a temporary permission gets a permission set added then removed, not a profile upgrade. Audit who has admin every 90 days. Salesforce orgs accumulate admins the way phones accumulate apps you do not use.

Single Sign-On with your identity provider (Okta, Microsoft Entra, Google Workspace) earns its place once you have more than 15 users. The setup is a half-day. The licensing nuance is real (Salesforce requires SSO licences on some editions). For solo and tiny teams, Salesforce Authenticator on phones is fine.

Day 3: Objects, Fields, and the Discipline That Saves You Six Months

Salesforce gives you Account, Contact, Lead, Opportunity, Case, and many more out of the box. You will be tempted to add custom fields freely. Do not.

Three rules we follow for any new field:

• The field must answer a specific business question you wrote down on day zero. “Source of lead” answers “where is marketing investing best”. “Favourite colour” does not.
• Picklists, not free text, wherever possible. Free text “Industry” gives you 47 variations of “Retail”. Picklist “Industry” gives you a usable report. Validate input rules at creation, not via dashboards on dirty data.
• Mark required fields sparingly. Sales reps work around required fields by typing “x” in them. If a field is genuinely critical at stage transition, use a validation rule on the stage update, not on record creation.

The Lead vs Contact question trips up most beginners. The Salesforce convention: a Lead is an unqualified prospect, a Contact is a person inside an Account. Once a lead is qualified, you convert it (Salesforce creates the Account, Contact, and Opportunity). Decide your conversion criteria explicitly. “BANT met” or “discovery call booked” works. “Sales rep feels good about it” does not scale.

For B2C businesses or property/agency models, enable Person Accounts only after you have read the implications. It is one-way (cannot be disabled), it changes how reports work, and Salesforce treats Person Accounts as both Accounts and Contacts which can confuse third-party integrations.

Day 4: Salesforce Setup for the Sales Process Itself

This is the day you turn the sales process you wrote down on day zero into Opportunity stages, probabilities, and a path. Five to seven stages, named with verbs the team uses:

• Qualification (10%): discovery call booked or completed.
• Discovery (25%): customer pain confirmed, decision criteria known.
• Proposal (50%): proposal sent.
• Negotiation (75%): commercial terms agreed in principle.
• Closed Won (100%) or Closed Lost (0%).

Use Sales Path to define exit criteria per stage and the next step. Sales reps see these on the Opportunity record. The path is the cheapest training mechanism Salesforce ships and almost nobody uses it.

The probability column matters more than people realise. It is what feeds your weighted pipeline. Default percentages are bad guesses. Look at your actual conversion rates after 90 days of clean data and update them to reflect reality. Salesforce will let you create deals at 10% that you know are 60%. That is fine. The point is the average across all deals at that stage.

Lead and Opportunity assignment rules are worth setting up now. Round-robin to sales reps, or by territory, or by lead source. The alternative is a daily morning routine of someone reassigning leads, which never lasts.

Day 5: Reports, Dashboards, and the First Real Data Load

Build the first five reports the team needs before you load production data:

• Open Pipeline by Stage
• Closed Won This Month
• Deals Stuck (no activity in 14 days)
• Lead Source Performance
• My Activities This Week

If any of these break or look wrong after you load the data, your fields are wrong. Fix the fields before adding more reports. The mistake is loading data and then realising the report you need cannot be built because the field does not exist or the picklist is unstructured.

For the data load itself, use the Data Import Wizard for small or one-off jobs (under 50,000 records), and the Data Loader for anything else. Map fields explicitly. Run a small test batch (10 records) and confirm the result before loading the rest. We have seen six-digit data restores after a careless data load wrote NULL into populated fields. The “always use the External ID matching” rule prevents almost all of those incidents.

Build one Salesforce dashboard for the team’s home page. Three to six components, all real-time. More than that and people stop scanning it.

What to Defer in Week One of Salesforce Setup

The shopping list of Salesforce features is long. These are the ones to leave alone in week one:

• Service Cloud. Unless you are running a support team day one, set this up later. Cases without a defined service workflow become a ticket graveyard.
• Marketing Cloud, Pardot, Account Engagement. Different product, different setup, different licence. Decide if you actually need it after sales is running.
• Flow Builder. Powerful but easy to make brittle. Most use cases beginners reach for can be solved with validation rules, approval processes, or field updates first. Add Flow when those run out.
• Custom Lightning components and code. The temptation to write Apex on day one is real. Resist. Salesforce ships solutions to 90 percent of common needs.
• Einstein and most AI features. The licences are expensive, the value comes from data quality, and you do not have that yet. Add after six months of clean data.

Integrations and the Third-Party App Question

Two integrations earn their place in most week-one Salesforce setups:

• Email and calendar (Outlook or Google Workspace). The Salesforce Inbox or Einstein Activity Capture surfaces customer emails on the record. Without this, reps stop logging activities.
• One marketing tool. HubSpot, Mailchimp, ActiveCampaign, or whatever you already use. Send marketing-qualified leads into Salesforce as Leads with a clear source tag.

Everything else (accounting, ticketing, document signing, AI assistants) can wait. The AppExchange has 7,000+ apps. New admins install too many. Each one is a permission grant, a possible data sync conflict, and a future audit headache. We have seen orgs with 40 installed packages that nobody can map to a business owner.

When Salesforce Setup Is the Wrong Call

Salesforce is excellent and overkill for plenty of businesses. If you are under 5 sales users and your sales process is a six-stage funnel, HubSpot Free or Pipedrive will give you what you need at a fraction of the licence cost and setup time. Salesforce earns its premium when you need customisation depth, regulatory audit trail, multi-currency, complex territory and forecasting, or a single source of truth for an enterprise.

If you are migrating to Salesforce from another CRM, our advice is to ship the standard Salesforce setup first, then layer in the bespoke logic from the old system after the team is using the new one. The temptation to recreate the old system exactly inside Salesforce wastes the upgrade.

If You Want Help With Your Salesforce Setup

We help businesses set up Salesforce cleanly, integrate it with their existing tools, and automate the parts where humans are the bottleneck. If you are at the start of a Salesforce setup and want to talk through the structure before you start clicking, you can book a call or read more about how we approach CRM and automation work. Get in touch through our contact page with the specifics of your sales process and we can give you a starting framework.

For more on the underlying disciplines that make a CRM setup pay off, our process mapping guide covers the decision-aid we use before any system implementation.

Frequently Asked Questions

How long does a Salesforce setup for beginners take?

A clean first-week Salesforce setup is five working days of an admin’s time, assuming the sales process is documented before they start. A full deployment with custom objects, integrations, data migration, and training typically takes 6 to 14 weeks of part-time consultancy work, depending on the depth of customisation. Beginners often underestimate the half-day of process documentation that has to happen before clicks one.

Getting started with Salesforce, which edition do I pick?

For 1-5 users with a simple sales process, Starter ($35 AUD per user per month). For 5-30 users with a B2B sales motion, Professional ($115 AUD per user per month). For anything bigger or with serious customisation needs, Enterprise ($250 AUD per user per month). Take the trial of the next edition up before committing, so you can see what you would be missing.

How do I use Salesforce day to day as a beginner?

Three habits sales reps need from week one: log every customer interaction (call, email, meeting) on the Account or Opportunity, update Opportunity stage when something genuinely changes, and run the “My Activities This Week” report on Monday morning. If those three habits are not in place, the data degrades and the system stops earning its cost.

What are the basics of Salesforce CRM?

Five objects do most of the work: Account (the company), Contact (the people at the company), Lead (unqualified prospect, becomes Account+Contact when converted), Opportunity (a deal in the pipeline), and Activity (calls, emails, meetings). Understand those five and you can navigate 80 percent of Salesforce. Everything else is customisation on top.

How much does Salesforce cost in Australia (AUD)?

Sales Cloud editions in AUD as of 2026: Starter around $35 per user per month, Professional around $115, Enterprise around $250, Unlimited around $500. Multiply by the number of users. Annual commitment usually saves 10-15 percent. Implementation and consultancy on top: $5,000 to $40,000 AUD for a beginner Salesforce setup, depending on customisation and integration depth.

Should I get help with my Salesforce setup, or do it myself?

Do it yourself if you are under 10 users with a simple sales process. The Trailhead training is genuinely good and Starter or Professional is built to be admin-friendly. Get help if you are doing complex integrations (especially with finance or marketing automation systems), migrating from another CRM, or implementing Enterprise features like advanced security, territory management, or CPQ. Half a day with a Salesforce consultant before you commit to a setup approach pays for itself.

What is the most common mistake in Salesforce setup for beginners?

Adding custom fields without writing down the business question they answer. The org accumulates fields, half of them are never populated, reporting becomes painful, and within 18 months the team is muttering about “Salesforce being slow”. It is not the platform. It is the field bloat. Audit and retire unused fields every six months.

How do I import data into Salesforce safely?

Three rules. First, deduplicate the source data before import (Excel or a quick Python script). Second, run a 10-record test batch and confirm the result on screen before loading the rest. Third, always use External ID matching when updating existing records, never just record IDs. The Data Import Wizard handles up to 50,000 records and is fine for beginners. For anything bigger or repetitive, use the Data Loader or a paid tool like Skyvia.