AI-powered advertising operations
I build the integrations connecting your paid advertising accounts, CRM and store data to Claude. Lead generation or ecommerce, in house or agency side. Your team gets the data and the workflows without building the technical infrastructure itself.
Compare paid media spend against qualified pipeline across all channels.
What I connect
Advertising platforms are the focus. The CRM or the store is not an optional extra, because platform-reported conversions are only half a picture. Which half matters depends on whether you sell a subscription or a basket.
Advertising
Campaign, ad group, keyword and search term data, conversion actions and budget pacing.
Advertising
Campaign and ad set performance, creative-level metrics, audiences, pixel and dataset health.
Advertising
Campaign and ad group reporting, creative performance and catalogue-driven activity.
Advertising
Campaign group and campaign reporting, lead gen form submissions and B2B audience data.
Advertising
Search campaign structure, keyword performance and asset-level reporting.
Revenue
Contacts, deals and lifecycle stages, so advertising activity can be read against pipeline rather than form fills.
Revenue
Opportunity and lead objects for attribution against closed revenue, not platform-reported conversions.
Revenue
Orders, revenue and new against returning customers, so platform-claimed ROAS can be checked against what the store actually took.
Measurement
Session, conversion and channel data as an independent check on platform-reported numbers.
Not every platform has an official Claude connector. Where one does not exist, the integration uses an authorised API, an MCP server or a vetted middleware layer. Which route applies to your stack is confirmed during the audit, before any build begins.
What I build
Each agreed platform connected by the appropriate route, with the choice documented and the limitations stated.
Scoped credentials with least-privilege access. Read-only by default, write access only where you have asked for it and approved the controls.
Metrics named and calculated the same way across platforms, so a conversion means one thing in every report.
Repeatable reporting that pulls, reconciles and assembles without anyone exporting a CSV.
Advertising activity read against lead quality and pipeline, not just platform-reported conversions.
Pacing against plan and flags on unusual movement, checked on a schedule rather than remembered.
Written documentation and a working session, so the setup survives you and does not depend on me.
Example workflows
Performance compared across every connected platform on one consistent definition of spend, conversions and cost.
Month-to-date spend against planned budget, with projected end-of-month land and a flag when something runs hot or cold.
Advertising activity connected to pipeline or store revenue, so channel decisions are made against money rather than platform-reported conversions.
Unusual movement in campaign metrics surfaced as a fact, with the other things that changed in the same window.
Structured performance summaries generated from connected data in your own format.
Claude reviews performance and proposes changes. A named person approves them. Nothing executes on its own.
I do not build unsupervised budget changes, autonomous campaign creation or publishing without approval controls. Where platform APIs permit write access, it is gated, capped and logged. That is a deliberate limit, not a technical one.
See it working
This is the shape of what gets built. Switch between lead generation and ecommerce, change the reporting period, and every figure, delta and answer recalculates. Open the creative and audience tabs, because that is where connected data earns its keep.
Creative
Cost per MQL for lead gen, revenue per impression for ecommerce. Never click-through rate. The best CTR on the demo account is also its weakest creative.
Audience
Which creative angle works for which audience, indexed against the account average. No single angle wins everywhere.
Fatigue
Creatives flagged as fatiguing while frequency climbs week on week, so a refresh happens before the next budget increase rather than after it.
Revenue
Lead to MQL to opportunity to closed, or click to basket to order to repeat purchase, with the conversion rate at every step.
Northfield Software is a fictional account and every figure in the demo is illustrative. A live build reads the same structure from your own connected platforms and CRM.
How it works
Accounts reviewed, connection routes confirmed, conversion definitions agreed and scope fixed in writing.
Platforms connected, authentication scoped, permissions set and data validated against the platform UI.
Agreed workflows built and run against live accounts alongside your existing process.
Numbers reconciled, documentation written, team trained and the setup handed over in full.
Who builds it
I am Tom Packham. Twelve years in paid media and over £50M of managed spend across Google, Meta, TikTok and LinkedIn. Every workflow here exists because I built it for my own client accounts first, broke it against live spend, and fixed it.
That is why this page is specific about what I will not automate. Most people selling AI integrations to marketers have never had a client ring them about a pacing miss, and it shows up in which decisions they are willing to hand over.
Pricing
£6,999
One-off. Four-week target implementation.
Scope is fixed in week one. Additional platforms and workflows are £900 and £1,400 each. Bespoke development and non-standard data sources are quoted separately. The timeline assumes account access in week one.
Scope your buildThe build is a one-off. There is no retainer attached to it and no subscription you have to keep paying to use what you own.
The first thirty days after handover are covered, so if a connection drops or something does not behave the way it did in testing, that is mine to fix rather than a conversation about scope.
After that, plenty of people want more: another platform connected, a workflow that only became obvious once they started using the first two, or someone to sit with the team while they take it further. All of that is available. Tell me what you need and I will scope it properly rather than selling you a retainer you did not ask for.
Talk about what happens nextGet in touch
A short call to go through your platforms, where your revenue data lives and what you want back. If the build is not worth doing for you, I will say so on that call rather than after you have paid for it.