How an Agent Engagement Actually Works: Week by Week

People ask what it is like to work with us. The honest answer is that it looks nothing like working with a traditional consultancy. There is no weekly status call where someone reads slides at you. There is no shared Google Drive filling up with deliverables you will never open. At Armada Works, an engagement means agents running in your codebase, committing work to main, and posting briefs to a dashboard you own. The rhythm is daily. The output is diffs, not decks.

This post walks through what actually happens during an engagement, week by week. I am using the Operate tier as the primary example (that is our monthly retainer, $5,000 to $12,000/month, where we run the fleet for you), but the daily mechanics are similar across all three tiers. The difference is who holds the wheel at the end.

The First Morning

You wake up to a message from the CMO agent. Not a person. An agent that ran at 9 AM, read briefs from every other agent in the fleet, and wrote you a single synthesis: here are the three things that need your attention today.

Behind that message, four to six other agents already ran. The SEO agent audited your meta tags and flagged two pages where the title tag is truncated. The Content agent drafted 1,800 words on a topic the SEO agent briefed last week. The Outbound agent researched three prospects and wrote personalized first-touch emails sitting in your drafts folder. The Sales Lead agent updated your pipeline with qualification notes.

All of this happened before you opened your laptop. Every agent committed its work to your repo with its own bylined commit message. Every brief is a markdown file in docs/agents/state/. If you want to know why the Content agent chose that topic, you can git log the state file and trace it back to the SEO agent's keyword brief from three days ago.

This is what the daily rhythm looks like, and it stays this way for the duration of the engagement.

Week 1: Getting the Fleet Running

The first week is the noisiest. Agents are running on their initial prompts, which means their output is competent but not yet tuned to your voice, your priorities, or the specific shape of your bottleneck.

The fleet deploys into your repo on day one. You will see commits from agents you have never met. The CMO agent will introduce itself in its first founder message. The Content agent will draft a post that sounds like a reasonably smart person who read your website but has never talked to you. The SEO agent will produce an audit that is technically correct but does not yet know which pages you care about most.

This is normal. The first week is about calibration, not perfection.

Your job during week one is simple: read the CMO's daily message and leave feedback. "The content agent sounds too formal. More like a founder, less like a copywriter." Or: "I do not care about the pricing page SEO right now. Focus on the blog." That feedback goes into prompt tuning, which is where the second week gets interesting.

By the end of week one, you will have seen 5 daily briefs, 1 weekly synthesis, and somewhere between 3 and 8 pieces of tangible output: drafts, audits, prospect research, email copy. You will also have a clear sense of which agents are already useful and which need tuning.

Week 2: Prompt Tuning Kicks In

This is where the engagement starts to feel different from anything you have tried before.

Prompt tuning is not a mysterious process. Every agent in the fleet runs from a prompt file, a markdown document checked into your repo at docs/agents/. When you say "the Content agent sounds too formal," we open content-agent-prompt.md, adjust the voice section, commit the change, and the next morning the agent runs differently. The feedback loop is 24 hours, not two weeks.

By the second week, the fleet starts producing output that actually sounds like your company. The Content agent stops writing generic marketing copy and starts writing in the register you established on your website. The Outbound agent stops sending bland cold emails and starts referencing specific things about each prospect that your founder would actually notice.

This is also when the coordination layer becomes visible. You will see the CMO agent reference something the SEO agent flagged, which becomes a task in the Content agent's queue, which produces a draft that the CMO agent summarizes in your morning message. The agents do not message each other directly. They coordinate through git-committed state files. But the effect is the same: work flows through the system without you routing it.

The founder's daily time commitment during week two is about five minutes. Read the CMO message. Flag anything off. Move on.

Week 3: The System Finds Its Stride

By the third week, you stop noticing the agents. That is the goal.

The daily briefs arrive. The CMO synthesis tells you what matters. You approve the content drafts, review the outbound emails, and occasionally ask the SEO agent to dig into a specific keyword. The fleet handles the rest.

