Same tools. Different job.

A familiar Monday

Your agent has tools.
It doesn’t have the job.

You asked why checkout dropped. You got a dashboard. You forwarded it. Three weeks later, nothing moved.

Checkout Health

2.1%Conversion
12,408Segment
61%Mobile
RecommendationSimplify checkout. Add a progress bar.

Sent to engineering. Three weeks later, nothing moved.

The gap nobody named

Tools connect the model to your APIs.
Nothing connects it to you.

The protocol already knows how to call a funnel, a segment, a session. It does not know whether the person at the keyboard is hunting a mechanism, closing a ticket, or defending a launch. That missing layer is the job — compiled before the first call.

Same tools. No job.

Checkout Health

2.1%Conversion
12,408Segment
61%Mobile
RecommendationSimplify checkout. Add a progress bar.
Same tools. Job first.
Objects
Industry
Who / job
What the answer is for
Playbook

Same question

One prompt. Two kinds of output.

Why are users dropping off at checkout?

The ungrounded side finishes. The grounded side refuses to recommend until the drop has a name, a window, and evidence.

Count + rec

Checkout Health

2.1%Conversion
12,408Segment
61%Mobile
RecommendationSimplify checkout. Add a progress bar.
A brief — not a chart
WhereDrop is at payment, not “checkout.”
WindowDown vs last comparable week.
Next testPayment vs address.
EvidenceSessions queued — no rec until those are read.

The fork

Same tools. Different job.

If the model were “just having a better day,” both people would get a prettier dashboard. They don’t. They get different investigations.

No job

Dashboard + rec

Leads with 2.1% and a progress bar. Ends with “simplify checkout.” Same artifact whether Product or Support asked.

Product

Testable claim

Named step + equal window. Next measure: payment vs address. Sessions queued. No rec yet.

Support

Artifact + owner

Three sessions, same control. Replay attached. Route to engineering. The ticket can move.

Same tools. Different job.

This is a standard you can demand — context compiled before the first call — not a bigger toolbox.

For the person who forwards this

How the Health card gets made

The next screens are the practitioner layer. Same story, hood open. Skip them if the fork already landed.

Objects

It invented a segment you don’t have.

Left names Checkout_Dropoff and fills it with 12,408 people. Right uses the funnel that already exists in the org.

create_segment
Checkout_Dropoff · 12,408
ObjectsFunnel: Checkout · 5 steps
Search → PDP → Cart → Checkout → Purchase

Industry

Checkout is not a page.

In retail, purchase is a path. Treating “checkout” as one rate is how you get “simplify the page.”

SearchPDPCartCheckout · paymentPurchase

Same data. Different job.

Device is not the answer.

The pie isn’t false. It’s false as a headline. Right keeps the split — under the named step.

Headline

Mobile 61%

What explains this?
StepPayment · down vs last week

Device share sits under the step. Same 61%. Lower altitude.

The rec you forwarded

Zero results. Confident theory.

It searched an event name it guessed. Found nothing. Wrote “likely UX friction.” That sentence is how sprints disappear.

search_events · checkout_error
0 results → Likely UX friction
PlaybookUse existing funnel → equal window → path drop step → stop if the drop isn’t material or sessions aren’t in yet.

Before the first call

The pause is the product.

Left is already mid-request. Right writes the rule onto the tool. Then — and only then — the icon lights.

Firing
compute_metric
Compiling
funnel

Same registry

Identical tools. Stamped differently.

The badge is what the answer is for. The strip is what this tool may do this turn. They do not share a line.

What explains this?
Product
funnelexisting · equal window · then path step
path
Did the task complete?
Support
sessionscomplaint pattern · open · view · stop at artifact
open

What ships

Two object types. An evidence gate.

No recommendation without session evidence. Thin data is a legal ending on the right. Completeness without evidence is the left’s sin.

Health card

2.1% · 12.4k · mobile pie · add a progress bar.

Product

Payment step · vs last week · next test payment vs address · sessions queued.

Support

3 sessions, same control. Artifact. Route to eng.

The standard

Same tools. Different job.

Tools connect the model to your APIs. Nothing connects it to you.

Until the job is compiled before the first call, teams will keep buying bigger toolboxes.

See how jobs sit in the stack ↓

Optional · retail slice

Jobs live at altitudes. People travel.

Vertical is resolution — one moment up to the roll-up. “Over time” is a second axis: the same person again. It is not a coarser zoom.