How I Work
Architecture decisions. Honest trade-offs. Delivery reality.
Marketing technology projects rarely fail because a platform is missing one feature. They fail because the architecture is unclear, the data model is weak, the operating model is underestimated, or the organisation expects a tool to solve a problem it has not yet defined.
That is where my work usually begins.
I help companies make better decisions about Customer Engagement Platforms, Marketing Automation, and cross-channel orchestration; not by starting from vendor promises, but from business objectives, data reality, integration constraints, and the teams that will have to operate the solution after go-live.
My role is not to make technology sound simple. It is to make complexity manageable enough to be designed, delivered, governed, and improved over time.
My Approach
Architecture first
Over time, I have learned that architecture usually decides the outcome long before the platform does. Platforms change, acronyms multiply, and product roadmaps evolve quickly. But the underlying data model, integration patterns, identity strategy, consent logic, decisioning rules, and governance model determine whether a MarTech stack will actually create value.
Before discussing features, I try to understand the system around them. What data exists? Where is the customer truth? Which systems own which decisions? How are audiences built, journeys triggered, conflicts and pressure rules handled?
The answers to these questions usually matter more than the demo.
Business-first, not business-only
Good MarTech architecture starts from business goals, but it cannot stop there. I work to translate executive objectives into practical architectural decisions, and technical constraints into language that business stakeholders can understand.
The goal is not to create elegant diagrams. The goal is to help organisations make decisions they can actually implement: connecting strategy, data, platforms, delivery capacity, campaign operations, measurement, and long-term maintainability.
Pragmatic and honest
I prefer useful truth over polished narratives. Every platform has strengths, limits, trade-offs, and contexts where it makes more or less sense. Adobe, Braze, Bloomreach, Insider, Iterable, Salesforce, Hightouch; all can be good choices, depending on the architecture, the maturity of the organisation, and the operating model around them.
Not every problem needs a new platform. Not every platform needs to become the centre of the stack. Not every AI feature changes the architecture. Not every "quick win" remains quick after governance, data quality, consent, and delivery reality are considered.
Independent judgment
I work inside an independent consultancy and I try to bring that same independence to every engagement. The right choice for a client should be based on their maturity, data landscape, business priorities, integration context, and ability to operate the solution.
That does not mean being theoretically neutral. It means being clear about why a specific platform, pattern, or roadmap makes sense in a specific context.
From strategy to delivery reality
I usually operate at the strategic and architectural layer, but always with delivery reality in mind. A MarTech strategy that cannot be implemented is just a slide deck. An architecture that delivery teams cannot maintain is technical debt with better typography. A roadmap that ignores operational maturity will collapse under its own ambition.
For this reason, I work closely with delivery, data, development, and campaign teams to ensure that architectural decisions remain grounded in what can actually be built, tested, adopted, and improved.
Knowledge transfer matters
I do not believe a good consulting engagement should leave the client dependent. A strong engagement should leave internal teams with better clarity, stronger decision-making criteria, more confidence in the platform, and a clearer understanding of how the architecture works.
The objective is not only to deliver a solution. It is to leave the organisation better equipped to evolve it.
The Kind of Work I Believe In
I believe good MarTech work should make things clearer.
Clearer for executives deciding where to invest. Clearer for marketing teams designing journeys and campaigns. Clearer for IT and data teams integrating systems. Clearer for delivery teams implementing the solution. Clearer for customers who experience the outcome.
The best architecture is not the most complicated one. It is the one that makes the right decisions easier, the wrong decisions harder, and future evolution possible.
The point is not architecture for its own sake. The point is to make better customer engagement decisions, reduce waste, and create a stack that can support measurable business growth over time.