AI & CRM Architecture Advisory

€2,400-3,600 per month · 2-3 days a month, one quarter minimum

For when AI and CRM decisions have become continuous, but do not yet justify a role on the payroll.

When you need it

You have several AI, CRM or data initiatives running and have to set priorities.
The partner handles delivery and development, but you need someone on the client side to lead architectural decisions.
You are building a roadmap to present to leadership, IT, security or an investment committee.
You have proposals, quotes, platform choices or architectural designs to assess.
You have completed an assessment and now need to turn it into decisions and action.
The work is recurring, but does not justify a hire.

What we work on

Roadmap and priorities

What to do, in what order and which initiatives to defer, tying every investment to a process, an owner, a dependency and a value metric.

Architecture

Decisions on platforms, data, integrations, agents, security and evolution over time. This can involve Salesforce, Data 360, Snowflake, APIs, MCP, ChatGPT, Claude, Slack, Teams, proprietary systems or a combination.

Governance

Accountability, decisions, access, approval processes, risk management and go-live criteria, defined together with your team.

Partners and proposals

Assessment of offers, work plans, proposed architectures, risks, assumptions and change requests.

Value and measurement

The metrics that show whether an initiative is generating value, and that let you defend the budget in later phases.

How a quarter runs

First month - we start from the current situation, open decisions, objectives, stakeholders and the calendar of significant choices. Out of that comes the quarter's roadmap and the priorities the days will go to.
Second and third month - the days go where they are needed: reviewing a proposal, defining an architecture, preparing a committee, assessing a partner, a governance workshop, defining metrics.
End of quarter - decisions taken, results reached, risks still open and what comes next. If continuing support is no longer needed, the engagement ends; if it is useful to carry on, we define a new scope, duration and set of objectives.

What it does not include

Implementation or configuration, application development, hands-on project management, on-call support or standby, permanent on-site presence, licence resale.

Availability is limited and the days are planned at the start of the month. If a steady need for more than three days a month emerges, the problem is not solved by increasing my commitment: it calls for an internal hire or a delivery partner with dedicated capacity.

Frequently asked

How is this different from hiring an architect?

An in-house architect is the right call when the volume of decisions, coordination and evolution is constant. This engagement is built for a phase of significant but bounded change: a roadmap to build, a platform choice, an AI programme to set up, a partner to select, an architecture to define.

What happens if more days are needed?

First we revisit priorities. If demand consistently exceeds the agreed capacity, that is the signal you need a dedicated internal role or a partner with delivery capacity. I can help you define that profile or that scope, but I do not increase availability beyond the agreed limit.

Do you implement what we decide?

No. Delivery is done by your team or by a partner you choose. My role is to set the direction, assess the plan and check the architectural decisions during execution.