Overview
You build ROI models and business cases for Samsara's IoT platform in government deals. You work with AEs selling to public sector organizations (transit agencies, municipal fleets, state DOTs), creating financial justifications that survive budget committees and procurement processes. Most of your time goes to analyzing customer data, building Excel models, and presenting cost-benefit analyses to finance teams and elected officials.
Role Snapshot
| Aspect | Details |
|---|---|
| Role Type | Pre-sales Value Engineering / Consulting |
| Sales Motion | Outbound-heavy enterprise, long procurement cycles |
| Deal Complexity | Strategic public sector |
| Sales Cycle | 9-18 months (government procurement) |
| Deal Size | $200K-$2M+ ACV |
| Quota (est.) | Not quota-carrying, but measured on deal influence/win rate |
Company Context
Stage: Public (NYSE: IOT, ~$1B revenue)
Size: 5,300+ employees
Growth: Mature growth phase, expanding into public sector vertical
Market Position: Leader in IoT fleet management, competing against Geotab, Verizon Connect, and legacy telematics providers in government space
GTM Reality
Pipeline Sources:
- 30% Inbound - RFPs, government procurement portals, contract vehicles (GSA Schedule)
- 60% Outbound - AE-sourced relationships with fleet managers, IT directors at agencies
- 10% Referrals - Existing government customers, reseller partners
SDR/AE Structure: Enterprise AEs own accounts, you support deals in technical/financial evaluation stage
SE Support: You ARE the specialized support - work alongside standard SEs who handle technical demos
Competitive Landscape
Main Competitors: Geotab (dominant in government), Verizon Connect, GPS Insight, Teletrac Navman
How They Differentiate: AI-powered cameras, unified platform vs point solutions, modern UI, cloud-native architecture
Common Objections: "We already have GPS tracking," budget constraints, existing vendor relationships, data privacy concerns, union pushback on driver monitoring
Win Themes: Total cost of ownership vs legacy systems, safety improvements (accident reduction ROI), fuel/maintenance savings, grant funding alignment (federal infrastructure money)
What You'll Actually Do
Time Breakdown
Value Analysis (40%) | Deal Support (35%) | Internal (25%)
Key Activities
- Building ROI Models: Gather customer baseline data (current fleet costs, accident rates, fuel consumption), build 3-5 year TCO models showing savings from Samsara. You're in Excel/Google Sheets daily, pulling apart their budget line items.
- Executive Presentations: Present business cases to city councils, transit board meetings, procurement committees. You're explaining why spending $500K on cameras will save $2M in liability costs. Expect questions from elected officials who don't understand the technology.
- Discovery Sessions: Interview fleet managers, finance directors, risk managers to quantify current pain points. How many accidents per year? What do they pay in insurance premiums? What's their fuel budget? Most don't have clean data.
- Proposal Support: Write the "business value" sections of RFP responses. Government buyers need detailed cost justifications. You're translating technical features into budget-defensible outcomes.
- Grant Application Help: Some deals involve federal/state grant funding (infrastructure bills, safety grants). You help customers articulate ROI in grant language to unlock funding.
The Honest Reality
What's Hard
- Public sector moves slowly. Deals you start in Q1 might close in Q4 of the next year. Budget cycles, procurement rules, committee approvals - everything takes 2-3x longer than commercial deals.
- Data is messy. Government fleet managers often don't have clean baseline metrics. You're estimating accident costs from incomplete insurance records and building models on assumptions.
- Stakeholder complexity. You're not just convincing one buyer - it's fleet ops, IT, finance, legal, risk management, union reps, and elected officials. Everyone has veto power.
- Your work gets picked apart. Procurement teams scrutinize every assumption in your ROI model. Finance directors challenge your savings calculations. You need to defend your numbers in public meetings.
- Not all deals close. After months of work, budget gets cut or political priorities shift. Your ROI model was perfect, but the city council voted no anyway.
What Success Looks Like
- Your business cases survive procurement review and get approved by finance committees
- AEs tell you "we wouldn't have won without your ROI model"
- Customers use your analysis to secure budget or grant funding
- Deal win rates improve in opportunities where you're engaged early
Who You're Selling To
Primary Buyers:
- Fleet managers (operations stakeholders - they want the solution)
- Finance directors / budget officers (gatekeepers - they approve the spend)
- IT directors (technical evaluation)
- Risk managers / safety directors (care about liability reduction)
- Elected officials / executive leadership (final approval, political considerations)
What They Care About:
- Budget justification: Can you prove ROI that survives audit scrutiny?
- Grant eligibility: Does this align with federal infrastructure or safety funding?
- Risk reduction: Quantified impact on accidents, liability claims, insurance costs
- Taxpayer defensibility: Can they explain this spend to constituents?
- Procurement compliance: Does your pricing fit contract vehicles (GSA Schedule, NASPO, state contracts)?
Requirements
- 5+ years in consulting, value engineering, finance, or business operations roles
- Excel/financial modeling skills - you build TCO models from scratch
- Experience with public sector procurement (understanding RFPs, grant funding, budget cycles)
- Ability to translate technical features into financial outcomes
- Comfortable presenting to executive audiences and government officials
- Willingness to travel to customer sites for discovery and presentations
- Understanding of fleet operations, safety metrics, or government budgeting is a plus