Salesforce Implementation
Sales, Service or Revenue Cloud configured around how your business actually runs — security model, automation and reporting designed from your process, not lifted from a template org.
01
The problem
Why people call us about this.
A
You bought licences months ago and the team is still living in spreadsheets.
B
A previous partner configured it, left, and nobody can explain why anything is the way it is.
C
Reporting cannot answer the two questions your board asks every month.
02
What’s covered
The Salesforce we actually configure.
A first implementation decides what every change after it costs. These are the parts of the platform we set up, and the order we set them up in.
03
How it runs
Five phases, and what you see at the end of each.
01 · Week 1
Inventory
What exists, who owns it, and which system is really the source of truth. Almost always surfaces something nobody knew was live.
A written map
02 · Weeks 2–3
Contract
The design in writing, with each decision and its reversal cost named. This is where we argue with the brief — before money is spent.
A signed scope
03 · Middle
Build
Built against the contract and reviewed against it. You see working software every two weeks, in your own sandbox.
Fortnightly demos
04 · Late
Prove
Volume testing at twice expected load, deliberate failure injection, and a replay run with your team watching.
A test evidence pack
05 · Final week
Hand over
Runbook, monitoring, escalation path and a named owner on your side — then a month watching it together before we step back.
Runbook and owner
04
First call
Thirty minutes. Three answers.
You speak to a certified architect, not a sales engineer. No deck, no discovery fee, and no obligation to go further — you leave the call with three things whether you hire us or not.
Whether this is even the right line
About a third of the time it is not, and we say so. Usually the ask is custom development when the real problem sits in the data model underneath.
A shape and a range
Roughly how long, roughly how many people, and the band it falls in. The firm number follows discovery about two weeks later, and it holds.
The two risks we would flag
The things most likely to blow the timeline on a project like yours — named on the call, before anyone has signed anything.
Book it for this week.
Pick a slot directly in the calendar — most questions get answered inside the thirty minutes.
05
FAQ
Asked on nearly every call.
How long until we are live?
Ten to sixteen weeks for a first implementation, depending on how many processes are in scope and how clean the data is. If you need to be live sooner than that, the Quickstart package is the more honest answer.
Do you migrate our existing data?
Open records are mapped and reconciled against source before anyone logs in. Deep historical archives are a separate decision — often they belong in cheaper storage rather than in Salesforce, and we will say so.
What if we already started and it stalled?
Roughly a third of our implementations are rescues. We inventory what exists before proposing anything, and we usually keep more of the previous work than clients expect.
Who trains our team?
We do, in your org with your data — not a demo org. Admin and end-user sessions, recorded, with a runbook you keep and can re-use when someone joins.
Other lines