Operand Studio

Readout

RUNNING NOWTHE AI INSIDE

SITUATION

Leads arrive from SMS, email, and community posts — each one needs reading, banding, and a drafted reply before a human can act fast.

BOTTLENECK

Every inbound lead read by hand, triaged by gut, replied to whenever there was time.

SYSTEM

Readout is the intelligence layer inside the product line. Wherever a lead comes from, it runs one AI pass: intent, a refined hot/warm/cold band, the details extracted, and a suggested reply drafted for a human to send. It sits beside the pipeline, never inside it — if the AI is slow or down, leads still get answered. Hard daily spend cap, every pass logged with its cost.

OUTCOME

RUNNING NOW — on the studio’s own lead line. Telemetry pending.

WHAT IT'S MADE OF

Guarded AI passOne structured AI call with a hard daily spend cap and per-call cost logging — over the cap, it skips instead of spending.Request routerReads what kind of request arrived and dispatches it to the right sub-system.Review round-tripPushes work out for a human verdict and feeds the answer back into the pipeline.Spend gateThe hard daily cost cap behind every AI pass in the line — one pricing truth, enforced server-side.Append-only historyPoint-in-time snapshots that only ever grow — the trend data the source system doesn't keep.

View the parts on GitHub →Pricing →

Every part above is a real component in the build manifests — click through to see it on the graph, or on GitHub.

See what it costs to run for you →Back to the graph →