Scoping · Ref. ST-2026
Scope it before you choose an integrator
Two weeks to write down what you will build, in what order, and what every integrator has to quote.
Who I am
I am Sébastien Tang, a programme lead based in Seoul. I scoped Disneyland Paris’s move to Salesforce, ran Lacoste’s Customer 360 programme and L’Occitane’s Service Cloud delivery, and I now train Salesforce administrators.
The problem
Usually the integrator comes first. It discovers your processes while it prices them, and each quote depends on what it understood in a few workshops. The quotes do not compare, and the scope moves during the project.
Scoping reverses the order: the scope is written before the tender.
What you have at the end
- A map of your processes as they run today, with what gets stuck.
- The scope of the first release, written to go into the tender as is.
- A shared pricing grid: every integrator fills in the same lines, so the answers compare line by line.
- The order of work: what gets built first, what waits, and the decisions to take before you start.
How it runs
- A 2-hour kick-off, three or four 2-hour workshops with your process owners, a 2-hour readout.
- Everything happens on video, on Paris hours.
- Two weeks from kick-off to readout.
Price
€4,000 excl. VAT, fixed. Half when you order, the rest at the readout. A trip to France is possible, expenses on top.
What I do not do
- I do not configure. Scoping prepares the work of whoever configures, integrator or freelancer.
- I take nothing from the integrators or freelancers I help you choose.
Done before
Disneyland Paris, 2022: the audit of B2B processes came before the integrator was chosen. Every integrator priced the same scope.
Read the programmeAfterwards
You leave with a file you can use on your own. Running the rollout and training your teams remain possible afterwards, on quote.
The scoping checklist
What gets decided, in what order, and what you have at the end, on one page. To take stock on your own before you call an integrator.