Your First Day in the Sales System: A One-Day Account Setup Checklist

You can finish setting up your sales system in a single working day — provided you follow one order: structure first, then data, then the pipeline, then permissions, then inbound channels, and finally an acceptance test on a live deal. Most setup mistakes that are painful to undo — duplicate imports, wide-open permissions, a pipeline that looks nothing like reality — come from reversing that order, not from running short on time.

The shape of the day: six stops, and why this sequence

Each stop produces something the next one depends on. You can't set permissions before teams exist, you can't build teams before you know your branches, and you can't import customers before there's an owner to assign them to. Work in sequence, and give every stop a written output and a clear definition of "done."

Stop one: account structure, branches and teams — before any data

Create branches as they actually exist on your org chart, not as you hope they'll look after expansion. Then build teams beneath them, then add users with their real names and official work email addresses.

Output: a tree of branches, teams and users. Done when every rep finds themselves under the right team with the right direct manager.

Stop two: clean the customer file, then import it once

Clean before importing, not after. Standardise phone number formats, remove duplicates by matching on number rather than name, and strip customers who've been dormant for two years out of the import file — keep them in a separate archive. Test with a sample of fifty records first, review the result, then import the rest.

Output: one approved import file. Done when no customer appears twice and every record has a named owner.

Stop three: map the pipeline as it actually happens, not as it's supposed to

Ask two reps: what steps does a deal really go through here? Write the stages down using the names they already use. Five or six stages are plenty, and each needs a single exit condition that leaves no room for interpretation — "quote sent," "purchase order issued." In Effistar, stages are defined once and then flow through every report that follows, so precision here saves a lot of rework later.

**Done** when two reps place the same deal in the same stage without arguing about it.

Stop four: permissions — who sees what, who edits what

Start narrow and widen on request; the reverse is painful. The practical rule: a rep sees their own customers and deals, a team manager sees their team, and finance sees receivables but not pricing margins. Restrict record deletion and edits to closed-deal values to one person.

Done when you log in as a test rep account and can't see anything that isn't theirs.

Stop five: connecting WhatsApp and inbound channels

Connect the company's official WhatsApp number, not an employee's personal mobile. Decide who picks up new conversations and how an incoming message becomes a lead in the system.

Done when you send a message from an outside number and a conversation appears, assigned to a specific employee, within a minute.

Stop six: an acceptance test on a real deal before you go live

Take a deal that's genuinely in progress and run it end to end: customer, opportunity, activity, quote, a move between two stages — then open the report and confirm it shows up.

Done when the full cycle completes without you stepping in. Only then announce go-live to the team.

Setup mistakes that are hard to undo, and how to avoid them

Mistake	Preventive fix
Duplicate import	Test with fifty records first; match on phone number
Permissions open to everyone	Start narrow, widen on written request
Borrowed pipeline stages	Derive them from what your reps actually say
Too many mandatory fields	Don't require a field no report will ever read

Day two isn't for setup. It's for watching the first ten deals that actually get entered.