AI & CRM Readiness Assessment

In short

The AI & CRM Readiness Assessment establishes whether the company is ready to make an AI, agent, CRM, automation or data platform initiative work. It examines data, processes, architecture, security, governance, skills and value measurability. The output is not a score: it is the first realistic use case and the sequence of decisions needed for it to produce value. €2,400-3,000, two days, document and readout call.

€2,400-3,000 · 2 days + document + readout call

A platform can be sound and the company can still not be ready to use it properly. Those are two different judgements, and only the second one is about you.

The question it answers

The question is not:

Are Agentforce, Data 360 or an AI agent good products?

The question is:

Given our company's data, processes, people, systems and objectives, which is the first use case worth taking on, and what does it need in order to produce value?

The dimensions examined

Data

Quality, availability, ownership and reliability of the data the use case needs: where it lives today, whether conflicting sources exist, whether it is complete enough, and who is accountable for maintaining it.

Processes

The process you want to improve: is it repetitive, is it documented, do people run it consistently, how many exceptions does it carry, does the volume justify automation, and which outcome has to improve.

Architecture and integrations

Systems involved, data sources, dependencies, APIs and required integrations. The architectural choice sits here too: a Salesforce-native solution, Data 360, Snowflake, a point integration, or a headless architecture on ChatGPT, Claude, Slack, Teams or internal applications.

Governance, security and access

Accountability, permissions, sensitive data, roles, traceability and the decisions needed to use AI and automation under proper control.

Skills and ownership

Who will own the process, who will decide on priorities and who will maintain the solution after go-live.

Value and measurement

How to measure the result: against which baseline, with which metrics and over which horizon.

How it runs

  1. Initial collection - I go through the available documentation: architecture, roadmaps, integrations, data model, backlog, tickets, proposals already received and any material on the use case.
  2. Targeted interviews - short sessions with the key people: business owner, CRM lead, IT, data owner and, where needed, security or compliance.
  3. Analysis and readout - priorities, obstacles, dependencies, sequence of work and architectural scenarios, presented on a call with the people who have to decide.

What you receive

Frequently asked

Do you need it before or after choosing the partner?

Ideally before. Arriving at vendor selection with the use case, prerequisites and responsibilities already defined improves the quality of the proposals you receive and reduces the risk of buying work you do not need.

Who should take part?

Typically the business owner, the CRM lead, IT or the data owner, and the sponsor who holds budget or priority authority. The total time asked of your people is around 4-5 hours, spread across interviews and the readout.

Can the document be used in an executive committee?

Yes, it is built for that. It makes the decision, objective, risks, dependencies, indicative costs and required work visible. It is not a technical report to be filed away.

What if the conclusion is that we are not ready?

That is a useful result, and it happens often. The assessment sets out what is missing, which work takes priority and in what sequence to proceed. Sometimes the right move is to start from a simpler use case; other times it is to fix the data, the process or the governance first.

Related reading