Z. Ahmed Z. Ahmed Dallas, TX

Ten years running growth marketing.Then I built an AI team to run it with me.

I have spent ten years in growth marketing. Today I run my own company, Your Growth System, with a team of AI agents. Eight of them work every day. They plan, write, build, check each other's work and watch for problems. Nothing goes live until I say yes. Here is what I have built.

Now: Director of Growth Marketing at Veritas Automata. Before: Chartis.io, Bailey Brand Consulting, BeMo.

8AI agents on duty every day
Nearly 300Working sessions logged
3Ways to work with YGS
10yrsGrowth foundation
ZARIFFINAL APPROVAL · SPEND · PRICEChief (orchestrator)Plans the day · hands out tasksAsks me to approveDOING THE WORKGrowthYGS marketingForgeBuilds codeSocialDrafts postsCHECKINGGuardReviews and can say stopWATCHINGSentinelSystem healthScoutNew methods and what they costCityBuilding a picture of whateach agent is doingShared MemoryThey remember what we decided · nearly 300 sessions ZARIFFINAL APPROVAL · SPEND · PRICEChief (orchestrator)Plans the day · hands out tasksAsks me to approveDOING THE WORKGrowthYGS marketingForgeBuilds codeSocialDrafts postsCHECKINGGuardReviews and can say stopWATCHINGSentinelSystem healthScoutNew methods and what they costCityBuilding a picture of whateach agent is doingShared MemoryThey remember what we decidednearly 300 sessions
The agent team Builders, checkers, and one person who says yes.

I call on original specialists too: Mark (growth strategy), Vera (blocks machine-made writing), Iris (design), Gus (claims), and a CEO twin.

8AI agents on duty every day
Nearly 300Working sessions logged
3Ways to work with YGS
10yrsGrowth foundation

A small team of agents, and one person who says yes.

Operating model

Each agent has one job. A different agent checks the work. I make the final call on what goes live, any money spent and any price.

ZARIFFINAL APPROVAL · SPEND · PRICEChief (orchestrator)Plans the day · hands out tasksAsks me to approveDOING THE WORKGrowthYGS marketingForgeBuilds codeSocialDrafts postsCHECKINGGuardReviews and can say stopWATCHINGSentinelSystem healthScoutNew methods and what they costCityBuilding a picture of whateach agent is doingShared MemoryThey remember what we decided · nearly 300 sessionsZARIFFINAL APPROVAL · SPEND · PRICEChief (orchestrator)Plans the day · hands out tasksAsks me to approveDOING THE WORKGrowthYGS marketingForgeBuilds codeSocialDrafts postsCHECKINGGuardReviews and can say stopWATCHINGSentinelSystem healthScoutNew methods and what they costCityBuilding a picture of whateach agent is doingShared MemoryThey remember what we decidednearly 300 sessions
The agent team: builders, checkers, and one person who says yes

What I have built.

System walkthroughs

Agents write the first draft. Other agents check it. Nothing ships until I say yes.

A phone receptionist

An AI voice receptionist answers the calls an owner cannot take and writes down what each caller needs. In one test call it answered, handled an interruption, booked a visit on the calendar and sent a confirmation email. That was one call. I keep testing.

Launching now. One test call so far.

Phone Catcher

With Phone Catcher on and calls forwarded to it, a missed caller is saved as a lead and the owner gets an email with a text ready to send from their own phone.

Built. Not yet tested with a live customer call.

Follow-ups that wait for a yes

Add a quote you sent. AI drafts up to three follow-up emails, for day 2, day 6 and day 12. Each one waits for the owner's OK, then goes out on its day.

Built. Follow-up sends not yet tested with a customer.

Customer Tracker

One list for every lead and customer, with a next step, a due date and dated notes. Bring a list in with a CSV file. Take it out the same way.

Live in the product.

A team that builds and checks

Eight agents build and check my software. One writes code. One reviews it and can say stop. One watches system health. One looks for new methods and what they cost. Nothing goes live until I say yes.

Live. This is how I work today.

How the work gets done

Blog Autopilot

Does the work of: a content writer, an editor and an SEO specialist

A blog helper researches what people ask, writes the post, and runs it past a checker named Vera. She blocks writing that sounds machine-made. A person approves it before it goes out.

Research Draft Review gates SEO pass Publish VETO RETURNS THE DRAFT Research Draft Review gates SEO pass Publish VETO RETURNS THE DRAFT

Short videos

Does the work of: a notebook of hooks that works

I study which hooks work in the first two seconds of a short video. I keep a library of fill-in-the-blank hooks and use one for each new script.

The detail that mattersI take apart short videos that did well and write down why. The notes go back into the library.

