Salesforce Consulting
An architect’s written opinion before you spend build budget — what your org is actually doing, what it is costing you, and the shortest route to the outcome you want.
01
The problem
Why people call us about this.
A
Every change costs more than the last one and nobody can explain why.
B
Two partners have quoted wildly different numbers for the same brief.
C
You are about to sign a large build and want a second opinion first.
02
What’s covered
The Salesforce we actually configure.
Advisory work with a deliverable at the end, not a relationship. Every engagement below produces a document you keep and could hand to another partner.
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 do we actually get at the end?
A written document: findings ranked by what they are costing you, each with an effort band and the cost of reversing it later, plus a prioritised roadmap. You could hand it to a different partner and they could act on it — that is the test we hold it to.
How long does an org health check take?
Two to three weeks. About a week inside your org with read-only access, a week writing, then a session walking your team through the findings rather than emailing you a PDF.
Will you just recommend your own build work?
Around half of our audits conclude that the process needs changing rather than the org. Where a build genuinely is warranted we quote it, and you are free to take the document elsewhere — several clients have.
Can you review a proposal from another partner?
Regularly, and it is some of the most useful work we do. We read their scope against what is actually in your org and tell you what is missing, what is priced oddly, and which parts are harder than the proposal implies.
Other lines