Automotive Software Development Cost: Web Platforms, Not Embedded

An automotive web platform, such as a dealer portal, used-car marketplace, service booking system, fleet dashboard or parts shop, typically needs 300 to 1,600 engineering hours for a first production version worldwide. At illustrative rates of US$40 to US$75 an hour, that is about US$12,000 to US$120,000 (€10,600 to €105,700). Embedded and in-vehicle software is a different trade and is not priced here.

This guide is for automotive founders, dealer groups, fleet operators and parts retailers budgeting a browser-based product. Two plain statements first. RAITHub builds web platforms: dealer portals, used-car marketplaces, booking and service scheduling, fleet dashboards and parts e-commerce, as responsive web apps and PWAs. RAITHub does not do embedded, in-vehicle, infotainment, AUTOSAR, ISO 26262 functional-safety or firmware work. And RAITHub has not yet shipped an automotive product, so the figures below are engineering estimates drawn from comparable platforms RAITHub has built, not automotive case studies.

Which kind of automotive software are you actually pricing?

"Automotive software" covers two industries that share a word and little else. Get this wrong and every quote you collect will be for the wrong job.

	Automotive web platforms	Embedded and in-vehicle software
Examples	Dealer portals, used-car marketplaces, workshop booking, fleet dashboards, parts e-commerce	ECU software, infotainment, driver assistance, battery management, firmware
Runs on	Browsers and cloud servers	Electronic control units and in-car hardware
Typical standards	Web security, payments rules, privacy law	AUTOSAR architecture, ISO 26262 functional safety
Cost driven by	Features, integrations, data quality	Safety level, hardware, verification and certification evidence
RAITHub builds it?	Yes	No

AUTOSAR is "a global development partnership" founded in 2003 to standardise the software architecture of automotive electronic control units, with around 309 member companies in 2026 (AUTOSAR overview). ISO 26262 is the international standard titled "Road vehicles – Functional safety", covering electrical and electronic systems in road vehicles (ISO 26262 overview). Work under either is priced around safety analysis and verification evidence, not screens and APIs.

Where do you find a vendor for embedded or in-vehicle work?

Look for automotive engineering service providers and Tier 1 suppliers that already deliver to vehicle manufacturers. A generic example of the search: start from the partner list the AUTOSAR partnership publishes on its own site, shortlist firms that name the ECU domain you need (body, powertrain, infotainment, driver assistance), and ask each one for evidence of an ISO 26262 process at the safety level your part requires, previous production programmes and the toolchain they qualify. A web agency, RAITHub included, is the wrong shortlist for that job.

Many products need both: a connected-vehicle company has firmware in the car and a web dashboard for customers. Split the contract. The embedded vendor owns the device and its data interface; the web team builds the dashboard against that documented interface.

How much does automotive web software cost to build?

The hours below are illustrative assumptions for a first production version of each product type, not benchmarks and not a quote. They assume a web app with admin, customer and staff roles, automated tests and a production deployment. The money columns multiply the hours by two illustrative rates: US$40 an hour, inside the most common global band Clutch lists of roughly US$25 to US$49, and US$75, inside its US band of US$50 to US$99 (Clutch software development pricing guide, updated September 2026). Euros are converted at the European Central Bank reference rate of €1 = US$1.1355 on 30 September 2026 (ECB reference rates). RAITHub publishes no hourly rate.

Project type	Illustrative hours	At US$40/h	At US$75/h	Full span in EUR
Dealer website with inventory sync from the DMS	300–600	$12,000–$24,000	$22,500–$45,000	€10,600–€39,600
Service booking and workshop scheduling	400–800	$16,000–$32,000	$30,000–$60,000	€14,100–€52,800
Fleet dashboard (vehicles, maintenance, telematics feed, reports)	600–1,100	$24,000–$44,000	$45,000–$82,500	€21,100–€72,700
Dealer or trade portal (B2B ordering, documents, claims)	700–1,200	$28,000–$48,000	$52,500–$90,000	€24,700–€79,300
Parts e-commerce with vehicle fitment search	800–1,500	$32,000–$60,000	$60,000–$112,500	€28,200–€99,100
Used-car marketplace (multi-dealer listings, search, inquiries, lead routing)	900–1,600	$36,000–$64,000	$67,500–$120,000	€31,700–€105,700

