How Long Does a Salesforce Implementation Take for a Small Business? A Week-by-Week Plan

How long does a Salesforce implementation take for a small business?

Two to eight weeks, and scope picks the range: the edition, the number of users, and whether Salesforce has to talk to another system. Our small business page (as at September 2026) lists Starter Suite at 2 to 4 weeks (simple configuration, limited customisation), Pro Suite at 4 to 6 weeks (more customisation, additional integrations) and Pro Suite with complex integrations at 6 to 8 weeks (custom integrations, advanced automation). Our Sales Cloud service page quotes "6-12 weeks from kickoff to go-live" for fuller builds. The phases are the same in every case; the middle ones get longer.

Not sure you should buy? See is Salesforce worth it for a 5-person business.

What happens in each week?

Four phases, from our small business page: "Discovery & Planning (Week 1)", "Configuration & Data Migration (Weeks 2-3)", "Testing & Training (Week 4)" and "Go-Live & Support (Week 5+)". A 2-week Starter Suite build compresses them; an integration stretches the middle two. Inclusions are quoted from our pricing page (as at September 2026), integration steps from our integration service page.

Phase	Starter Suite (2 to 4 weeks)	Pro Suite (4 to 6 weeks)	Pro Suite with one integration (6 to 8 weeks)	Your team's tasks
Discovery & Planning (Week 1)	Map your process; agree stages, fields and reports. "Salesforce setup for up to 5 users".	The same, plus the workflow to automate. "Up to 20 users".	The same, plus "Discovery & Integration Architecture" for the "1 third-party integration (Xero, Mailchimp, etc.)".	Explain how a lead becomes a customer; name one decision-maker; list your systems.
Configuration & Data Migration (Weeks 2-3)	"Sales Cloud / Service Cloud configuration"; import your data; connect email and calendar.	"Custom configuration for your workflow"; "Workflow automation & Flow builder"; migration from existing systems.	The same, with "Design & Development" of the integration alongside; the extra weeks go here.	Export and clean your data; answer questions within a day; review the build.
Testing & Training (Week 4)	Your team tests real scenarios. "2 hours of live team training".	Role-based testing. "4-hour role-based training workshop".	The same, plus "Testing & Data Validation" of the integration.	Test with real deals; attend training; sign off.
Go-Live & Support (Week 5+)	"30-day post-launch support"; "Email & phone support".	"60-day post-launch support"; "Priority support".	"60-day post-launch support", with hypercare on the integration.	Use it daily; retire the spreadsheet; flag what does not fit.

How many hours does your own team need to put in?

Fewer than most owners fear, but front-loaded. For the build itself, the only hours we publish are our own: "2 hours of live team training" on the Starter package and a "4-hour role-based training workshop" on the Professional package (as at September 2026). The rest is a pattern, not a figure; your hours depend on your data and your decisions.

Week 1 is heavy for one person. The owner or sales lead must be available for discovery and decide on the spot: sales stages, what "qualified" means, who owns which accounts. Expect a few hours that week from that person, plus some from whoever knows the data.

Weeks 2 and 3 are light but need fast answers. Someone exports and cleans the data; someone answers questions within a day. In our experience, answer speed is why two projects of the same scope finish weeks apart.

Week 4 is everyone. Every user tests real scenarios and attends training. Protect this week; a session with half the team missing is a reliable way to stall adoption.

Week 5 onwards is ownership. Our Sales Cloud page calls this a "citizen admin": an existing team member who gives it part of their month. Salesforce's Trailhead rollout guidance (as at September 2026) names four roles (executive sponsor, operations manager, end users, admin) and says one person can cover two or more.

What adds weeks to a Salesforce implementation?

Six things, mostly about people rather than software.

1. Data that is not ready. Records spread across inboxes, spreadsheets and an old CRM make the cleanse step swallow weeks 2 and 3. Our data migration guide shows what "ready" looks like; most of it can be done before kick-off.
2. Integrations. Our integration service page (as at September 2026) says simple native connectors "can often be completed in 1-2 weeks" and a Xero-type integration typically takes "4-8 weeks". A second integration is a scope conversation, not a week added.
3. Automation beyond the basics. Salesforce's edition comparison table (as at September 2026) shows Flow Builder as not included on Starter Suite and limited to "5 flows per org" on Pro Suite. Every flow added mid-project adds design, build and test time.
4. Decisions that stall. Stages nobody agrees on, a field list that keeps growing, a report three people want three ways. One named decision-maker in week 1 prevents most of it.
5. Scope that grows. Our project work "is scoped in a statement of work with defined deliverables" (answers page). The honest reply to "can we just add..." in week 3 is usually "yes, after go-live".
6. No separate place to test. The same Salesforce table shows a Developer Sandbox on Pro Suite but not Starter Suite, so a Starter build is tested in your live org with sample records.

