OPERAND STUDIO
← The full graph

Radar

RUNNING NOWPOWERED BY READOUT
SITUATION

A studio selling automation needs to know, immediately, when someone in a developer or business community describes a problem it solves.

BOTTLENECK

Scrolling forums between real work — days late to threads that mattered, or not watching at all.

SYSTEM

A watcher polls the communities around the clock, deduplicates every new post, and hands each one to a guarded AI pass that scores intent. Hot leads ping the owner's phone in minutes with a brief and a suggested angle; everything else lands in one daily digest. Detection is automated; every reply is written by a human.

OUTCOME

TELEMETRY PENDING — posts scanned · leads surfaced · response time land here once published.

WHAT IT'S MADE OF
Source watcherWatches configured firehoses and hands over only the new, deduplicated items — adding a source is data, not code.SchedulerThe clock — fires on cadence, remembers its place, and never loses a due job.Read-only JSON APIA safe read window onto live data — fetch, shape, respond; never writes.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.Notification fan-outSigned delivery of alerts to phone or inbox — one message, any channel.Email composerValidates, composes, and sends an email — and logs whether it actually went.Spend gateThe hard daily cost cap behind every AI pass in the line — one pricing truth, enforced server-side.Write-only captureThe public can submit but can never read back — and personal fields are locked at the column level.Append-only historyPoint-in-time snapshots that only ever grow — the trend data the source system doesn't keep.

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 →