← All posts

What “Agentic” Actually Delivers

July 2026 · 7 min read

Most AI in go-to-market produces a copilot — something that drafts an email a human still has to send. We built the other thing: a system that notices a merchant's deal has gone offline, contacts them, gets their consent, and makes the fix itself.

$2.3M

recovered in Q2

$225,725

with no human in the loop

285

deals restored autonomously

The quiet failure

In a marketplace, the loud failures get fixed — a checkout bug pages someone within minutes. The expensive failures are quiet.

A merchant sells out their monthly voucher cap on a Tuesday and their deal stops being purchasable. Nothing breaks. The merchant doesn't notice, because nothing changed on their end. The rep doesn't notice, because they own hundreds of accounts. The deal sits offline, and every day is revenue neither side ever sees. The traditional fix — more account managers — scales with headcount, which means it doesn't scale.

How it works

Detection is the easy half and has existed for twenty years. What matters is whether the loop closes without a person in it:

Trigger

A merchant's deal sells out and goes offline

Nothing breaks. No alarm fires. Nobody notices.

1

Priced on arrival

Margin per day × expected days offline. This number decides whether contact is worth it — and later becomes the attribution base.

2

Gated

Account live? Merchant contactable? Already alerted this week? Auto-replenish already handling it?

3

Contacted, two ways

An email showing what they lose per day, and a two-way SMS that accepts a plain “YES”.

Merchant replies

Consent → backend action

The reply is parsed, the capacity change is written through the deal API, the deal goes live.

under 60 seconds · no human

Silence at T+4h

Escalate to a rep

A call cadence opens with the full context attached. The person is the fallback, not the default.

hours to days · human

Outcome

The deal is purchasable again — and the recovery is measured

The whole design question is the left-hand box. Everything above it is a notification system.

The agentic channels don't just work — they hold their own against the human one, because the merchant never has to leave the message. No login, no form, no call to schedule. The whole transaction is one word.

Recovery rate by channel
SMS
78%
autonomous
Email
61%
autonomous
Rep task
82%
human

What it produced

One quarter of recovered merchant value, split by whether a human was involved:

Rep-driven — $2,074,471
Autonomous — $225,725 (9.8%). 285 deals brought back online with no human anywhere in the chain.
Q2 2026 total: $2,300,196. Verified recoveries plus the kept-alive tail, net of each deal's own historic run rate.
Q2 2026VerifiedKept-aliveTotal
Autonomous$61,414$164,311$225,725
Rep-driven$658,898$1,415,573$2,074,471
Total$720,312$1,579,884$2,300,196

The green sliver is the one I care about, precisely because it's the smallest number on the page. The gray bar grows with headcount. The green one doesn't — and three months ago it was zero. That slope, not the absolute value, is the whole thesis.

The 98% haircut

Any alerting system can produce an impressive number: fire an alert, observe that the deal later made money, claim the money. Most internal AI programs report their wins this way, and most of those numbers are fiction.

The honest question is counterfactual — how much would have happened anyway? So we calibrated every alert type against a control group of alerts that were generated but never actioned. Our biggest-looking result did not survive it:

“Deal ending soon” alerts — claimed vs. defensible
Gross value
$2.02M
Real lift
$39K

The control group showed 95.7% of those deals kept selling with or without us. Real lift: 1.9%. So we wrote our own headline down by 98%.

Not a fun chart to present. Also the only reason the rest survived scrutiny — at the investment review nobody litigated whether the value was real, because we'd already argued against ourselves harder than any reviewer would. Every dollar above reconciles to a specific deal, on a specific date, with a specific touchpoint. Without that you don't have a result. You have a slide.

Two people

All of it is built and run by two: one engineer and me. Not as a flex — it's the product claim. If it took thirty people to build a system whose purpose is removing manual work, the argument would refute itself.

It works because one person holds the entire chain: signal definition, data modelling, message copy, the commercial case, the attribution. Most of the cost in enterprise projects isn't the work — it's the handoffs between six people who each own one slice of it. AI absorbs the analysis: the pipelines, the backfills, the warehouse queries, the reporting. What stays human is choosing which alert types to build, and deciding when to tell a stakeholder the number is worse than they hoped.

That capacity is what lets a two-person team run a catalogue this wide — and keep extending it:

11 live
16 planned
12 future
39 defined alert types across 7 lifecycle categories. Restock and lifecycle shipped first because they have exactly one correct action — which is what makes them automatable at all.

The scarce resource was never engineering capacity. It's someone who understands the commercial mechanics well enough to know which fix is correct, and who can ship it without translating through three teams first.

The test for any agentic claim is simple: at the end of the process, did a human have to do something? If yes, you built a very good notification system. That's worth real money — two thirds of our own number comes from exactly that. But it isn't new, and it scales the way the org chart does.

The part that scales differently is small today: $225,725 out of $2.3M. Three months ago it was zero. That's the line worth watching — in our program, and in anyone else's.