Overview
You manage existing Roboflow customers after AEs close the initial deal. Your job is to ensure they're getting value (so they renew), identify expansion opportunities (new teams, use cases, higher tiers), and manage usage-based pricing conversations. Most accounts are $10-75K ACV, with a mix of startups, mid-market companies, and occasional enterprise teams.
Role Snapshot
| Aspect | Details |
|---|---|
| Role Type | Account Management (retention + expansion) |
| Sales Motion | Land-and-expand, usage-based upsells |
| Deal Complexity | Consultative (technical value realization) |
| Sales Cycle | Ongoing relationship, 30-90 day expansion cycles |
| Deal Size | $10-75K initial, expanding to $100K+ |
| Quota (est.) | 95%+ net retention, $300-400K expansion/year |
Company Context
Stage: Series B ($63.6M raised, GV-backed)
Size: 107 employees
Growth: Scaling quickly - "best year yet" in 2025, expanding team and NYC office
Market Position: Category leader with 4.7 G2 rating. Customers are generally happy with product, but price sensitivity exists (Reddit discussions about cost vs alternatives).
GTM Reality
Customer Base:
- Mix of startups (tight budgets, 1-2 CV projects), mid-market (multiple teams potentially), enterprise (one team using, others could adopt)
- Technical users (ML engineers) who are hands-on with product
- Usage-based pricing means you're tracking image volume, API calls, deployment metrics
Support Model: Customer success owns relationships, support team handles technical tickets, SEs help with complex implementation questions
Renewal Process: Annual contracts mostly, some quarterly for smaller accounts. Renewals require ROI proof to engineering leadership.
Competitive Landscape
Expansion Competitors:
- Inertia ("We'll just stick with current scope")
- Budget constraints (CV projects get deprioritized)
- Switching to cheaper alternatives (Clarifai mentioned in Reddit as $$ concern)
- Building in-house for specific use cases
Retention Risks: Price sensitivity, project cancellations, switching to cloud platforms they already pay for, technical issues during deployment
Expansion Triggers: New CV use cases, more teams doing CV work, scaling from dev/test to production, adding edge deployment
What You'll Actually Do
Time Breakdown
Customer Meetings (40%) | Expansion Pipeline (30%) | Renewals (20%) | Admin (10%)
Key Activities
- Quarterly Business Reviews: Check-ins with 2-3 customers per week to review usage, ROI, roadmap fit. You're asking about other CV projects, who else is doing CV work, what's changing in their priorities.
- Usage Monitoring: Track who's approaching tier limits, identify accounts growing quickly (upsell opportunity) or declining (churn risk). You're proactive about "Hey, you're at 80% of your image limit - let's talk about your next tier."
- Expansion Hunting: Multi-threading into other teams. Customer started with manufacturing QA, but they also have retail analytics and security teams doing CV. You're trying to get intros and run expansion demos.
- Renewal Prep: 90 days before renewal, you're building business case with customer champion. Usage data, time saved, models deployed. You need to justify spend to their leadership.
- Technical Escalations: When customers hit issues (deployment failures, API performance, integration bugs), you're coordinating with support/engineering and keeping customer updated.
The Honest Reality
What's Hard
- Usage-based pricing creates friction - customers hit limits and need to upgrade or optimize usage. Some reduce usage to avoid paying more.
- CV projects get cancelled - if customer's product feature gets cut, they churn immediately. You have little control over their business decisions.
- Multi-threading is slow - getting intros to other teams takes months. Your champion doesn't always have influence across the org.
- Renewal risk with budget cuts - CV tooling is often discretionary spend. When budgets tighten, they'll try to build in-house or switch to cheaper alternatives.
- Technical users go direct to support - they don't want account manager check-ins, they want to use the product. You're adding value through expansion conversations, but they see it as sales.
- Price sensitivity - customers compare to open source alternatives or cloud platform credits. Proving ROI requires data they don't always track.
What Success Looks Like
- 95%+ gross retention (lose very few customers)
- 120-130%+ net retention (expansion exceeds churn)
- Upsell 30-40% of accounts in a given year
- Identify expansion opportunities within 2-3 months of initial deployment
Who You're Selling To
Primary Contacts:
- ML Engineers / CV Engineers (day-to-day users and champions)
- Engineering Managers (expansion approvals, renewal sign-off for smaller accounts)
- Directors/VPs of Engineering (renewal approvals for larger accounts, multi-team expansion)
What They Care About:
- Are they getting ROI vs building tools themselves?
- Is the platform keeping up with their scaling needs (more models, more deployments)?
- Cost predictability - usage-based pricing creates uncertainty
- Support responsiveness when they hit production issues
- Roadmap - are upcoming features worth staying vs switching?
Requirements
- 2-4 years in customer success or account management for technical products
- Experience with usage-based pricing models and expansion sales
- Ability to speak credibly with ML engineers about their workflows (you don't need to code)
- Track record with net retention and upsell targets
- Comfortable managing 30-50 accounts (mix of high-touch and tech-touch)
- Data-driven approach to identifying expansion opportunities and churn risk