Salesforce Quickstart Packages
Fixed scope, fixed price, four to six weeks. A clean Salesforce start for teams who need to be live this quarter rather than perfect next year.
01
The problem
Why people call us about this.
A
You need to be live this quarter and a six-month programme is not an option.
B
A small team is drowning in spreadsheets and shared inboxes.
C
You want to prove the platform internally before funding a bigger build.
02
What’s covered
The Salesforce we actually configure.
A deliberately bounded implementation. You get a working org with your data in it and your team trained — and a written list of what we did not do, so the next phase is honest.
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.
What is actually excluded?
Custom code, integrations beyond a single data import, more than three customised objects, and anything needing a bespoke security model. The exclusions are listed in writing before you sign, because that is the part people get burned on.
Is the price genuinely fixed?
Yes, for the scope in the document. If you change the scope we quote the change openly rather than absorbing it quietly and putting it on a later invoice.
What happens after the four weeks?
You get a written phase-two backlog. A good number of clients stop there for six months and run on what they have, which is a perfectly reasonable outcome.
Is this just a worse implementation?
It is a smaller one — the same architect sign-off, far fewer decisions. The real risk is outgrowing it in a year, which is exactly why the phase-two backlog is part of the deliverable.
Other lines