Mode 01 ~40% of cases
Governance vacuum
No named owner for any cross-cloud decision. Drift compounds quarter over quarter. Most common.
Path C · independent review
The program is failing quietly. You need a written read this week.
When a Salesforce delivery slips three quarters and the steering committee keeps reading green, the issue is rarely the platform. It is the architecture, the governance, or the politics, and the SI in the room is not the one who can name it. The review delivers a written diagnosis the sponsor can act on, in one to two weeks, under NDA.
From €12k
Investment
1 to 2 weeks
Duration
1 architect
Team
< 24h
Reply SLA
Why it stalls
Every stalled engagement is one of these four.
The operating theory the assessment runs on. Four failure modes, in order of frequency. You will know which one by Friday of week 2.
Mode 02 ~30% of cases
Architecture debt
Configuration written for a use case nobody runs anymore. Layered, never refactored. Performance suffers, no one knows why.
Mode 03 ~20% of cases
SI capture
The party that built the problem is also the party reporting on it. The RAG status reflects the SI’s revenue, not the program.
Mode 04 ~10% of cases
Scope creep
Original requirements are still open, nobody renegotiated, and the SoW has been amended five times.
If you do not recognize any of these, the architecture probably is not the bottleneck. The discovery call says so honestly, before any contract gets signed.
What you get
Four written artifacts. Yours.
Documents the engagement leaves behind. No retainer required to keep them. No follow-on dependency by design.
- D1
Independent technical read
Architecture, automation, data model, security posture, integration patterns. Where it actually breaks, not where the RAG says it does.
- D2
Priced risk register
Every finding scored for severity, with a remediation cost range and a name attached to the decision that gets it done.
- D3
Recovery roadmap
90-day sequence of fixes, ranked by impact and political damage. Build-vs-stop options where they apply.
- D4
Sponsor brief
15 to 25 pages, written for someone who needs to make a decision this week, not next quarter.
Schedule
Shippable artifact at each milestone.
The timeline below is fixed. If discovery surfaces something that warrants a longer engagement, the SoW gets amended in week 1, not by surprise.
- Day 1-2 Access
NDA signed. Code, configs, governance docs, key interviews scoped.
→ Discovery memo - Day 3-6 Investigation
Independent technical review. No SI in the room. Engineer interviews under the same NDA.
→ Risk register and remediation candidates - Day 7-8 Briefing
Written findings. Verbal walk-through with the sponsor and the sponsor’s CTO.
→ Sponsor-ready brief, 15 to 25 pages - Day 9+ Steer
Optional ongoing architecture oversight role, scoped separately so the diagnosis stays independent.
→ Statement of work, by request
Methodology
Why the work is shaped this way.
Independent
No license resale. No implementation team to feed. The recommendation is allowed to be "stop."
Architecture-first
Prompts get tuned by anyone. Data access models get fixed by someone who has shipped them. Different problem.
Written, not presented
A report a CTO can mark up and take to the board survives the next staff change. A deck does not.
What clients say
“It's rare to come across a profile like his: the skill set to operate as a Salesforce architect and as a program manager at the same time. He turns difficult engagements into shippable outcomes.”
Pablo Corell Bover · Senior Salesforce Consultant, Cognizant
See full case studies → Best for / not for
Honest qualification.
A short list of who this engagement was built for, and a shorter list of who it was not.
Best for
- You suspect the program is not telling its sponsor the truth.
- You are closing a PE deal and need a fast read on a Salesforce-heavy target.
- You inherited an org with years of accumulated decisions you never made.
- A board review is on the calendar and you need a defensible diagnosis.
Not for
- You want a public review for marketing or analyst distribution.
- You are running a greenfield program with no delivery history to audit.
- You need the incumbent SI to approve the findings.
- The political answer is fixed and you want it laundered.
vs. an SI assessment
How this differs from a Big-Four engagement.
Independent architect
Big-Four assessment
€12,000 · 1 to 2 weeks
€60,000+ · 6 to 8 weeks
Sponsor-only by default
Findings shared with the SI that built the problem
NDA signed before scoping starts
NDA negotiated alongside the fee
Written brief, 15 to 25 pages
Slide deck, 60 to 100 pages
Independent of license resale
Tied to Salesforce reseller margin
Decision in 2 weeks
Decision in 2 months
Questions
Questions that come up in procurement.
If yours is not here, ask on the call. The answer will be specific.
Q01 Will the incumbent SI see the report?
Only if the sponsor decides so. The default contract is sponsor-only. NDA is signed before scoping starts. The SI hears about the findings the day the sponsor wants them to.
Q02 How fast can you read a Salesforce-heavy target?
For PE diligence, ten business days from access to written brief. The brief is short enough to read in the cab to the closing meeting and defensible enough to price into the deal.
Q03 What if the right answer is to stop the program?
Then the brief recommends that, with options for redeploying the budget. About one in three reviews ends here. It is the most expensive answer to deliver and usually the cheapest one for the sponsor to receive.
Q04 Do you talk to the engineers, or only the sponsor?
Both. The sponsor is the audience for the brief. The engineers are the source of the truth. The SI is usually neither.
Q05 Can you ride along during remediation?
Yes, on a separate engagement. The review is independent on purpose; the steer is optional and paid separately so the diagnosis stays clean.
Q06 Is this admissible in a contract dispute?
The brief is written under NDA for sponsor use. It has been quoted in two contract renegotiations and stood up. It is not a legal opinion and does not replace one.
Q07 Where are you based?
Paris and Seoul. The work is delivered remotely. One on-site day is available in week 1 for EMEA teams.
Q08 What languages do you work in?
English and French, written and spoken. Korean conversational.
Before you go
Take the AI Readiness Assessment → How AI-ready is your Salesforce org?
9 questions, 2 minutes, instant results. No signup required.