Control X marketing automation plan
For Timo Schumacher, by Bryan Dianco, September 2026

One system.
Local buyers only.
Always revertible.

Every lead answered in minuteson the channel it came from
Ads shown only in Thailandlocation targeting on Google and Meta
Any change undone in one stepbackup taken before every change

Today

Leads go coldEnquiries wait. Nobody owns the follow-up.
Wrong buyersAds were targeted too widely. Homes start at 300k dollars, so the ads must only run in Thailand.
All manualEvery channel needs instructions from Timo.

What the best builders do

Pattaya rivals and the strongest builders abroad, checked against the same list.

Pattaya House Buildertoday
Phuket House Buildertoday
Casa MiguelPattaya
WandeegroupPattaya
Best abroadUS, Germany, UK
Price per square metre published
Warranty and insurance stated
Named client testimonials with year
Finished-project tour videos
Search ads as the main engine
Leads qualified before a salesperson calls
CRM tells Google and Meta which leads were real
Tracked from click to contract
+75%

qualified leads, at 43% lower cost, when a Thai developer let its CRM tell Meta which leads were real.

0

qualified opportunities from three weeks of pay-per-lead Meta ads for a luxury design-build firm abroad. Same story as the old agency.

Copy the trust signals. Keep Google as the engine. Use Meta to follow up, not to prospect. Reuse the video you already have.

Outside-in view from public sites and published case studies. Your own numbers come in week one, once access is granted.

Follow a lead

Press play, or tap any box. A lead qualifies with either a 300k dollar budget or land already owned. Switch the lead type to see the gate work.

Lead flow diagram Google search Meta ads Both websitesPattaya, Phuket WhatsApp, LINE,Facebook, Instagram Qualify300k dollar budgetor owns land Reply & chase2-minute reply,escalates if unspoken Nurture listno sales time Pipeline New Qualified Consult Contract Timo sees every stage Qualified leads teach Google and Meta who to find
1

A lead arrives from any channel and lands in one place.

The orchestrator

One coordinator, four specialists. The creative one makes image and video ads from your finished projects; you approve, it uploads them to Meta switched off. Slide to change how much the system may do on its own.

Orchestratorreads numbers daily Googlesearch enginebids, budgets Metaretargeting,qualified-lead goal Creativeimage + video adsfrom your projects Contentposts and pagesfrom existing video Google AdsMeta AdsTimo approves,uploads pausedWebsite, YouTube
Watch onlyProposeAct within limits

It earns permission in three steps, two weeks each. Timo can drop it back a level at any time.

Guardrails

Backup firstbefore every change, and nightly
Every action loggedwhat, why, before, after
One-tap stoprestores the last approved setup
Performance floor7 bad days = auto revert
No money accessbilling and accounts stay off limits
Watch a bad week revert itself baseline cost per qualified lead floor day 7: reverted, both alerted day 1day 8

Follow-ups to leads keep running the whole time.

Where it runs

No server to look after. Each part runs on the cheapest thing that fits how often it fires, and they all share one database.

Leads arriveWhatsApp, LINEMeta formswebsite formsemail Lead OS appVercel, Control X's accountinbox, pipeline, rules,dashboard, approvals,kill switchanswers in milliseconds Minute timerCloudflare, freewakes the app to send follow-ups One databaseSupabase, free tierleads, messages, rules,proposals, change log, backups Daily agentGitHub Actions, freereads Google, Meta andthe database, writesproposals and the briefruns long, once a day Google Ads, Meta Adsonly touched by the agent,only within the trust level Timo and Bryanphone or laptop, anywhere
AppVercel. Inbox, pipeline, approvals. Moves to Control X's account on day one.
free tier
Minute timerCloudflare. Pings the app every minute so follow-ups go out on time.
free
Daily agentGitHub Actions. Long-running, no server. Same scripts move to a server later if ever needed.
free
DatabaseSupabase. The only thing every part talks to. Approvals and the kill switch are rows in it.
free tier

Paid lines: WhatsApp messages (Meta's per-conversation fee) and the AI model's usage. Both small, both usage-based, both in Control X's name.

Open to your AI tools

One core, three doors. Whatever Claude, Codex, or the daily agent does goes through the same rules and the same log as a person.

One core leads, rules, messages, pipeline, change log every write is logged with who did it Web appTimo, Bryan, sales reps APIdaily agent, Codex, any script MCPClaude Code, Claude Desktop, Codex Keys with scopesread leads · write leads · sendmessages · edit rules · read metricsone key per tool, revoke any time No tool can everapprove a proposalflip the kill switchtouch billing or accounts
What an AI tool can do
  • List and read leads and conversations
  • Reply to a lead on their channel
  • Move a lead along the pipeline
  • Read and, if allowed, edit the qualification rules
  • Propose an ad change for Timo to approve
  • Generate an image or video ad and put it in the library for approval
What stays with Timo, in the app only
  • Approving or rejecting a proposal
  • Switching an ad on (agents upload creatives paused)
  • Pausing everything
  • Anything involving money or account structure

Connecting Claude Code is one command. Connecting Codex is a few lines of config. Both use a key Timo can revoke.

Built one piece at a time

Foundation first. Tap a phase.

Week1234567891011121314+

What changes

MeasureTodayAfter
Time to first replydaysminutes
Qualified leads spoken to within 24 hoursunknown100%
Ads shown outside Thailandyesnone, Thailand only
Instructions from Timo to the officedailynone
Cost per qualified lead, by sourcenot trackedon the dashboard weekly
Bryanbuilds, operates, prepares proposals
Timoapproves from his phone, can stop everything