IMPLEMENTATION
A Salesforce rollout your team doesn’t have to be talked into
We implement Sales, Service, Experience, Marketing and Data Cloud in two-week sprints, with migration and adoption planned from day one rather than bolted on in the last fortnight.
Most failed implementations were competent builds of the wrong thing. Someone documented the process as it’s described in a policy document rather than as it happens, and the gap only surfaces when a rep tries to log a real deal on a real Tuesday.
We open every implementation by watching the work. Two weeks of discovery gets us the actual decision sequence, the systems people alt-tab to, and the spreadsheet everyone swears they don’t use. That becomes the data model, not the org chart.
From there we build in two-week sprints in your sandbox. You see working configuration at the end of every sprint, with your own data in it. Nothing is described in a slide that hasn’t been demonstrated in the org.
What you get
- Working software in week three. Not a discovery deck. Sprint one ends with configuration you can click.
- Migration rehearsed twice. Two full dry runs and a reconciliation report before production is touched.
- Adoption designed, not hoped for. Role-based training, in-app guidance, and a named champion per team.
- Integrations contracted up front. Field-level ownership agreed before a line of code, so nothing silently overwrites.
- A documented org. Data dictionary, automation map, permission matrix, release notes — handed over, not held hostage.
- Hypercare included. Thirty days of floor-walking and rapid fixes after go-live, at no extra cost.
What’s included
| Workstream | Included |
|---|---|
| Discovery | Process shadowing, systems inventory, data profiling, success metrics definition |
| Solution design | Object model, record-level security, sharing model, automation map, integration contracts |
| Configuration | Objects, fields, page layouts, Lightning record pages, list views, reports, dashboards |
| Automation | Flow, validation rules, approval processes, scheduled jobs, bulk-safe patterns |
| Development | Apex, LWC, triggers — only where declarative can’t reach, with 85%+ test coverage |
| Data | Cleansing rules, mapping, dedupe strategy, staged migration, reconciliation |
| Integration | REST/Bulk/Platform Events, middleware config, error handling and replay |
| Enablement | Role-based training, quick-reference guides, admin handover, in-app guidance |
| Go-live | Cutover runbook, rollback plan, comms plan, hypercare rota |
How we run it
01 Discover (1–2 wks) · 02 Design (2–3 wks) · 03 Build (2-wk sprints) · 04 Migrate & validate · 05 Launch & enable · 06 Improve Full detail on /process/.
What you receive
Solution design document · Data dictionary · Automation map · Permission and sharing matrix · Integration contracts · Migration reconciliation report · Cutover runbook · Training pack (per role) · Admin handover session (recorded) · 30-day hypercare log · Post-launch scorecard
Common questions
How long does a Salesforce implementation take?
A single-cloud implementation for a team of 20–80 users typically runs 8–14 weeks end to end. The two variables that move it most are data quality and the number of systems that must exchange records.
Can you work with our internal admin?
Yes, and we prefer to. Your admin’s knowledge of the business is the fastest route to a good data model.
What if requirements change mid-build?
They will. The backlog is shared and re-prioritised each sprint; changes that alter total scope get a written impact note before they’re accepted.
Do you migrate historical data?
Usually a defined slice of it. We migrate what’s used, archive what’s needed for compliance, and resist the instinct to bring twelve years of dead records into a new org.
Who owns the org after go-live?
You do, entirely — including all documentation and source control. Managed services is a choice, never a dependency we engineer in.
What does hypercare cover?
Thirty days of priority response, daily check-ins in week one, on-the-floor support for the first full business cycle, and a fortnightly fix release.
Ready to scope a rollout?
Bring your current process, your systems list and your worst spreadsheet. We’ll tell you in thirty minutes whether this is a 6-week or a 6-month job.
Start here
Tell us what your CRM is getting wrong
Thirty minutes with a consultant, not a salesperson. You’ll leave the call with at least one thing you can fix yourself — whether or not you hire us.
Prefer email? hello@zeptglobal.com · Typical reply time: one business day