Ops Agent: Case Study
Ops architecture across workflows.Cross-workflow control layer.
We run Instagram, blog, partner publishing, syndication, and outreach operations end to end with agents. Every publish and every email send requires approval in Signal. No manual drafting. One tap to act.
Note: The workflows shown are our own. The architecture, detect, draft, approve, execute, log, applies to any ops process. Your build uses your existing tools: your CMS, your email platform, your approval channel, your CRM.
The Pattern
Every ops workflow is the same five steps.
The tools change. The source signal changes. The pattern does not.
The highlighted step is the only one that requires a human. Everything else runs automatically.
By the Numbers
What the cross-workflow ops layer delivers.
Workflow 1
Workflow A: Content Publishing Ops
From Instagram scheduling to blog and partner publishing. No manual drafting required.
Instagram runs 3 daily posts on Codex: Carousel at 9:30 AM, Reel at 2:00 PM, and Story at 5:30 PM. Blog Draft Generator runs Mon, Tue, Thu, and Fri at 10:30 AM on Sonnet. Wednesday Partner Article runs at 10:00 AM on Sonnet and includes writing plus deployment. Wednesday Content Syndication runs at 11:30 AM.
Codex drafts all Instagram content artifacts. Sonnet drafts long-form blog and partner article copy, including structure and deployment-ready formatting. Syndication variants are generated for each distribution channel. No human writes drafts manually.
Every content cron sends an approval request to Signal before execution. Approve to publish or skip to discard. This human-in-the-loop gate is required before any content goes live.
After approval, the agent publishes Instagram outputs, writes and deploys blog and partner articles, runs syndication, updates indexes and feeds, and pushes the final assets live.
Each run records approval status, execution status, timestamps, and artifacts so content and publishing actions are fully traceable.
Now live: 3 Instagram posts per day, weekday blog automation, weekly partner article writing and deployment, and Wednesday syndication.
Control layer: All content crons route approval requests through Signal before publishing.
Workflow 2
Workflow B: Outreach Operations
From buying signal to tracked email. No copywriting required.
When a prospect is enriched, outreach starts a 4-touch sequence T1 to T4 using buying signals, role context, and account size metadata.
The agent drafts each touch using signal-specific context and size-aware tone. Messaging style adapts for founder-led teams, mid-market operators, or enterprise stakeholders.
Every outbound email request arrives in Signal for approval. Reply to send or skip. No email is sent without explicit human confirmation.
Approved emails send through Gmail SMTP by default. If primary delivery is unavailable, Resend is used as fallback to maintain sequence continuity.
Each touch, send decision, and delivery event is logged to outreach records and CRM context so follow-ups and reporting stay current.
Sequence: Automated T1 to T4 cadence with signal-based personalization and size-aware tone.
Control layer: One tap approval in Signal before every email send.
The Design Principle
Keep humans in the loop. Not in the work.
Ops is the control layer across workflows. Content Agent is one specialized workflow family inside this model. Outreach and other approval-driven operations use the same control pattern.
The agent handles everything that can be handled without judgment. The one step that benefits from human eyes, approving the output before it goes live or goes out, stays with the human. Everything else is mechanical and the agent is better at mechanical than you are.
This is not about removing humans from the process. It is about making the human contribution the only part that actually requires a human.
Friday at 11:30 AM, a metrics digest is generated and delivered with the same pattern: detect, draft, approve, execute, log.
The approval interface, same for both workflows:
Content Ops
"IG Reel draft ready for 2:00 PM. Blog draft and syndication package queued. Approve publish?"
approve publish skip publishOutreach Ops
"T2 draft ready for review. Account: Mid-market SaaS. Tone: concise operator. Approve send?"
send it skip outreachSame interface across every workflow. One tap to approve. One tap to skip.
The Point
The same pattern works for any approval workflow.
Instagram, blog automation, partner content, syndication, outreach, and metrics digest are current examples. The architecture, detect, draft, approve, execute, log, applies to any process where work currently moves through a human inbox before something happens.
Invoice Processing
Invoice arrives by email. Agent extracts vendor, amount, due date, and category. Routes for approval. On approval, logs to accounting system and marks for payment.
Contract Intake
New matter or contract submitted. Agent extracts parties, key dates, and obligations. Creates the record in your matter management system. Routes to the right person for review.
Employee Onboarding
New hire confirmed. Agent drafts welcome email, creates accounts in relevant systems, generates onboarding checklist, and routes manager approval for equipment and access.
Fixed price. Two to four weeks. You own the code.