The EUR column runs from the low end at US$40 to the high end at US$75. The spread inside each row is mostly integrations and data, covered next. For comparison, the US Bureau of Labor Statistics puts the median software developer's pay at $135,980 a year (May 2025), before benefits, hiring and management (BLS Occupational Outlook Handbook). A first version usually needs more than one person.

What makes an automotive web platform cost more?

In almost every row of the table, the features are ordinary web work. The cost sits in the connections to automotive data you do not own.

• DMS access. Stock, customer and service data live in the dealer's DMS, and access runs through the vendor's own programme and fees. Budget time for approval, not just code.
• Vehicle data. VIN decoding, valuations, parts fitment and vehicle specifications are licensed datasets. The licence is often a larger recurring cost than the build.
• Telematics. A fleet dashboard reads location and diagnostics from the telematics provider's API. Each provider's data shape differs, and a second provider can add a quarter to the integration work.
• Payments and deposits. Card handling stays with a processor. Stripe's standard US rate is 2.9% + 30¢ per successful domestic card transaction (Stripe pricing); what you build is the deposit, refund and reconciliation flow around it.
• Maps and routing. Branch finders, delivery zones and fleet maps use a maps API. Google Maps Platform lists subscription plans from $100 a month, and 10,000 free calls per SKU a month on its Essentials tier (Google Maps Platform pricing).
• Roles and rooftops. A group with several sites needs per-site, per-role permissions. That is a design decision early, and an expensive retrofit later.
• Data quality. Duplicate VINs, missing photos and prices in the wrong unit have to be caught somewhere. Validation and a circuit breaker on feeds are cheaper than the support tickets.

How do the hours split for a typical project?

Take a service booking system at around 600 hours, the middle of its row. An illustrative split:

Work	Share	Hours
Discovery, scope and design	12%	72
Booking engine: slots, bays, technicians, no double-booking	25%	150
Customer flow, reminders and deposits	18%	108
Staff and admin screens, roles	15%	90
Integration with the DMS or workshop system	12%	72
Automated tests and QA	13%	78
Deployment, monitoring and handover	5%	30

If a quote has no visible line for tests, the hours for them are either hidden or missing. Missing costs more, later.

What does a quick estimate look like in code?

If you are comparing quotes, put the arithmetic in one place so every vendor is measured the same way. A minimal TypeScript helper, written for this post:

type Estimate = { lowHours: number; highHours: number }

// usdPerEur: ECB reference rate, e.g. 1.1355 (EUR 1 = USD 1.1355)
export function costRange(e: Estimate, lowRate: number, highRate: number, usdPerEur: number) {
  if (e.lowHours > e.highHours || lowRate > highRate) throw new Error('ranges reversed')
  const usd = { low: e.lowHours * lowRate, high: e.highHours * highRate }
  const round = (n: number) => Math.round(n / 100) * 100
  return {
    usd: { low: round(usd.low), high: round(usd.high) },
    eur: { low: round(usd.low / usdPerEur), high: round(usd.high / usdPerEur) },
  }
}

// Service booking row: 400–800 hours at USD 40–75
// costRange({ lowHours: 400, highHours: 800 }, 40, 75, 1.1355)
// => usd 16,000–60,000; eur 14,100–52,800

The helper is only as good as its hours. The hours come from a written scope, which is why the scope matters more than the rate (how to write an MVP spec for an agency).

What will it cost to run each month?

Hosting for a first version is usually the smallest line. Recurring costs that do grow are licensed vehicle data, maps calls, telematics provider fees, payment processing, email and SMS reminders, and maintenance time for security updates and small changes. Budget each by volume before launch; a breakdown of typical running costs is in what a SaaS costs to run per month.

