How the work runs
Every week has a deliverable.
Including the first one.
Consulting goes wrong in the gap between the kickoff call and the first thing you can look at. This is what happens in that gap, week by week, and what you are holding at the end of each one.
The four phases
What happens in each phase?
The order matters more than the speed. Every phase ends with a document you keep, which is what makes the next phase arguable rather than assumed.
Discovery
Working sessions with the people who actually use the system, not only the ones who bought it. Objects, stages, roles, sharing and reporting, decided and written down. Where two teams disagree, that disagreement is recorded rather than silently resolved by me.
You receive: a written data model and a scope document listing what is in and, more usefully, what is explicitly out.
You pay: nothing before you sign the scope. The first two weeks, with up to four calls, lead to it, and if you do not go ahead, nothing is owed. Where a large org needs longer, the rest of discovery becomes the first part of the signed work, inside its price.
Build
A sandbox first wherever the org has one; where it has none, every change is backed up, tried as a dry run, deployed by named file and read back. You get access from day one and a walkthrough every week, so the first time you see the system is not the week it goes live. Changes are logged as they are made, not reconstructed afterwards.
You receive: a working sandbox, a weekly change log, and a running list of decisions taken.
Launch
Migration dry run, then the real one. User acceptance testing with a written script rather than "have a look and tell me if it seems fine". Your team has two weeks to test, then five working days to sign the acceptance certificate or name a defect in writing; a named defect is fixed and tested again, and without one the stage counts as accepted. Launch is never scheduled into quarter end, because the people who would find the problems are closing deals that week.
You receive: a UAT script with results, a migration report with row counts, and a rollback plan you hopefully never open.
Handover
A week of structured transfer, then thirty days of support while your team takes the wheel. The measure of success is not that the system works. It is that someone inside your company can change it without calling me.
You receive: administrator documentation, recorded walkthroughs, thirty days of support after handover and a sixty day warranty on what was built.
The uncomfortable questions
What if something goes wrong?
What if the estimate turns out wrong?
The estimator gives a figure before anyone has seen your org, so it can be wrong. What cannot happen is the price moving upward after the scope is signed. If discovery uncovers work nobody knew about, it becomes a separate decision with its own price, and you are free to decline it.
What happens if the consultant is unavailable?
Everything is built inside your own org and documented as it happens, not summarised at the end. If I disappeared mid-project you would hold the data model, the change log and the sandbox, which is enough for another consultant to continue without starting over. That is the point of writing it down as we go.
Who owns the work?
You do. Configuration, documentation, flows, everything, in your org and under your licence. There is no proprietary layer, no managed package that stops working when the invoice stops.
Can the engagement be stopped early?
At any time, on fourteen days written notice, before work starts or during it. You pay for the work completed and for the time set aside for you in those fourteen days, never more than 40 hours, and whatever was paid in advance and not worked is refunded. You keep the documents produced up to that point. Before the scope is signed nothing has been paid, so stopping then costs nothing.
After the thirty days
What happens when the handover support runs out.
Every build includes thirty days of support after handover: questions about what was built answered and small adjustments made, up to eight hours in total. When the work runs in stages, each stage gets its own thirty days and eight hours, which end when the next stage starts. For sixty days after each stage is accepted, anything I built that does not meet the signed scope is fixed at no charge, outside those eight hours. After that there is continued support by the month, with a written scope, a fixed price and a named end date. It also covers orgs somebody else built, which is the more common case.
Scope it before you talk to anyone.
Four estimators run in the browser and produce a document you can take to whoever signs the budget. No form, no call, no email address required.
Serhii Skrypnyk · Senior Salesforce Administrator · 7 Salesforce certifications · on the platform since 2018. Reviewed 6 November 2026.
One thing to settle early
Decide where the reasoning lives before the tools are connected.
Most teams discuss records somewhere other than Salesforce, and that is fine until nobody can find why a decision was taken. Six governance gaps that opens, each with a read only check, and three sentences that cost nothing if they are written before rather than after.