3 worked examples

How Acme routes
in the real world

Three inbound messages. Three teams. Watch Acme classify, reason, and act — in the time it takes to read this sentence.

Try it yourself → Join the beta
1
Engineering
PR review triage
Inbound message
"PR #4421 is blocking the release — we need a reviewer ASAP. The failing tests are in the auth module and Sarah's the only one who's touched that code recently."
📨 Slack #eng-releases 09:42 AM Release window: 2 hours
1 — Classification
Acme's reasoning
Message contains PR #4421, blocking the release, failing tests, and auth module. Signals: release-blocking severity, specific PR reference, module ownership hint. Category: Engineering / Code Review — Priority: Critical.
2 — Routing decision
👤
Reviewer assigned: Sarah Chen (auth module, last commit 3 days ago, availability: online)
📢
Slack DM sent to Sarah: "PR #4421 is blocking the release — failing tests in auth module. Can you review? Release window closes in 2 hrs."
📌
Status posted to #eng-releases: "PR #4421 → routed to Sarah Chen for review. ETA: 30 min."
3 — Blocking file surfaced
Acme pulls the PR diff and identifies the specific failing file: src/auth/session-validator.ts — token expiry edge case introduced in the last commit. Context attached to Sarah's DM so she can review without context-switching.
4 — Measurable outcome
⏱ 23 min saved
✅ Release unblocked
📋 Zero Slack noise

Manual path: engineer scrolls Slack history, checks git blame, DMs the right person, re-explains context, re-posts status update. Acme does all of it before the next coffee is poured.

2
Sales
Inbound lead routing
Inbound message
"Hey, we're evaluating tools for our 40-person engineering team. We're a SaaS company and currently use Jira + Slack. Any chance someone could walk us through pricing for a team that size?"
📩 Sales inbox From: m.torres@brightloop.io Tuesday 2:15 PM
1 — Intent classification
Acme's reasoning
Signals: evaluating tools (buying intent, not just curious), 40-person eng team (mid-market segment), SaaS company, pricing ask. Confidence: high-intent inbound lead, mid-market tier. Route to AE with mid-market focus, not SDR.
2 — Company enrichment
🔍
brightloop.io — Series A SaaS, 85 employees, engineering-led. Tech stack: React, Node, AWS. No current contract. CRM: first contact.
🎯
Segment match: Mid-market engineering (30–100 seat deals). AE assigned: Jordan Rivera (owns mid-market, 3 similar logos closed in Q1).
3 — Reply drafted
✉️
Draft ready for Jordan's 1-click send:

"Hi Marcus — thanks for reaching out. For a 40-person eng team, you'd be on our Team plan. I'd love to show you how Brightloop could use it across your Slack + Jira workflow. 15 min this week? — Jordan"
📊
CRM record created. Lead source: inbound email. Stage: Contacted. Deal size estimate: $18,000 ARR (40 seats × Team tier).
4 — Measurable outcome
⏱ 31 min saved
📬 Response time: <4 hrs
💰 $18k ARR opportunity logged

Manual path: sales ops researches company, finds the right AE, forwards the thread, AE reads it, googles the company, drafts a reply from scratch. That's 31 minutes of non-selling time — on every inbound lead.

3
Finance
Vendor approval request
Inbound message
"Need sign-off on the $8,200 annual renewal for Datadog. Contract expires Friday. Last year's rate was $7,400 — they increased it. Can someone approve so I can get the PO issued in time?"
📨 Slack #finance-requests From: K. Okafor, DevOps Monday 10:08 AM · Expires Friday
1 — Classification
Acme's reasoning
$8,200 renewal, contract expires Friday, PO issued. This is a time-sensitive vendor approval, not a net-new purchase. Amount is above the $5,000 manager threshold but below the $25,000 CFO threshold. Route: Budget owner (VP Engineering) — 48hr SLA triggered.
2 — Contract retrieved
📎
Prior contract attached: Datadog_MSA_2025.pdf — $7,400 annual, signed by VP Eng. 10.8% YoY increase flagged automatically.
📊
Spend context: Datadog is in the approved vendor list. Q4 usage: 94% of plan capacity. Renewal is operationally necessary (used daily by DevOps).
3 — Approval request dispatched
✉️
Slack DM to VP Eng (Rachel Kim): "Datadog renewal approval needed — $8,200 (+10.8% from $7,400 last year). Contract expires Friday. Prior agreement + usage data attached. Approve or flag by Wednesday for PO to clear in time. [Approve ✓] [Flag for review ⚑]"
⏰
48hr SLA set. If no response by Wednesday 10am, Finance is auto-notified to escalate to CFO before the Friday deadline.
4 — Measurable outcome
⏱ 27 min saved
📋 Contract auto-attached
🔔 48hr SLA active
✅ No deadline missed

Manual path: DevOps pings Finance, Finance hunts for the prior contract, identifies the budget owner, composes a request with context, sets a calendar reminder not to let it slip. Acme does this in seconds — with a fallback if the approver goes quiet.

Want Acme routing your requests?

Join the beta. First 100 users get 3 months free — no credit card required.

Join the waitlist →