Ops Agent: Case Study
Two workflows.All we do is approve.
We run our content publishing and outreach operations end to end with agents. No manual drafting. No copying between tools. One tap to act, and the rest handles itself.
Note: The two 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 trigger changes. The pattern does not.
The highlighted step is the only one that requires a human. Everything else runs automatically.
By the Numbers
What two automated workflows actually deliver.
Workflow 1
Content Publishing Ops
From Instagram post to live blog article. No writing required.
A scheduled cron checks for recent Instagram posts. If a new workflow post exists, it pulls the caption, image URL, and metadata.
The agent reads the caption, maps the industry, and writes a 600 to 900 word blog post. It pulls in the featured image from Cloudinary, structures the post with an intro, workflow breakdown, and outcome section, and applies the site template. No human writes a word.
A Signal message arrives with the post title and a two-sentence excerpt. Reply "post blog" to publish or "skip blog" to discard. That is the entire review step.
The agent writes the HTML file, adds the post to the blog index, updates the RSS feed, and deploys everything to the live site via FTP. The post is live at montebelle.com/blog/ within seconds of approval.
The draft queue is updated, the pending file is removed, and the Instagram post is marked as processed so it will not be picked up again on the next run.
Before: Write the post → format HTML → update the index → upload via FTP → 45 minutes minimum.
After: Read the excerpt. Tap approve. 30 seconds.
Workflow 2
Outreach Operations
From buying signal to tracked email. No copywriting required.
When the prospecting agent identifies and enriches a lead, it passes a structured record to the outreach system: company, contact name, title, email, buying signal, and a one-line angle.
The agent drafts a short, plain email referencing the specific buying signal. Not a template with variables swapped in. A real email, written from the signal, that reads like a human wrote it, because the reasoning behind it is human-quality even if the typing is not.
The full email draft arrives in Signal. Reply "send it" to fire, "skip outreach" to discard. No login required. No switching tabs. One message, one reply.
The email goes out from a verified domain with tracking enabled. Every send is assigned a unique message ID. Delivery, opens, and clicks are tracked from the moment it leaves.
A note is written to the HubSpot contact with the send timestamp and message ID. Every morning at 9:30AM, a metrics agent polls for email events and writes opens, clicks, and bounces back to HubSpot automatically.
Before: Research the contact → write the email → log to CRM → send → manually check for opens → 30 minutes per lead.
After: Read the draft. Tap send. 30 seconds.
The Design Principle
Keep humans in the loop. Not in the work.
Both workflows share the same approval interface: a message arrives, you decide, the agent acts. You never log in to a tool. You never copy data between systems. You never draft from scratch.
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.
The approval interface, same for both workflows:
Content Ops
"New blog draft: The $11/mo Tenant Screening Stack. A real estate investor wanted to cut tenant screening from three hours to ten minutes..."
post blog skip blogOutreach Ops
"Hi John, I saw your team's work on AI-assisted denial appeals. The 60% reduction in review time stood out. We build the kind of agents that make that extension possible..."
send it skip outreachTwo decisions. Two taps. Two things live in the world.
The Point
The same pattern works for any approval workflow.
Content and outreach ops are two examples. The architecture, trigger, generate, 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.