Applied AI systems. Build evidence. Operating model.

Problem

Campaign knowledge is scattered across emails, landing pages, outcomes, blog posts, project notes, and memory.

System emerging

A learning layer that turns historic campaign assets and project work into future campaign briefs, emails, LinkedIn posts, and reporting support.

Status

Emerging architecture, not finished production. The goal is a learning layer, not another generic content generator.

Problem

Enterprise form spam does not just create bad submissions. It pollutes Eloqua data, damages campaign reporting, wastes sales time, and creates operational noise across marketing automation workflows.

System built

Cloudflare Turnstile and Eloqua protection layer with exception queue, direct forwarding, accept/reject handling, secured reviewer access, and multi-form architecture. Applied to a real enterprise Eloqua marketing environment.

Why it matters

Proves Greg can build applied AI-adjacent workflow protection around real marketing operations, with anonymised enterprise usage evidence.

Problem

High-intent prospects abandon marketing forms before becoming visible in Eloqua, Salesforce, or campaign reporting.

System built

A governed recovery layer for partial intent capture, consent-gated recovery journeys, AI-assisted completion, and CRM handoff.

Why it matters

Recovers demand that already reached a form while keeping compliance and human handoff controls visible.

Problem

Audience targeting decisions made without structured evidence, scoring criteria, or human review controls at scale.

System planned

Planned AI-supported targeting workflow with scoring, evidence trails, manual accept/reject controls, queue management, export readiness, and a planned Cloudflare Worker backend with KV memory layer.

Why it matters

Planned human-in-the-loop design with evidence, scoring criteria, and operator review before any action.

Problem

Marketing teams need campaign, competitor, channel, and website intelligence pulled into one decision layer.

System built

A governed dashboard layer for turning scattered marketing signals into operator-ready insight.

Why it matters

Shows AI support for marketing strategy and evidence-led campaign decisions.

Problem

Client support workflows managed across email, files, invoices, status updates, and memory - with no shared visibility, request tracking, or billing transparency.

System built

A lightweight client documentation and request portal with email PIN access, durable documentation storage, client-specific visibility, and Cloudflare-backed migration. Built around Greg's real support and retainer workflow without Jira or Confluence overhead.

Why it matters

Proves Greg can build the operational layer around client work, not just isolated prototypes. The kind of system that forward deployed engineers design inside real customer environments.

Problem

Build progress disappears into chats, commits, and memory notes unless it is captured into reusable content.

System built

A local agent that turns Tanya memory and build records into draft-only weekly content packs.

Why it matters

Converts real build evidence into reusable marketing assets while keeping human review in the loop.

Problem

Eloqua form submissions need a durable identity stitching key where the visitor GUID is available.

System built

Page JavaScript reads the Eloqua visitor GUID where available, injects it into a hidden form field, submits it with the form, and stores it in a SYSTEM - Eloqua ID CDO.

Why it matters

Supports CDO processing, CRM matching, campaign reporting, and visitor/contact stitching without blocking submissions when GUID is unavailable.