Modal's first account managers start with "no playbook, no territory map", measured on retention and expansion of consumption revenue. In a usage-priced business, the signals that matter are in the billing data long before a customer says anything: spend climbing toward a concurrency limit, a new workload type appearing, a sudden drop.
First action
Define the four signals with RevOps and pull last week's list by hand for one account manager.
How to measure it
Accounts contacted within a week of a signal
- Now
- –
- Target
- 90%
- By
- 1 quarter
Steps
Define signals
Spend change, near limits, new product, new GPU type; agree thresholds.
Revenue Operations 2 days
Build the query
A weekly job over usage data, joined to account owners.
GTM Engineer, Data Platform 1 week
Write reasons
One suggested message per signal ("you started using Sandboxes; here is how others scale them").
Account Manager 2 days
Deliver weekly
Into Salesforce or Slack each Monday.
GTM Engineer, Data Platform 1 day
Log outcomes
Account managers note what each conversation led to.
Account Manager Ongoing
Tune
Drop signals that never lead anywhere; add new ones monthly.
Revenue Operations Monthly
Why it works
Each Monday, give every account manager a list built from usage data: accounts whose spend grew or fell more than 30% week on week, accounts near their container or GPU concurrency limits, accounts that started a new product (Sandboxes, training, inference) for the first time, and accounts whose top workload moved to a different GPU type. Each line comes with a suggested reason to reach out.
Expansion in usage-based infrastructure follows workloads; catching a new workload or a limit early is the difference between growing with the customer and the customer splitting work to another cloud. The GTM engineering team already builds data systems and account-research to do this.
Ready to use
ChecklistSignals and suggested outreach
1. Spend up 30%+ week on week: offer an architecture review and check concurrency limits. 2. Within 20% of container or GPU concurrency limit: offer a limit increase before it bites. 3. First use of a new product (Sandboxes, training, inference): share the matching guide and a customer example. 4. Spend down 30%+: ask what changed; offer help with performance or a migration blocker. 5. Top workload moved to a new GPU type: share the pricing and performance notes for that GPU.
Risks and how to handle them
Too many alerts
Start with the top 50 accounts and two signals, then widen.
Customers dislike being watched
Lead with help (limits, cost, architecture), never with "we saw your usage drop".
Evidence
- HiringAccount Manager (posted September 16, 2026): "We're hiring the first Account Managers at Modal... This function does not exist yet. There is no playbook, no territory map, no established motion." A revenue target "measured on retention and expansion"; customers are "engineers running GPU workloads, inference, and batch jobs in production"; experience at companies "consumption in nature" wanted.Source
- HiringGTM Engineer, Data Platform (posted October 13, 2026): build "an org map and people graph connecting companies, labs, teams, and individuals to identify researchers, engineers, and early-stage startups, including people beyond our existing users and CRM"; the team already builds "agents for account research". A Revenue Operations hire owns lead routing, attribution and territories.Source
- Your websiteSeries D post (October 14, 2026): usage has tripled since the Series C five months earlier; Sandboxes is "a $300M run rate product just on its own", with close to 3 billion sandboxes started and scaling to a million concurrent; the capacity pool spans "20+ clouds"; recent launches include multi-node training, Modal servers, Endpoint Candidates and virtual machines; Modal is "moving up the stack" into RL and post-training. Customers named include DoorDash, Cognition, Ramp, Linear, Hebbia, Runway, Physical Intelligence and Chai Discovery.Source
- Your websitePricing is per second (for example Nvidia B300 at $0.001972/s and H100 at $0.001097/s); Starter is $0 plus compute with $30 a month of free credits; Team is $250 a month plus compute with $100 of credits; Enterprise on request.Source