Services
The system underneath your marketing, built to outlast the engagement.
Five engagements, one discipline: customer data collected properly, unified once, and put to work where revenue happens.
Architecture, data strategy, tracking, customer data platforms, and lifecycle automation, delivered by an independent MarTech consultant who sits on your side of the vendor table. Every scope ends with your team running the system.
Programs for Vodafone Italy, Sky Italy, Unipol, De'Longhi, Leroy Merlin, among others.
- No vendor commissions
- Handover in every scope
- Remote-first, across time zones
The system underneath
top to bottom
- StackMarTech ArchitectureWhich tools, connected how, and why.
- GovernData StrategyWhat is worth measuring, and who owns it.
- CollectTracking ImplementationSignals captured cleanly, with consent enforced.
- UnifyCDP ImplementationOne profile across web, app, and CRM.
- ActivateMarketing AutomationLifecycle programs that run on that profile.
Each engagement fixes one layer. Together they are one system your team can run without me.
The five engagements
Pick the layer that is broken.
Each one is scoped end to end, discovery to handover, with the in-house team operating it afterwards.
Start from the problem
Nobody wakes up wanting a CDP. They wake up with one of these.
Pick the sentence that sounds most like your Monday. It points to the engagement that usually fixes it.
Fix the unify layer
CDP Implementation
Fragmented profiles are a unification problem, not a reporting one. A CDP program lands one identity across web, app, and CRM, with consent carried into every destination and the first audiences activated before the platform is fully finished.
See the CDP engagementOne operating discipline
Five different problems. The same four movements underneath.
- 01
Discovery
Audit what exists: sources, identity logic, consent posture, contracts, reporting. The current state fits on one page before anything gets designed.
- 02
Design
The data model, architecture, or framework, written down with the trade-offs. Documented for the people who inherit it, not for the kickoff deck.
- 03
Build
In production behind a release plan with rollback. Paired with your engineers and marketers, not around them.
- 04
Handover
Runbook, enablement sessions, and a team that owns the system. The program does not collapse when I leave.
Handover is in scope
Every engagement ends with your team running the system. Enablement is part of the work, not a favour at the end.
No vendor commissions
The engagement fee is the only revenue from the project. Recommendations stay honest and procurement stays comfortable.
Consent is a first-class signal
TCF and GPP states travel with the data into every destination. No quiet leaks, no after-the-fact retrofits.
Scope before price
Cost and timeline are scoped in discovery against the real shape of your stack. Never quoted blind, never from a rate card.
Track record
Programs shipped across telco, insurance, retail, travel, and media.
Most delivered as part of an in-house team or a lead consultancy. Names listed with permission.
Vodafone Italy
Telecom
Unified customer data across web, app, and offline for the first CDP rollout in the Vodafone Group
Sky Italy
Media & Entertainment
Set up measurement for a new web and mobile product, validated across both platforms
Unipol
Insurance
Brought five disconnected data systems into a single customer view
De'Longhi Group
Consumer Electronics (Global)
Ran CDP discovery, assessment, and vendor selection for a global Consumer Electronics group's 35+ tool MarTech stack
Leroy Merlin Italy
Retail
Turned eCommerce browsing data into audiences for paid media activation
Twinset
Fashion
Wired Braze into the Tealium CDP across web, app, and in-store for a fashion brand
Edenred
Corporate Benefits
Built the data collection layer from requirements through end-to-end validation
ho.mobile
Telecom (MVNO)
Set up tag management and consent orchestration across all touchpoints
Before you pick
Questions that usually come before the intro call.
The ones that stop a prospect before they choose an engagement. Service-specific questions live on each engagement page.
How do I know which engagement I need?
Start from the symptom, not the service name. The section above maps the common ones. When it is still unclear, the intro call usually settles it, and when it does not, the first phase is a short discovery that names the right engagement before anything larger is scoped.
Can engagements be combined?
Yes, and they often are. Architecture feeding a CDP program, tracking rebuilt ahead of a CDP, or a data strategy that lands in a lifecycle rebuild. Combined work is scoped as phases with decision gates, so leadership can pause or pivot between them.
Do you work through agencies or consultancies?
Yes, often. The strongest fit is when the agency owns delivery and I sit on the data, MarTech, or measurement layer as a senior counterpart. Ownership lines get agreed before kickoff, and the end client is always named to me.
How are scope and pricing set?
Through discovery, not a price list. The intro call frames the problem, a written scoping document captures what success looks like, and the proposal lays out scope, deliverables, and commercial terms against your specific situation.
Do you work remotely or onsite?
Remote-first, from wherever the work is. Onsite for kickoff, mid-engagement working sessions, and any moment where being in the room unblocks a decision. Comfortable across European time zones and beyond.
Next step
Bring the messy version of the problem.
A short call usually saves weeks of back-and-forth. You describe the situation, I ask the questions that surface what is actually being asked. No deck, no pitch.