-
The problem
Modal customers can go from zero to hundreds or thousands of GPUs, so workloads are spiky. That makes revenue unpredictable and leaves expansion, contraction and churn loosely defined. Revenue forecasting, spend propensity and churn prediction are hard when you can't easily define "closed won" or "closed lost."
-
What they built
With Justin Dignelli, Chris treated the problem as forecasting and anomaly detection. He built an ontology of Modal's business, product and space, applied it to Modal's data, and used it to build a model that tracks and forecasts each customer's usage. When a customer deviates from the forecast, an alert goes out so someone can engage the customer and find out what's going on.
-
So what
In a usage business, the warning sign is a change in usage, not a deal stage. This flags customers who drift from their forecast and sends someone to talk to them.
Under the hood
For GTM engineers
The ontology is created automatically rather than by hand-tagging, and can be applied across meeting transcripts, notes, Slack, email and support tickets, with Jev doing the batch classification. The ontology is used to create features in a multivariate time series model that forecasts usage; deviations from the forecast trigger an alert. Built with TypeSafe AI.
More examples
Other systems GTM engineers have built, or see all of them.
-
Air Rebuilt outbound so no account quietly falls through the cracks; meetings booked went from 1% to over 6% of assigned accounts
Tom Bonagura · GTM Engineer -
Vercel Turned what customers say on calls, in support cases and in Slack into a weekly report that tells each product team what the field is asking for
Brandon Galang · GTM Engineer -
WorkOS Gave the whole go-to-market team one shared record of every account and contact, which anyone can ask questions of or act on without help
Jack Perales · GTM Engineer
Hiring someone who can build like Chris?
We search for GTM engineers who have shipped systems like this one, and Joe speaks to every candidate before you do.