
Five real agent workflows: exact steps, model routing, and actual costs
Most articles about AI agents talk about potential. They describe an abstract future where software handles your operations, coordinates your schedule, and runs your back office.
This article is about what is running right now.
Here are five concrete workflows deployed in production environments today. For each one: the business problem it solves, the step-by-step trigger and execution logic, the specific tools it touches, how it routes between models, and what it costs per run.
1. Automated competitor and market intelligence
The problem
A small B2B team needed daily visibility into five key competitors: product launches, pricing page changes, key executive tweets, and customer complaints on Reddit and Twitter. A human analyst spent 90 minutes every morning manually opening tabs and copy-pasting notes into Slack.
Execution steps
- Trigger: Daily cron at 06:00 UTC.
- Fetch: Run headless scrapes and search queries against competitor domains, GitHub releases, and relevant X lists.
- Diff & Filter: Compare fetched snapshots against yesterday's stored markdown cache. If no material change is detected, exit immediately (zero analysis tokens burned).
- Synthesize: Pass verified changes to a mid-tier reasoning model to extract key shifts, categorize severity (1 to 5), and draft a two-paragraph executive brief.
- Deliver: Push formatted summary to a designated Telegram channel with direct source citations.
Tools touched
Web scraper, diff cache, Telegram Bot API.
Cost breakdown
- No changes detected (60% of runs): ~$0.002 (scrape and diff only)
- Changes detected and synthesized: ~$0.038 per run
- Monthly total: ~$1.10/month vs $1,500/mo human analyst time
2. Inbound lead qualification and CRM enrichment
The problem
A service company received 20 to 40 contact form submissions daily. Half were unqualified solicitations, while high-value inbound leads often waited hours for manual research before an account rep followed up.
Execution steps
- Trigger: Webhook from form submission (or email parser).
- Domain verification: Query WHOIS and company databases to verify corporate existence, head count, and sector.
- Intent scoring: Evaluate the submission text against an ideal customer profile rubric.
- Enrichment: Append discovered tech stack and LinkedIn profile URLs to the lead record in Google Sheets.
- Route:
- Unqualified: Auto-archive with a polite template.
- Qualified: Draft personalized outreach notes and ping the sales rep on Slack.
Tools touched
Google Sheets, HTTP proxy, Slack webhook, email parser.
Cost breakdown
- Average cost per lead evaluated: $0.015
- Daily cost (30 leads): $0.45/day
- Speed advantage: High-intent leads receive a personalized follow-up in under 3 minutes.
3. SEO content audit and internal linking sync
The problem
A content site with 400+ articles struggled to keep internal links updated as new pillar content was published. Dead links went unnoticed and fresh pieces lacked authority links from older, high-traffic pages.
Execution steps
- Trigger: Weekly scheduled run or on-demand post-publish hook.
- Catalog audit: Read site sitemap and build an in-memory graph of all article headings, target keywords, and outbound links.
- Opportunity detection: Identify published articles with high semantic relevance to new posts that lack internal backlinks.
- Edit proposal: Generate unified unified diffs showing exact anchor text and target URLs for 3 to 5 candidate articles.
- Verification & Commit: Validate links return HTTP 200, commit the markdown edits to the repository, and rebuild the static site.
Tools touched
Git repository, markdown parser, HTTP verification tool.
Cost breakdown
- Full audit run (400 articles): ~$0.24 (token-efficient embeddings + targeted LLM diff generation)
- Manual equivalent: 4 to 6 hours of editorial coordination.
4. Multi-channel social copy adaptation and asset prep
The problem
A media team published detailed technical blog posts weekly. Adapting one 2,500-word deep dive into an X thread, a LinkedIn carousel brief, an email newsletter teaser, and clean visual banners required hours of repetitive context-switching.
Execution steps
- Trigger: New published post detected in git or CMS.
- Key idea extraction: Parse the markdown file, extract the thesis, the 3 strongest arguments, and all concrete data tables.
- Format-specific generation:
- X thread: 5 to 7 concise tweets with no corporate fluff or em dashes.
- LinkedIn: Professional case-study angle focused on business ROI.
- Newsletter: 150-word teaser linking directly to the canonical post with tracking UTMs.
- Header banner generation: Build matching 2000x800 social cards using brand vector templates and Google Sans typography.
- Draft review: Deliver all copy and image assets to an approval inbox for one-click human sign-off.
Tools touched
Markdown reader, Pillow / graphics engine, Telegram review channel.
Cost breakdown
- Full multi-channel package: ~$0.08 per post
- Turnaround time: 45 seconds from blog publish to draft review pack ready.
5. Daily financial reconciliation and anomaly alerting
The problem
An e-commerce brand operating across Shopify, Stripe, and two merchant gateways needed daily reconciliation. Mismatches between gateway deposits and order records frequently went unnoticed until month-end accounting.
Execution steps
- Trigger: Nightly cron at 02:00 local time.
- Data extraction: Pull previous day settlement reports from Stripe API, merchant processor exports, and Shopify order logs.
- Reconciliation math: Deterministic Python script balances gross sales, processor fees, refunds, and net payouts.
- Anomaly triage: If discrepancies exceed $5.00, pass the raw transaction logs to an agent to isolate the specific transaction ID, customer email, and error code.
- Report: Deliver a clean ledger summary table to the finance lead via email and log the audit entry.
Tools touched
Payment APIs, local Python sandbox, email delivery.
Cost breakdown
- Clean reconciliation (no anomalies): $0.00 (deterministic script only)
- Anomaly investigation run: ~$0.04
- Benefit: Zero month-end surprise discrepancies and instant fraud detection.
The common pattern across all five
None of these workflows rely on a single massive prompt or an all-powerful autonomous agent wandering the web.
They all share the same structural pattern: 1. Strict boundaries: Narrow scope, explicit trigger, defined deliverable. 2. Hybrid execution: Deterministic code handles data collection, diffing, and math. The LLM handles synthesis, judgment, and formatting. 3. Model routing: Fast, inexpensive models do 80% of the volume. High-tier models are invoked only when genuine reasoning is required. 4. Human in the loop: Deliverables land in review queues or notification channels with clear diffs and source citations.
When you design agent workflows around these principles, reliability approaches 99% and costs stay in the pennies.