Watch a shortNote why it workedHook libraryfill-in-the-blankWrite the scriptNOTES KEPT FOR NEXT TIMEWatch a shortNote why it workedHook libraryfill-in-the-blankWrite the scriptNOTES KEPT FOR NEXT TIME

Market Intelligence Loop

Does the work of: a research analyst on retainer

Every Monday, research sweeps run. One checks what people are searching for and asking in five industries. One tracks what competitors did that week. A third weekly job checks what is new in AI agent methods and what it would cost. The findings go into one shared record. The strategy agents read the newest ones before they plan, so research reaches the work with no one carrying it over by hand.

YouTube demand what people ask Google Social chatter Competitor moves Weekly sweep5 industries · Mondays Shared recordstructured findings Strategy agentsread before planning NO ONE CARRIES IT BY HAND YouTube demand What people ask Social chatter Competitor moves Weekly sweep5 industries · Mondays Shared recordstructured findings Strategy agentsread before planning NO ONE CARRIES IT BY HAND

Async Agent Worker

Does the work of: the follow-through that usually waits until next week

My agents hand each other tasks on a shared list. One asks, another does the work, a third checks it. At night they stop before anything customers can see. I sign off in the morning.

Local agentsadd a job to the list Shared to-do listwaiting to done The night shiftpicks it up in the cloud RESULTS RETURN WITH STATUS TRACKING Local agentsadd a job to the list Shared to-do listwaiting to done The night shiftpicks it up in the cloud RESULTS RETURN WITH STATUS

Client Onboarding Intake

Does the work of: three discovery meetings and a shared doc graveyard

Each new client gets a branded intake. They talk, upload files and answer questions that change as they go. The agents turn it into notes the team can use. Then the client gets an approval board where they check the work before it goes out. I have done this for two client businesses.

Voice recording File upload Raw brain-dump Adaptive questionsagent asks the next one Agents structureraw into fields Plan-readydata PLAN-READY NOTES Voice recording File upload Raw brain-dump Adaptive questionsthe agent asks the next one Agents structure itraw talk into fields Plan-ready notesready for the team PLAN-READY NOTES

Living playbooks

Does the work of: the onboarding binder nobody reads

Each system I build comes with a written playbook, so someone new can take it over. Those are the playbooks I have been writing since my first marketing job.

Command Centerliving HTML manual Pitch Product Proof Library Architecture maps Who does what TAKE OVER A SYSTEM YOU DIDN'T BUILD Command Center a living manual, always current Pitch Product Proof Library Architecture maps Who does what TAKE OVER A SYSTEM YOU DIDN'T BUILD

What a week looks like on the team.

One week

Research lands on Monday. The agents read the newest findings before they start work.

MON · Market radar5 industries · MondaysCompetitor sweep · AI methods noteTUE · WED · THU · FRI · SAT · SUN AGENTS, IN BETWEENBlog helper · short videos · site · email read the latest findingsMON · Market radar5 industries · MondaysCompetitor sweepAI methods noteTUE · WED · THU · FRI · SAT · SUN AGENTS, IN BETWEENRead the newest findingsBlog · short videos · site · email
Monday research · agents reading the newest findings throughout

The loop most teams leave open, closed.

Architecture

Research feeds strategy. Strategy feeds production. I check the results and feed them back into strategy.

Scheduled agentsMarket radar · competitor sweep · MondaysShared recordstructured findingsStrategy agentsGTM · pricing · CEO twinProduction agentsblog · short videos · site · emailMeasuredanalytics · search · ad dataI check the resultsback into strategyScheduled agentsMarket radar · competitor sweep · MondaysShared recordstructured findingsStrategy agentsGTM · pricing · CEO twinProduction agentsblog · short videos · site · emailMeasuredanalytics · search · ad dataI check the resultsback into strategy
Research → storage → strategy → production → measurement → back into strategy

A bug could crash any contact page. Fixed, checked and live 24 minutes after the rollback, with my yes.

FINAL SAYFINAL SAYMeMePLANS AND ROUTESPLANS AND ROUTESChief (orchestrator)Chief (orchestrator)GuardGuardfinds andfinds andfixesfixesGrowthGrowthtries totries tobreak itbreak itLive siteLive siteCRASHPREVIOUS VERSIONLIVE00:0024minsince the rollbacksince the rollbackSOURCE: GUARD REPORT ANDDEPLOY RECORD, OCT 11Also on the teamForge, Sentinel, Social, Scout, CityFINAL SAYFINAL SAYMeMePLANS AND ROUTESPLANS AND ROUTESChief (orchestrator)Chief (orchestrator)GuardGuardfinds andfinds andfixesfixesGrowthGrowthtries totries tobreak itbreak itLive siteLive siteCRASHPREVIOUS VERSIONLIVE00:0024minsince the rollbackSOURCE: GUARD REPORT ANDDEPLOY RECORD, OCT 11Also on the team: Forge, Sentinel, Social, Scout, City
  1. Guard checks the live page. It crashes.
  2. Chief orders the rollback. Clock starts.
  3. Guard builds the fix.
  4. Growth tries to break it.
  5. Chief asks. I say "Yes fix."
  6. Guard ships it. The page turns green.
  7. Chief checks it too, then tells me.

