Services

Three scoped packages, and a no-charge review to start. Each one states what I deliver and how it begins, so you know what you are buying.

To start

No charge. You describe the problem and I send back a one-page written diagnosis, with the three things I would fix first.

What you get: A one-page written diagnosis.
The three priorities, ordered by impact.
A recommendation on where to go next.
Who it is for: Anyone with an AEP or Real-Time CDP implementation and a specific problem, who wants a second opinion before hiring anything.
How it starts: You email me the problem. If you want, with screenshots of the schema, the segment or the journey.
Turnaround: Five business days from the moment I receive the description.
Limits: I ask for no access and no credentials, and it is a single round. If more is needed, that is a project.

I review what you have and tell you what is wrong, what it costs to fix, and in what order to do it.

What you get: Prioritized findings on XDM schemas and identity resolution.
A review of Data Prep mappings and ingestion.
A review of data governance and consent.
Each finding with its impact and its estimated effort.
An ordered remediation plan.
Who it is for: Teams with AEP or Real-Time CDP already running that underperforms, or where nobody knows if it was built well. Often inherited from another firm.
How it starts: A context session and read access to the sandbox.

I design the model, configure ingestion and get the first journey live, with the documentation for you to carry on alone.

What you get: Schema design and identity model.
Ingestion configured.
First audiences activated.
First journey live in production.
Documentation for the internal team.
Who it is for: Anyone starting from zero, or sitting on a license they bought and never used.
How it starts: A use case workshop to scope the first deliverable.

I compare what the business needs against what the platforms actually do, and what each option costs to run.

What you get: Business requirements compared against real technical capabilities.
Integration and running costs that do not show up in the license price.
An argued recommendation.
Who it is for: Anyone deciding what to buy, between a suite, composable or warehouse-native. Before signing, not after.
How it starts: A requirements workshop with business and technology.
What this is based on: I have been on both sides of the RFP table: I won one bid against Big 4 firms, and I have evaluated vendors on the client side.

Rates are discussed by email. I do not publish figures or ranges, because they depend on scope.