# Smartcar Financial Model

Cloud API platform that lets developers programmatically interact with connected vehicles across OEM brands.

- Canonical: https://finamodel.com/startups/smartcar
- Excel download: https://finamodel.com/startup-models/smartcar.xlsx
- Category: Dev Tools
- Model type: SaaS ARR / Valuation
- Funding round: Series A
- Funding: $2M
- Founded: 2020
- Geography: United States (market data cited is U.S.) [DECK, slide 6].
- Customer: B2C

## About the company

Smartcar provides a unified REST API for connected vehicles across OEM platforms including GM, Tesla, Ford, Chrysler, and BMW. Developers authenticate with an API key and car ID, then use one integration and SDKs across Python, PHP, Ruby, JavaScript, Objective-C, and Java to access vehicle capabilities.

The pure-software platform targets insurance, ride sharing, rentals, utilities, repair, and delivery businesses. Revenue is implied API-as-a-Service pricing by API call or connected vehicle, potentially with subscription tiers, but the deck does not disclose pricing, customers, ARR, usage volume, or contracts.

The model should therefore forecast customer wins, connected vehicles, calls per vehicle, unit price, minimum commitments, OEM integration coverage, infrastructure cost, expansion, churn, and gross margin. It should separate vertical adoption assumptions because fleet, insurance, and consumer vehicle use have different activation and volume profiles.

## What's included

- 5-year monthly revenue build with stage-appropriate growth assumptions
- Full P&L, headcount plan, and operating-expense schedule
- Cash-flow statement, runway, and burn-rate tracking
- Valuation via exit multiple with a DCF cross-check
- Returns analysis with MOIC and IRR
- Unit economics including CAC, LTV, payback, and cohort retention

## Product & value proposition

Smartcar provides a unified REST API (authenticated via API key + car ID) that abstracts across OEM telematics platforms (GM, Tesla, Ford, Chrysler, BMW cited). Developers write to one API and control any supported vehicle (e.g., `car.unlock()`). SDKs available in Python, PHP, Ruby, JavaScript, Obj-C, and Java. Positioning: "Pure Software Solution" - no aftermarket hardware required.

## Market

- U.S. annual car sales: 16.4M (2014) → 17M (2015) → projected 17M (2018).
- Percent of new cars that are connected: 10% (2014) → 20% (2015) → projected 80% (2018).
- Implied connected-car install base growing rapidly; by 2018 projection: ~13.6M connected cars sold annually in the U.S.
- No TAM/SAM dollar figures stated in deck.

## Revenue model

Not explicitly stated in deck. Business model is API-as-a-Service targeting developers at companies in verticals including: auto insurance, ride-sharing, car rentals, utilities, repair service, food delivery. Revenue likely follows a usage-based / API call pricing model (standard for developer API platforms) with possible tiered subscription plans - rationale: pure-software API companies at seed stage typically charge per API call or per connected vehicle/month.

## Competition / moat

- Competitive positioning chart (slide 7) maps players on two axes: Big Corp ↔ Startup (x-axis) and Aftermarket Hardware ↔ Pure Software Solution (y-axis).
- Smartcar occupies the unique upper-right quadrant: Startup + Pure Software Solution - differentiated from ~21 unnamed competitors clustered in lower quadrants (hardware-dependent or incumbent).
- Moat implied: no hardware dependency, developer-friendly API, multi-OEM abstraction layer.

## Team & funding ask / use of funds

- Sahas Katta - CEO & Co-Founder; UC Davis CS (dropout); Full Stack Developer.
- Sanketh Katta - CTO & Co-Founder; UC Berkeley ORMS + CS; Full Stack Developer.
- Two unnamed advisors listed.
- Seed ask: $2MM.
- Use of funds: Build founding team, develop core platform, procure customers.
- Milestone targets: Launch beta platform, support multiple car brands, sign 3 high-value customers → then Series A (amount TBD).

---

## Recommended financial model

- **Archetype + why:** Usage-based API / developer platform SaaS model. Revenue is driven by API calls or connected vehicles under management, not seats. This is structurally identical to Twilio/Stripe at seed: volume × price per unit. A 3-statement model is premature given pre-revenue stage; a driver-based operating forecast with runway analysis is more appropriate.

- **Forecast horizon & granularity:** Monthly for Year 1–2 (pre-revenue → beta → first paying customers); quarterly for Year 3. Total horizon: 3 years.

- **Key drivers & assumptions:**

| Driver | Value | Source |
| -- | -- | -- |
| U.S. connected cars sold annually (2018 target) | ~13.6M (17M × 80%) | - |
| Seed raise | $2MM | - |
| Beta launch timing | End of seed period | - |
| Target customers at seed close | 3 high-value enterprise customers | - |
| API pricing per connected vehicle/month | $0.50–$2.00 | developer API platforms (Twilio, HERE, OEM data brokers) price telematics access in this range |
| Average vehicles per customer at launch | 5,000–50,000 | insurance/fleet/rideshare pilots typically start in thousands of vehicles |
| Monthly burn (seed phase) | ~$80–120K | 2-person founding team + contractors + infra; $2MM / ~18–24 months runway |
| Gross margin | 70–85% | pure software API; COGS = hosting/infra + OEM data licensing if any |
| Sales cycle (enterprise) | 3–6 months | B2B API with automotive/insurance buyers |
| Customer count ramp | 3 (Y1) → 10 (Y2) → 25 (Y3) | consistent with seed milestone of 3 customers, then Series A fuels growth |

- **Scenarios (Base / Bull / Bear - which variables flex):**
  - Base: 3 customers at seed close, $1/vehicle/month, avg 10K vehicles/customer.
  - Bull: Faster OEM partnership expansion, 80% connected-car penetration arrives ahead of 2018; enterprise customers at 50K+ vehicles.
  - Bear: OEM API access is restricted or commoditized; sales cycles extend beyond 6 months; connected-car penetration lags projection.

- **Required sheets / outputs:**
  1. Assumptions - all drivers, toggleable by scenario.
  2. Revenue build - customers × vehicles under management × price per vehicle/month.
  3. OpEx / headcount plan - engineering, sales, G&A ramp post-seed.
  4. P&L - gross profit, EBITDA, net income.
  5. Cash & runway - monthly cash burn, months of runway remaining, Series A trigger.
  6. Market penetration bridge - connected-car TAM build (from slide 6 data) to show addressable vehicle count by year.

## Frequently asked questions

### Is the Smartcar financial model free?

Yes. The Smartcar model is a free Excel download with live formulas.

### Can I change the assumptions?

Yes. The workbook is editable and its live formulas recalculate when assumptions change.