Fixed price or time and materials for an automotive platform?

Fixed price works when the scope is written and the integrations are known: which DMS, which telematics provider, which data licence. Where access to a vendor's API is still being negotiated, fix the price of everything else and treat the integration as a separate, capped piece. The trade-offs are in fixed price vs time and materials for an MVP. RAITHub works fixed-scope after a free 15-minute technical audit, or with a dedicated monthly team; see pricing and engagement models.

Why RAITHub for this

• Comparable platforms, shipped. BlockEstate, a multi-tenant listing and inquiry platform with lead routing at its core, shipped its MVP in 6 weeks (BlockEstate case study); a used-car marketplace is the same shape with vehicles instead of properties. PropDesk collects payments through Stripe and carries 1,024 automated tests (PropDesk case study). Sundor Skin runs 88 permission codes across 12 staff roles, the pattern a multi-site dealer group needs (Sundor Skin case study).
• Honest about the boundary. No automotive product shipped yet, no embedded or safety work at all. Scoping starts by confirming what your DMS, data and telematics vendors allow.
• Hours that reach you. RAITHub works from Dhaka (UTC+6). US and Canadian clients get a daily 2-hour evening overlap, Dhaka 19:00 to 21:00, which is 08:00 to 10:00 in New York and Toronto in winter. UK teams get about 3 hours (4 in summer), Central Europe 4 (5 in summer) and Tokyo 6. The working week is agreed per client, and the rest runs on written daily handoffs.
• Fixed written quotes. The client owns the IP, and an NDA is standard.

When you don't need us

• You need embedded, in-vehicle, infotainment, AUTOSAR, ISO 26262 or firmware work. Go to an automotive engineering service provider or Tier 1 supplier, as described above.
• A dealer website provider covers you. A single rooftop with standard needs should configure a template dealer site, not commission one.
• You need a native mobile app. RAITHub builds responsive web apps and PWAs, not native mobile apps.
• You want developers placed in your team by the hour. RAITHub offers fixed-scope builds and dedicated teams, not staff augmentation.

To turn the table into a number for your own scope, try the MVP cost estimator, or see the MVP development service for how a first version is scoped and delivered. Book the free 15-minute technical audit with your product type, the systems it must connect to, and your target launch date.

Last reviewed: 1 October 2026. Rates, exchange rate and vendor pricing checked on 1 October 2026.

Frequently asked questions

How much does automotive software development cost?

For web platforms such as dealer portals, used-car marketplaces, service booking, fleet dashboards and parts shops, a first production version typically needs 300 to 1,600 hours: about US$12,000 to US$120,000 (€10,600 to €105,700) at illustrative rates of US$40 to US$75 an hour. Embedded and safety-critical software is priced differently.

How much does a used-car marketplace cost to build?

An illustrative 900 to 1,600 hours for multi-dealer listings, search, inquiries and lead routing, or about US$36,000 to US$120,000 depending on rate. Licensed vehicle data and DMS feeds are the biggest variables.

Does RAITHub build embedded or in-vehicle software?

No. RAITHub builds web platforms only. It does not do embedded, in-vehicle, infotainment, AUTOSAR, ISO 26262 functional-safety or firmware work. For those, go to an automotive engineering service provider or Tier 1 supplier.

How much does a fleet management dashboard cost?

An illustrative 600 to 1,100 hours for vehicle lists, maintenance tracking, a telematics feed and reports, or about US$24,000 to US$82,500. Each additional telematics provider adds integration work.

What are the ongoing costs of an automotive web platform?

Hosting is usually small. The recurring lines that grow are licensed vehicle data, maps calls, telematics fees, payment processing, reminders by email or SMS, and maintenance time.

Has RAITHub built an automotive platform?

Not yet. The estimates here draw on comparable platforms RAITHub has shipped: BlockEstate's listings and lead routing, PropDesk's Stripe payments with 1,024 tests and Sundor Skin's 88 permission codes across 12 roles.