Prepared for Luke Miller — Co-founder & CEO
SLNG
Voice-AI infra is one of the cleanest dev-first motions there is — nobody buys an execution layer off a sales call; they read the docs, grab a key, and watch the latency drop or they don't.
Your whole pitch is built to be proven in a terminal — plug SLNG in, watch cost and latency fall at $0.0033 a minute. The catch at 16 people is that the most telling signals live in that self-serve path and go unread, even though every one of them is instrumentable today.
The signals you're sitting on
◆ SIGNAL 01
Docs read at docs.slng.ai, then an API key pulled
Reads as
A developer past curiosity and into hands-on evaluation. Real eval, not yet hot.
Leaks today
Logged as docs traffic and a key issued, never joined; no owner, no trigger.
Wire this
Wire docs-read-then-key-pull as 'evaluation started' and open a light, helpful nurture — sample agents, integration guides. No sales yet.
◆ SIGNAL 02
First voice agent running on real minutes after the key was pulled
Reads as
They've proven it works in their stack. This is the buying moment.
Leaks today
Indistinguishable from any other usage in your billing metrics; nobody's alerted.
Wire this
Fire a real-time alert to a human the second a first agent goes live on real minutes, and reach out while the trial's still warm.
◆ SIGNAL 03
Minutes scaling up, or a second teammate appears in the workspace
Reads as
Moving from a test agent toward production. Expansion intent.
Leaks today
Treated as usage growth on a graph; no expansion signal wired to a person.
Wire this
Flag a sharp minutes ramp or a second seat as an account-expansion trigger and route it to a tailored scale-up touch.
◆ If you wire one thing
Pick the two developer moments that actually mean 'this one's real' — most likely key-pull-after-docs and first agent live — and get a human there before the trial cools, not into a weekly GitHub-stars digest.