Prepared for Lin Qiao — CEO & Cofounder
Fireworks AI
Inference platforms are a rare category where the product tells you who's about to grow before any sales motion does — someone signs up, runs a model or two, then starts a fine-tune, and that's not a trial, that's a team committing.
At your stage signups aren't the problem; routing them is. The free-to-serious moment lives inside the platform — first deployed model, first fine-tune, spend or rate crossing a line — and catching a fraction of those means real expansion revenue stops walking past warm.
The signals you're sitting on
◆ SIGNAL 01
New account runs its first model with the single-line-of-code call
Reads as
A developer kicking the tires on inference — early eval, real but not yet a commitment.
Leaks today
Logged as usage in the platform, not as intent; no owner, no trigger, indistinguishable from any other API call.
Wire this
Tag the first deployed-model call as 'evaluation started' and open a light, helpful nurture — use-case examples for the funnel they entered (Agentic, Code, RAG). No sales yet.
◆ SIGNAL 02
Same account starts its first fine-tune or training job
Reads as
A team committing to the platform, not just testing it — the cleanest expansion trigger an inference platform gets.
Leaks today
Sits in usage metrics next to every other job; nothing distinguishes 'a team is building on us now' from routine inference.
Wire this
Wire a real-time alert the moment a first fine-tune kicks off, and route it to a human while the intent is warm — the free-to-serious moment, caught live.
◆ SIGNAL 03
Spend or request rate crosses a defined threshold, or a second seat appears on the account
Reads as
Production load arriving — an account scaling past evaluation into real usage. Expansion revenue forming in-product.
Leaks today
Surfaces in a billing or usage dashboard after the fact, long after the warm moment passed and unconnected to the enterprise pull-through (Cursor, Vercel, Notion-class accounts).
Wire this
Flag spend/rate thresholds and multi-seat as expansion triggers and route them to a tailored, account-aware touch before the self-serve-to-expansion handoff goes cold.
◆ If you wire one thing
Pick the two in-product moments that actually mean 'a team just committed' — first fine-tune and a spend/rate threshold — and make sure they reach a human in minutes, not a usage report next week.