Rescuing an org that went wrong is a different job; see why Salesforce implementations fail and how to rescue one.

Can you implement Salesforce yourself, and how long does that take?

Yes, especially on Starter Suite. Salesforce publishes no setup duration on its pricing page, help articles or Trailhead rollout module, so we will not invent one. It does publish a trial: the Sales Cloud pricing page (as at September 2026) says "Try Sales Cloud free for 30 days. No credit card, no installations," and its FAQ adds a free 30-day trial of Starter Suite for up to 10 users. Load real customers and a real pipeline; see whether the team opens it unprompted.

Salesforce's "Setup Best Practices" article for Starter and Pro Suite (as at September 2026) lists the tasks as "Import contacts, connect email accounts, manage sales paths, and invite new users". The Trailhead rollout strategy module walks through "Gather Your Team", "Establish Your Goals", "See What You Get Out of the Box", "Understand Your Tools and Resources" and "Set Milestones", then lists five milestones: add users, configure Sales Cloud to fit your business, import your data, enable productivity features, train users. On timing it says only that "Your timeline will be unique because your business is unique", and advises picking a go-live date and working back from it.

Do it yourself when one person has the time, the process is simple and nothing needs integrating; the cost is that person's hours. Get help when the data is messy, the CRM must talk to Xero or your website, or the person who would do it is also the person who sells. Our partner selection guide lists the questions to ask first, including of us.

What does a fixed-price package include and exclude?

Everything we deliver for the stated scope; not the licences. Our answers page (as at September 2026) says: "Everything we deliver for the stated scope. The price you see is the price you pay." In detail: "Consulting hours (typically 30 to 150 depending on tier), configuration work, training, written documentation, and the post-launch support window stated on the tier. No hourly surprises during the engagement."

Honestly not included: "Salesforce licences and optional third-party apps." Licence fees "are billed to you by Salesforce directly; we help you size them and apply nonprofit discounts where eligible", and optional apps are quoted upfront before any commitment.

On lock-in: "Project work is scoped in a statement of work with defined deliverables. Ongoing support and fractional packages can be scaled up, down, or stopped; there are no long-term lock-in contracts." On the first fortnight: "If you are not satisfied within the first 2 weeks of an engagement, we refund your deposit minus any hours actually worked." Week 1 is discovery, so you will have seen the roadmap before that window closes.

How does the timeline relate to cost?

Loosely. Our packages are fixed price, so the invoice follows the scope, not the calendar. Our pricing page (as at September 2026, NZD, ex GST) lists the Starter package at NZ$2,500 to NZ$5,000 for up to 5 users, the Professional package at NZ$5,000 to NZ$15,000 for up to 20 users, and Enterprise by custom quote, with a 15% nonprofit discount. Payment is "50% deposit at kick-off, 50% at go-live", with "3 quarterly instalments at no extra cost" for nonprofits and cash-constrained SMBs.

A week lost on your side adds nothing to our invoice; it delays go-live and the value you are paying for. Licence fees start when the subscription starts, not when your team starts using the org, so time the purchase for week 1 rather than signing. What sits inside those ranges, and how to read any quote, is in how much Salesforce implementation costs in NZ.

Frequently Asked Questions

Can a Salesforce implementation really be done in two weeks? Yes, at the short end of SAASKOOL's published 2 to 4 week range for Starter Suite (as at September 2026), when users are few, the data is clean and one person can decide on the spot. The phases are compressed, not skipped.

Should we clean our data before we start? Yes. Every duplicate and dead record removed before kick-off is time the migration phase does not spend on it. Start with one list of current customers and one of open deals, and decide what you can leave behind.

How much of our team's time does it take? For the build itself, the only hours SAASKOOL publishes are its own: 2 hours of live team training on the Starter package and a 4-hour role-based training workshop on the Professional package. Beyond that, expect one decision-maker in week 1, quick answers in weeks 2 and 3, and the whole team in week 4.

What happens after go-live? The support window on the package: 30-day post-launch support on Starter and 60-day post-launch support on Professional (as at September 2026), during which we monitor adoption and adjust. After that, someone in your business owns the org, or a fractional admin does.

Does a longer implementation mean a better one? No. Length follows scope: more users, an integration, more automation. A project that runs long for the same scope is usually waiting on data or decisions, and delivers the same org later. Ask what the extra weeks are buying.

---

Our pricing page shows the package behind each timeline; contact us when you are ready to put dates on it.