Chief carried the work and my yes between Guard and Growth. The fixed page was live 24 minutes after the rollback.

One real job, start to finish: a crash on the contact page, rolled back, fixed and shipped, Oct 11

The checks were green, yet the live page crashed. Then the fix's tests had to prove they could fail.

First releaseGUARDGUARDFixFixphonedesktopGROWTHGROWTHTestsTests1BREAKCAUGHT2BREAKCAUGHT3BREAKCAUGHT33/3/3caughtcaught392 of 392 files passSOURCE: GROWTH TESTSCHECKSCHECKSFive checksFive checkstied to this exact versiontied to this exact versionFINAL SAYFINAL SAYMy yesMy yesChief logs it firstChief logs it firstCI GREENMERGEDTHE REAL PAGETHE REAL PAGELiveLiveCRASHLIVEphone and desktop openold pageTest rows deleted.crash found onthe live pageFirst releaseGUARDGUARDFixFixphonedesktopGROWTHGROWTHTestsTests1BREAKCAUGHT2BREAKCAUGHT3BREAKCAUGHT33/3/3caughtcaught392 of 392 files passSOURCE: GROWTH TESTSCHECKSCHECKSFive checksFive checkstied to thistied to thisexact versionexact versionFINAL SAYFINAL SAYMy yesMy yesChief logs itChief logs itfirstfirstCI GREENMERGEDTHE REAL PAGETHE REAL PAGELiveLiveCRASHLIVEphone anddesktop openold pageTest rows deleted.crash found on the live page
  1. All checks green. The live page crashes.
  2. Rolled back. The old page crashes too.
  3. Guard fixes it. Phone and desktop render.
  4. Break it 3 ways. Tests catch 3.
  5. Five checks pass on this exact version.
  6. My yes: merge once CI is green.
  7. Live. Phone and desktop open. Test rows gone.

Green checks missed the crash. Reading the real page found it, and the fix was read there too before I called it done.

On copy changes, Gus checks claims, Vera checks for machine-made writing, and Iris checks design.

The same job, seen as the gates it passed, Oct 11

My login page looked broken. The agent restarted twice mid-job, and the fix still went live.

LOGIN PAGELOGIN PAGEBROKENLIVEFORGEFORGESession oneSession onedrafts the fixdrafts the fixfixFORGEFORGESession twoSession twofixes 2 red checksfixes 2 red checksMERGED60%FORGEFORGESession threeSession threereads the note firstreads the note first62secondsto read the noteshown fastSOURCE: SESSION LOGLOGIN PAGELOGIN PAGEBROKENLIVEFORGEFORGESession oneSession onedrafts the fixdrafts the fixfixFORGEFORGESession twoSession twofixes 2 red checksfixes 2 red checksMERGED60%FORGEFORGESession threeSession threereads the note firstreads the note first62secondsto read the noteshown fastSOURCE: SESSION LOG
  1. My login page looks broken.
  2. Forge drafts the fix in 6 minutes.
  3. A new session picks up. Fixes 2 red checks.
  4. Checks pass. I say yes. It merges.
  5. Full again at 60%. Another note.
  6. 62 seconds later it reads the note.
  7. Live. The input box is visible.

The note carries the job across each restart. The fix went live within the hour of my screenshot.

The note is a file. The job's history lives on a shared task list.

One real job: an unstyled login page, from my screenshot to the live fix, across two restarts, Oct 11

A timer found my new video, scheduled it on two apps, and a second timer confirmed both went live.

1of 801:30 am04:30 am07:30 am010:30 am11:30 pm04:30 pm07:30 pm010:30 pm6:20 pmApp 1 clip2 pmscheduledliveApp 2 clip3 pmscheduledlivesame filetask recordCOMINGMonday radar and hooks sweep.First run Monday.
  1. Every 3 hours a timer looks. Nothing new.
  2. 1:30 pm: a new video is public.
  3. It tests first, then schedules.
  4. Two apps scheduled. Same file, checked.
  5. 4:30 pm: nothing new, so it stops.
  6. 6:20 pm: a second timer finds both live.
  7. 10:30 pm: one note goes on the record.

Most checks find nothing and stop on purpose. The one that finds something does the work, and a second timer proves it.

