I have rebuilt how a marketing function operates using AI, one workflow at a time. AI is now the default mode for content, reporting, advertising, and customer intelligence. These are the systems I built, the workflows they permanently changed, and the teams that now use them.
I believe a marketing team of one can outperform an agency if it owns its own automation stack.
Systems featured below have been sanitised to remove company branding and proprietary data.
AI should be the path of least resistance for every marketer, not an extra step. Every system in this portfolio was built to remove a manual process and replace it with an AI workflow the team can use without friction. The goal is not automation for its own sake. The goal is permanent workflow transformation: marketers who start every task with an AI tool because doing it any other way feels slower.
AI-powered support, shared between marketing and customer service.
The chatbot replaced a USD5,000/month vendor contract. The more significant change is operational: marketing and technical support now share responsibility for keeping the knowledge base current. Marketing owns product announcements, campaign context, and pricing updates; support owns integration guidance, error resolution, and account queries. Two teams now maintain an AI system together as a default part of their workflow.
Autonomous campaign management.
The most technically complex system in the portfolio. Five interconnected workstreams replacing manual agency processes across Meta, Google Ads, and TikTok, built on a self-hosted production n8n instance. The system runs autonomous campaign setup, optimisation, and reporting at the infrastructure level the team would otherwise outsource to agencies.
AI-powered performance reviews. Agencies are accountable. Teams arrive better informed.
Built to establish objective performance measurement across APAC, tracking three media agencies that run paid digital across Meta and Google Ads. The system creates a data-normalised accountability layer between the client and its agencies, replacing subjective slide deck reviews with repeatable AI analysis.
The real change is behavioral. Marketing teams now walk into agency review meetings with an AI meeting assistant active on screen. They query it in real time: what drove the performance delta, which campaigns underperformed against forecast, what to push back on. The agency prepares differently because the team arrives better informed. The dynamic in the room has changed.
Content production pipeline for guides, educational explainers, and localised market variants.
This pipeline produces the high-volume, content-team-owned work that sits alongside subject-matter expert authoring: guides, educational explainers, vertical landing pages, localised market variants. It does not replace the SME-authored thought leadership that lives elsewhere in the content function. It handles the templated production work that otherwise gets outsourced to agencies or deprioritised due to capacity.
The same architecture runs trilingual at PURE (EN, TC, SC) and replaced two content agencies. For a global business with regional content needs, the unit of work is not one article: it is one canonical piece plus its market variants, social derivatives, SEO metadata, and structured data schemas. The pipeline produces all of them from a single brief.
Sample output shown is illustrative of the pipeline producing one canonical article plus its social derivatives, SEO metadata, and structured data schema from a single brief.
AI ad creative at speed. The same architecture extends to organic content templates for the wider team.
A standalone application built with React and deployed on Cloudflare Workers and Pages, with Cloudflare R2 for image storage. Accepts a reference image, uses Claude API to describe the environment, then calls FAL.ai to generate AI images based on that environment description. Four visual types are supported: promotional with customisable offer text, UGC-style, community-based, and editorial ghost showing a person standing alongside a ghost-like figure representing an aspirational identity. All generated assets are resized into 9 formats covering Google PMAX, Meta, and Programmatic Display specifications. Logo compositing runs in-browser using Canvas API with three positioning options. Text overlays are fully customisable before export with font and size preserved across edits.
The underlying architecture, prompt-driven creative generation with brand constraint inputs, is format-agnostic. The same system is being extended to generate organic content templates for the social media team, who currently produce content manually. One build, multiple use cases, expanding adoption.
Every review answered. AI-drafted, human-approved, sent in minutes.
A market-agnostic review-response architecture, currently in production across two of the client's markets but designed so adding a new market is a configuration file, not a code change. Locations, Telegram approval channel, brand voice, and review-scoring thresholds are all per-market parameters. The same workflow scales to as many markets as a business operates in.
Replaced a manual, inconsistent process where reviews were answered sporadically. Every review now receives a contextual, brand-appropriate response with a human final check before anything is published.
Each market is a configuration: location list, Telegram channel, brand voice, escalation thresholds. Adding a new market means a new config file, not a new workflow. The architecture has no hardcoded market assumptions.
In production today across Hong Kong and Singapore, demonstrating the multi-market pattern. Same Claude-drafted, human-approved flow runs end to end in each market against its own Google Business Profile and Telegram channel.
From static reports to strategic dialogue. The team now queries their own data through AI.
Regional Instagram and Facebook performance analysis covering both markets. Each region pairs a scheduled analysis workflow with a conversational chat assistant, turning one-directional reports into interactive intelligence tools the social team can query in plain language.
The team was already doing ad hoc AI analysis by manually copying Instagram data into external LLMs. What changed was the setup cost: zero. All data is structured, embedded, and ready. The AI chat is open during weekly performance reviews. The team asks it for content recommendations, underperformance diagnoses, and posting schedule optimizations without leaving the dashboard. The behavior shifted because the friction disappeared.
Production-grade standards for AI and automation systems.
This framework governs how AI and automation workflows are designed, deployed, and maintained in production environments. It is designed to be ecosystem-agnostic, the patterns, tier classifications, and governance requirements apply regardless of whether your organisation runs on Google Workspace, Microsoft 365, or any other stack. The specific tools referenced are illustrative defaults and can be swapped for your equivalents without changing the underlying standard. This framework exists because sustainable AI adoption requires consistency: every tool built to the same standard, every failure handled the same way, every team customer able to trust that the system will behave predictably. Reliability is the foundation of adoption.
Use when only you run the workflow, no stakeholders are waiting for output, and a failure would only affect you. Suited to ad-hoc analysis or one-off internal pulls.
Use when something is explicitly tagged as a POC, proof of concept, or quick demo. Built to validate an idea, not to run in production.
The standard for every workflow unless explicitly stated otherwise. If a workflow runs on a schedule, feeds another team, or touches real customer data, it must meet Tier 2.
Reference standard, never auto-applied. Triggered only when the operator explicitly asks for it, or when Tier 3 risk is flagged and confirmed. Includes everything in Tier 2 plus a heavier operations layer.
| Function | Default tool | Alternatives accepted |
|---|---|---|
| Notifications | Telegram | Microsoft Teams, Slack, or equivalent |
| Logging | Google Sheets | SharePoint Excel, Airtable, or equivalent |
| SendGrid or equivalent | Any transactional email platform | |
| File storage | Cloudflare R2 | Google Drive, OneDrive, S3, or equivalent |
| Database | Supabase | Any managed Postgres or equivalent |
| AI generation | Claude API | Any LLM API depending on task requirements |
| CRM | CRM platform | HubSpot, Salesforce, or equivalent |