Building Marketing Technology That Connects Data, Teams and Decisions
I’m a Marketing Technology Product Manager and hands-on Solutions Developer.
I turn complex business requirements into scalable products — from user discovery and solution architecture through development, integration and adoption.
CRM · Customer Intelligence · Marketing Operations · Data Products · Automation
Representative workflows shown within a simulated client environment.
Product Thinking, Built and Shipped
I hold the product decisions and write the implementation. That combination is what makes the architecture below survive contact with real operations.
Product Management
Discovery with the people who will use the system, problem definition with a measurable outcome, prioritisation, and responsibility for adoption after launch.
- User research
- Product definition
- Roadmap & prioritisation
- Stakeholder alignment
- Adoption & enablement
Solution Development
Hands-on implementation. I build the products I define — interfaces, workflow logic, and the integrations that connect them to operational systems.
- Front-end development
- Workflow & automation
- API integration
- Custom tracking
- Reporting build
Systems & Data
The architecture underneath: shared data models, identity resolution, controlled taxonomies, and reporting layers that hold their definitions.
- Solution architecture
- Data modelling
- Identity resolution
- Taxonomy governance
- CRM & martech platforms
Marketing Technology Ecosystem
A conceptual reference model for how the products below connect. Each layer has a defined responsibility, and each product occupies a specific position within it. Select a layer to see its inputs, outputs and the systems it touches.
Five Products, One Operating Model
Five products solving different operational problems across one connected MarTech ecosystem — each shown as a working interface built with simulated data, with the process and architecture behind it available to explore.
Marketing Planning & Workflow Platform
One operating surface for planning, ownership and approvals across every channel.
- Rolled out view by view so no team had to change everything at once.
- Operating rules written and owned by the teams, not imposed by the tool.
- Weekly bottleneck review turned approval delays into a managed metric.
Behavioural Intelligence Infrastructure
Website activity becomes structured CRM intelligence the moment it happens.
- Insights reviewed monthly and retired when advisors stopped acting on them.
- Follow-up SLAs agreed with the sales team rather than imposed by the system.
- Taxonomy changes go through review so the score stays comparable over time.
Cross-System Data Architecture
Fragmented systems connected into one model, so every platform describes the same customer the same way.
- Data dictionary maintained as a product artefact, not a one-off document.
- New events reviewed against the taxonomy before implementation.
- Definitions owned jointly by marketing and analytics to keep them enforced.
Commercial Reporting & Decision Layer
Stakeholder requirements to KPI definitions to a reporting product leadership actually decides with.
| Name | Segment | Region | Score | Recent activity | Recommended action |
|---|---|---|---|---|---|
| Mei Laurent | VIP | Europe | 98 | Opened advisor email | Advisor call within 48 hours |
| Theodore Nakamura | VIP | Europe | 98 | Repeat-viewed sculpture | Advisor call within 48 hours |
| Mei Ashford | VIP | Europe | 98 | Saved 3 artworks | Advisor call within 48 hours |
| Beatrice Okonkwo | VIP | Asia Pacific | 98 | Opened viewing room | Advisor call within 48 hours |
| Ines Voss | VIP | North America | 98 | Inquired about Kusama | Advisor call within 48 hours |
| Greta Bridger | VIP | Europe | 98 | Viewed Hockney print | Advisor call within 48 hours |
| Greta Chen | VIP | North America | 98 | Saved 3 artworks | Advisor call within 48 hours |
| Eleanor Tanaka | VIP | Europe | 98 | Viewed Hockney print | Advisor call within 48 hours |
Identity-Aware Experience Platform
One website, three identities — the experience adapts to who is looking.
- View artworks
- View exhibitions
- Enquiry CTA
- Limited account features
How I Build Products
The same lifecycle runs across every product below — from discovery with the people who will use the system, through architecture and build, to the adoption work that decides whether it lasts.
These products are developed within a global organisation operating across five countries, requiring alignment across teams with different workflows, priorities and levels of technical maturity — and careful handling of commercially sensitive client and sales information.
Discover
Start with the people doing the work. I sit with teams through real cycles rather than collecting requirements in a workshop, because stated process and actual process rarely match.
Two full campaign cycles shadowed before a single screen was designed.
- Shadowing and interviews
- System and tooling audit
- Existing workaround inventory
I work where product, technology and marketing operations meet — a marketing technology product professional with ten years’ experience across contemporary art, cultural institutions and premium international businesses.
My work starts with the problem rather than the platform. I work with users to understand how they operate, translate their needs into requirements, assess technical feasibility, design the solution and then build it, from data models and workflows to APIs, automation and interfaces.
At White Cube, I combine product ownership with hands-on solution development across a global organisation operating in five countries. That means navigating different teams and workflows, commercially sensitive client information, and the change management required to turn new technology into working practice.
I’m particularly interested in turning fragmented information and manual processes into connected systems that people actually use.