One new video through a day of timers, Oct 11, Central time · Source: timer log

I asked what ads work. Agents studied 104, a critic caught five problems, and a voiced video is ready.

MEMEI askI askAN AGENTAN AGENTStudyStudyA CRITICA CRITICCriticCriticFINAL SAYFINAL SAYMy pickMy pickBUILDSBUILDSBuildBuildVOICEDVOICEDVoicedVoicedpublic ads,public ads,logged out,logged out,at human paceat human pace104104ads inSOURCE:AD RESEARCHMark made five video ideas.Mark made five video ideas.The CEO twin read it cold.The CEO twin read it cold.the free-check videothe free-check videoVeraFIXIrisFIXGusFIXREADY AND HELD1video out
  1. I ask what ads work.
  2. An agent studies 104 public ads.
  3. A critic recounts. Five problems.
  4. I pick the free-check video.
  5. Vera, Iris and Gus ask for fixes. Done.
  6. A voiced version waits in my phone preview.
  7. Nothing posts until I say.

A different agent checked the work before it reached me. I got one clear pick, and the video waits until I say go.

One real job: ads research to a voiced video, ready and held, Oct 11

Forge, my builder, carried most of the load. A lighter model got three real jobs to try. One passed.

main modellighter modelForgeForgebuilderbuildertest it8 OR BETTER769counts re-checkedaudit7plan6inventory1of 3SOURCE: CANARY REPORTRULEbounded reads onlyClaudestrategy, long documents,final calls.Codexbuilds and checks. Its output is runbefore it is trusted. A lighter modelnow takes bounded reads.Hermescheap reading and research.A daily spend alarm watches it.JEV, on trialquick yes or no checks, recordedand compared, not trusted yet.
  1. Forge carries most of the load.
  2. I say yes to a test.
  3. The scoring sheet comes first.
  4. Three real jobs run on the lighter model.
  5. Two score under 8. They go back.
  6. One passes: 9 out of 10.
  7. Rule: only bounded reads move.

Only the kind of job that passed moved to the lighter model. The whole test took eleven minutes.

One real test: a lighter model on three builder jobs, a partial pass, Oct 11

See it working.

Proof

Everything I have built is written up in the Letters, including the parts that broke.

Ten years of classical growth. Then I taught it to run without me in the room.

The path here

Before the agents, the same job with people: multi-client budgets across Google, Meta, LinkedIn and programmatic, KPI frameworks, CRM architecture, and being the escalation point between clients and leadership. The systems work because that discipline is real.

2025 · Present

Founder, YGS & the Agent OS

An AI growth system for service businesses: a plan to follow, a monthly Autopilot with a customer list, follow-ups and phone tools, and a done-for-you build. The Agent OS is the white-label version for agencies. Built with agents as the engineering team, checked by other agents, approved by me.

2025 · Present

Director-level growth work

I moved from associate-level work into director-level growth work, with a focus on growth strategy, demand generation, CRM architecture, and AI-assisted research and reporting.

2023 · 2025

Sr. Consultant to Digital Marketing Lead, Chartis.io

Multi-client digital strategy across Google, Meta, LinkedIn and programmatic. Client spend management, KPI frameworks, and the escalation point between clients and leadership.

2021 · 2023

Digital Marketing Manager, Bailey Brand Consulting

Brand-side digital: paid budgets and A/B roadmaps across eight platforms for the firm and its clients.

2020 · 2021

Digital Marketing Associate, BeMo

PPC, funnel testing, attribution (Hyros), demand-gen automation, and the first SOPs I ever wrote. I've been turning workflows into systems since my first marketing job. Now AI agents do the first draft and a person approves it.

Tools change. Architecture is the skill.

Stack
AI / Agentic
  • Claude Code and Codex: agents that plan, build and review
  • A shared task list, approvals and memory across 8 agents
  • Different models for leading, building and checking
  • OpenAI / ChatGPT, and OpenAI voice for the phone receptionist
  • Higgsfield · ElevenLabs · Remotion
Growth
  • Strategy: demand gen, ABM, pricing
  • SEO / AEO / GEO
  • Paid: Google, Meta, LinkedIn, programmatic
  • CRO & funnel architecture
  • Lifecycle & email
Data / Infra
  • Supabase (Postgres) · Vercel · Next.js
  • GitHub Actions CI
  • HubSpot · GA4 · Search Console
  • Supermetrics · VidIQ · Ubersuggest
  • Stripe · Square · Twilio · Calendly · Resend

I have already built and run this system end to end.

Open to Director+ roles leading AI-driven growth, marketing or GTM systems, and to walking your team through a live demo of everything on this page. Ten minutes, real systems, no slides.