This is also when the compounding effects start showing. The SEO agent's keyword research from week one has produced content briefs. The Content agent has turned those briefs into posts. Those posts have been committed, deployed, and indexed. The Outbound agent is referencing those posts in prospect emails ("we wrote about this exact problem last week"). Each agent's output feeds the others.

The system improves itself in smaller ways too. Agents file their own observations via founder messages. "The Content agent's queue is empty. Recommend the SEO agent produce two more briefs this week." These meta-improvements compound. After a month, the fleet you are running is meaningfully better than the fleet that deployed on day one. Not because anyone rewrote the system, but because it tuned itself through hundreds of small adjustments.

Week 4 and Beyond: What Varies by Tier

What happens after the third week depends on which engagement you chose.

Operate ($5,000 to $12,000/month): the fleet keeps running. We manage the agents, tune the prompts, and handle any issues. You review the CMO message each morning and give feedback when something is off. This is the "I want the output, not the system" tier. Some founders run Operate for months. The system stays in their repo regardless. If they ever want to take over, everything is already theirs.

Transfer ($10,000 to $20,000 one-time): week three or four is the handoff. We walk you through operating the fleet yourself. You learn to read the dashboard, edit prompt files, adjust cadences, and handle the daily review without us. By the end, you are running the same system we have been running. The optional $1,500/month support tier exists for founders who want a safety net during the first few months. For a deeper look at the handoff itself, read how the transfer engagement model works.

Build ($15,000 to $60,000 per project, or $8,000+/month retainer): the agents are doing product engineering work, not just marketing operations. The timeline depends on the project scope. But the daily rhythm is the same: agents commit, briefs post, the founder reviews.

All three tiers share the same architecture. The difference is who operates it after the engagement stabilizes.

What the Founder Actually Does Each Day

I want to be specific about this because it is the question founders ask most: "How much of my time does this take?"

The honest answer is five to ten minutes a day, once the fleet is tuned. Open the dashboard (or check your email, where the CMO message also lands). Read the synthesis. It will tell you what shipped, what is in progress, and what needs your decision. Most days, the answer is "nothing needs your decision." The agents handled it.

On days where something does need attention, it is usually a content draft to approve, an outbound email to tweak, or a strategic question the CMO agent surfaced ("the SEO agent found a competitor ranking for a keyword we are not targeting. Should we add it to the content queue?"). You respond in the dashboard or leave a comment in the repo. The agents pick it up on their next run.

The 5-minute daily review is non-negotiable. We learned this running the system against our own product. Without synthesis, the system overwhelms instead of scales. The CMO agent exists because the founder's attention is the real bottleneck.

When Things Go Wrong

They do. An agent will produce a draft that misses the mark. The SEO agent will flag something that turns out to be irrelevant. The Outbound agent will write an email that sounds wrong for your brand. This is normal, especially in the first two weeks.

The fix is always the same: you flag it, we tune the prompt, and the next run is better. Because every agent's prompt is a version-controlled markdown file in your repo, you can see exactly what changed and when. If a prompt tuning makes things worse, we revert it with a single git revert. No tickets, no escalation, no waiting for a product team to ship a fix.

The system took about three months to stabilize when we first built it. New engagements benefit from those lessons. We start with 4 to 6 agents instead of 9, which reduces early-stage noise. We front-load prompt tuning in week one. And we scope the fleet to your specific bottleneck rather than trying to cover everything at once.

Regardless of tier, you own the system at the end. The agents, the prompts, the dashboard, the state files, the git history. There is no platform to log into. No API keys that stop working when the contract ends. If you cancel the Operate retainer, the fleet is still in your repo. If you complete a Transfer engagement, you are already running it. The thing we build is designed to make us unnecessary.

---

If you want to see what the daily rhythm looks like for your specific bottleneck, book a 30-minute discovery call. We will scope the fleet, walk through the engagement timeline, and tell you honestly whether this is a fit.