Architecture & Data Assessment

€4,000-5,500 · 3-4 days

It reduces uncertainty before you hand over implementation, and gives every vendor the same technical baseline to estimate against.

When you need it

The Salesforce org has grown over time and no current documentation exists.
You have automation, customisation, integrations or data that nobody understands in full.
You are weighing an AI, CRM or data platform project, or a replatforming with material impact.
You need to work out whether a problem calls for remediation, refactoring, integration or a new architecture.
You want to prepare a technical specification before involving several partners.
You have received quotes that are hard to compare, because each partner made different assumptions.

What I examine

Salesforce and application configuration

standard and custom objects;
fields, relationships and actual usage;
flows, automation, code and dependencies;
limits, performance and components close to their thresholds;
features or licences going unused;
environments, release process and available documentation.

Data

data origin and systems of record;
quality, completeness, duplication and conflicts;
ownership and accountability;
data relevant to AI, reporting, processes or integrations;
privacy, retention and security constraints.

Integrations

connected systems and the data flowing in and out;
APIs, middleware and synchronisation patterns;
frequency, latency, error handling and monitoring;
dependencies on third-party vendors or systems.

Security and access

visibility and sharing model;
roles, profiles, permission sets and sensitive data;
constraints on making data available to AI processes or automation;
audit, traceability and compliance requirements.

Technical debt and priorities

components to fix before a new project starts;
components that can coexist with the new solution for a while;
technical and operational risks to factor into the estimate;
remediation work, held separate from the scope of the future project.

What you receive

A technical snapshot of the current state, grounded in evidence and documentation.
A map of the systems, data and integrations relevant to the scope.
The list of architectural constraints and principal risks.
The remediation work, in priority order.
A shared technical baseline for an RFP or for comparing different partners.
A document usable as input to architecture, budget and implementation planning.

Frequently asked

What access do you need?

Usually read-only access to Salesforce is enough, ideally on an up-to-date sandbox, plus whatever documentation exists on integrations, architecture and security. You do not need to share production data in the clear: the analysis can run on metadata, application structure, documentation and anonymised samples.

How is this different from the Readiness Assessment?

The Readiness Assessment answers "which initiative is worth starting and what does the organisation need for it to work". The Architecture & Data Assessment answers "which systems, data, integrations and constraints exist today, and what do they imply for the project". They are often sequential: the first sets direction and priorities, the second produces the technical basis for designing and estimating.

Do you produce the implementation plan?

I define the constraints, dependencies and preparatory work the plan is built on. The delivery plan is produced by your team or by the partner chosen for implementation. I can help you judge whether that plan respects the architectural direction and the agreed scope.