Current-state audit
Org analysis: data model, automations, code, security model, integrations, performance.
Salesforce Solution Architecture
De-risk your Salesforce architecture decisions
An independent architecture review: a factual current-state assessment, a well-argued target, a realistic trajectory. So you can decide on facts, not opinions.
The situations we encounter
An architecture review is rarely triggered by chance. It almost always answers one of these signals.
The org has grown in successive layers: no one holds the full picture anymore.
Technical debt slows every release and makes every change more expensive.
Platform limits are discovered in production, never upstream.
Structural choices are made by the implementation partner, with no independent counter-expertise.
The security and data-sharing model has not been reviewed since the initial go-live.
Every major change becomes a risky project, for lack of architecture documentation.
What we do
A complete analysis of your org and its ecosystem, delivered as recommendations you can act on.
Risk assessment
Identification and prioritisation of technical risks, each qualified by its actual business impact.
Target architecture
A realistic target, aligned with your priorities, your teams and your budget constraints.
Trajectory
A sequenced roadmap: quick wins, structural workstreams, explicit dependencies and prerequisites.
Executive readout
Presentation to decision-makers: findings, options, well-argued recommendations. You decide.
Deliverables
Documents designed to be used: by leadership to decide, by teams to act.
- Executive summary for leadership
- Documented current-state assessment
- Target architecture: diagrams and guiding principles
- Risk register, prioritised by business impact
- Well-argued recommendations, with options and trade-offs
- Roadmap sequenced by horizon
- Architecture decision records (ADRs)
- Quick wins actionable immediately
How we work
A short, predictable sequence, scoped before any commitment.
Framing
Objectives, scope, access, schedule. A single point of contact on each side.
Analysis
Org review, targeted interviews with your teams, reading of integrations and history.
Synthesis
Findings, risks, target and trajectory. Everything documented and traceable.
Readout
Presentation to decision-makers, then detailed handover to technical teams.
Typical engagements
Typical situations we address.
Before a major investment
An industrial group wants to validate its Salesforce foundation before committing to a multi-year programme. The review establishes the org's actual state and de-risks the investment decision.
An org inherited from several partners
A company in the energy sector has accumulated layers of customisation across successive vendors. The review restores a complete picture and prioritises remediation.
An independent second opinion
A CIO wants to test the implementation partner's recommendations against an external view before making a structural decision.
Frequently asked questions
What CIOs and architects ask us before commissioning a review.
How long does an architecture review take?
It depends on scope: a few weeks for a targeted domain, longer for a complex, heavily integrated org. The initial framing fixes duration and cost before any commitment.
Do we need to mobilise our teams?
Yes, but in a limited way: targeted interviews and read-only access to the org and documentation. We minimise the impact on deliveries in progress.
Do you work with our implementation partner or instead of them?
Alongside them. The review is independent but collaborative: the goal is to improve the existing setup, not replace it. Findings are shared with all parties.
Does the review cover security?
Yes. The data-sharing model, profiles and permissions, and the exposure points of integrations are part of the standard analysis.
What happens after the readout?
You are autonomous: the deliverables are designed to be used by your teams without us. Implementation support remains possible if you want it, but it is never a condition.
A doubt about your architecture?
A first conversation is often enough to frame the question. No commitment.