Identify
We'll do the audit with you in the demo — surface the recurring work that's draining your senior team.
Solution: Back-office automation
Stop paying a person to chase failed payments.
Dunning, vendor invoice triage, expense classification, recurring email drafting — handled by agents that wait for your approval whenever it matters. The work that takes a Senior AM half their week; runs as an agent stack with HITL where you set the gates.
50+ agent templatesHITL by defaultHash-chained ledger on every action
When the recurring work that drains your back-office team is mechanical, you want agents to handle it with HITL where it matters, so that your headcount stays focused on what only humans can do.
How it works
Identify, configure, run.
Configure
Pick from the 50+ template library or compose new agents. Attach an SoD policy that mirrors your existing approval gates.
Run
With your approval gates set where you want them. Every action enters the hash-chained ledger; signed evidence pack on demand.
Capabilities
Four templates that earn their keep on day one.
Dunning agent
Detects failed payments via Stripe webhooks, sequences follow-up notifications, escalates after N days. Indefinite-retention audit row per dunning event.
Vendor invoice triage
Classifies Mercury statement transactions, flags anomalies, queues material items for SoD-policy approval. Detection thresholds are named constants in the vendor-watchdog service.
Expense triage
CFO sub-agent classifies expenses against budget categories; flags exceptions for Controller review. Material actions never bypass an approver.
Routine email drafting
Drafts under HITL — never sends without approval. Same primitive that backs the support-agent reply flow today.
Use cases
Where SMB back offices put us to work.
Dunning at failed-payment + N days
Stripe webhook fires; agent sequences notifications; HITL gate on escalation.
Vendor invoice review
Anomaly flag on amount jumps, unknown vendors, off-pattern timing.
Expense triage with policy enforcement
Classification + budget-category match + Controller approval queue.
Calendar / scheduling triage
Filters inbound asks against your priorities; drafts holds; you confirm.
Recurring vendor-renewal review
Surfaces upcoming renewals from Mercury transaction history; flags ones that need a decision.
What it replaced.
53
Outgoing COO responsibilities replaced with agents at LMNTL
8 engineer-days
Playbook → agents transition timeline
17
Production agents running LMNTL itself
Three ways to get the work off your team's plate.
| Capability | GoodHelp | DIY Python + LangGraph | Hiring a junior |
|---|---|---|---|
| Setup time | Hours-days | Months | Weeks (recruit + onboard) |
| Ongoing cost | Per-agent fee + LLM passthrough | Engineering team | $50-80k+ fully loaded |
| Audit trail | Built-in | DIY | Manual log |
| Approval gates | Built-in | DIY | Human-mediated |
Comparison reflects publicly documented capabilities as of 2026-05-25. Customer mileage may vary by configuration.
What teams ask first.
Does the dunning agent send emails without me?
No. HITL is the default. The customer-facing email cadence is delegated to Stripe-hosted dunning + Smart Retries; the agent's job is to detect, sequence, and surface — never to send without your approval on escalation steps. Configurable per agent.
Can I see what the agent did?
Yes. Hash-chained action ledger captures every action; signed evidence pack — JSON manifest plus body, KMS-rooted signing key — on demand.
What if the agent makes a mistake?
Approval gates catch high-risk actions before they happen. Lower-risk actions can be replayed or corrected via the ledger — the action is recorded and reversible at the ledger layer.
Pricing?
Per-agent + LLM passthrough. See the pricing page.
Let your senior people stay on the work that hired them.
Thirty minutes — bring one recurring task that drains your team; we’ll show you what an agent stack looks like with the approval gates set where you want them.