How Much Does a Car Dealership Website Cost?

A car dealership website can cost anywhere from a focused marketing site to a substantial inventory and lead-management system. The difference is not the number of pages alone. It is the number of systems, departments, vehicle states, integrations, approvals, and customer actions the website must handle reliably.

The useful way to estimate a dealership website is by capability. Start with a written scope for the smallest release, count the integrations and operational rules, and separate one-time implementation from vendor subscriptions and ongoing merchandising.

Three dealership website scopes

Marketing site without live inventory

A small marketing site may cover the dealership story, departments, staff, hours, directions, financing information, trade-in guidance, service pages, contact forms, and local SEO foundations. It is appropriate when inventory lives on another platform and the first goal is a clearer brand and conversion path.

A focused build might take roughly 40 to 90 hours, depending on content readiness, design depth, forms, accessibility, migration, analytics, and review cycles. At Vertinus's published rate of $49.99 per hour, that is approximately $2,000 to $4,500 for implementation before third-party services and taxes. The range is an estimating model, not a quote.

Website with inventory and lead capture

Adding live inventory changes the project. The site may need feed imports, VIN or stock identifiers, photo handling, filters, vehicle detail pages, price and disclosure logic, sold-status rules, lead forms, source attribution, CRM handoff, and error monitoring.

A reasonable planning range for a custom or heavily integrated release may be 120 to 260 hours. The lower end assumes a clean feed, one main inventory source, limited departments, and straightforward forms. The upper end is more realistic when the site must reconcile multiple sources, preserve merchandising, support complex vehicle states, or provide staff tools.

Website with digital retailing and operational workflows

Digital retailing can include payment estimates, trade-in intake, credit or finance handoffs, appointment scheduling, document collection, deposits, chat or text, and a continuation path for a salesperson. Service scheduling, parts requests, and multi-location rules may be separate workstreams.

Once the website coordinates several departments and systems, planning for 260 to 500 or more hours is reasonable. A vendor may supply some of these capabilities through subscriptions. A custom build may give you more control, but it also puts data mapping, security, monitoring, and support inside the project scope.

What drives the price

• Inventory source: A clean, documented feed is cheaper to integrate than several feeds with conflicting prices, photos, or status values.
• Inventory behavior: Search filters, comparison, saved vehicles, alerts, sold pages, and price history each add rules and testing.
• Lead routing: Routing by department, location, vehicle, source, business hours, and staff availability needs explicit fallback behavior.
• Content: Existing approved copy and photography reduce production time. Thin or copied department pages create more editing and strategy work.
• Design: A custom responsive interface costs more than a template, especially when mobile inventory and forms need careful interaction design.
• Migration: Existing URLs, redirects, analytics, forms, and inventory history need an inventory before launch.
• Ownership: Domain, code, hosting, analytics, feed credentials, and customer data should be addressed in the agreement.

One-time build costs are not the whole budget

Ask which ongoing costs are included and which are separate. Common recurring items include inventory or CRM vendors, payment or credit providers, chat, texting, hosting, domains, image storage, analytics, support, and content merchandising.

There is also operational work. Someone must check failed inventory imports, correct missing photos, close sold vehicles, update incentives, review lead failures, and maintain department hours. An inexpensive website that requires daily manual correction may cost more than a better-scoped system.

How to compare dealership website proposals

Do not compare only the headline price or the number of templates. Ask each provider to describe the data flow and the acceptance criteria.

• Which system is the source of truth for price, availability, photos, and vehicle identifiers?
• What happens when an import fails or a vehicle is sold?
• Where do sales, service, parts, and finance leads go?
• Can the dealership edit copy, photos, offers, and structured content?
• Which accounts and credentials will the dealership own?
• How are redirects, analytics, forms, and search visibility handled at launch?
• What is included in support, and how are new requirements estimated?

The guide on comparing website design proposals provides a general framework. For inventory-specific work, add a test list for new, used, reserved, sold, transferred, duplicate, and missing-data scenarios.

Where a smaller first release makes sense

You do not need to automate every dealership process on day one. A first release might focus on a fast, accurate inventory experience, strong vehicle pages, department forms, CRM routing, and useful reporting. Later releases can add saved searches, trade-in workflows, service reminders, staff dashboards, or deeper digital retailing.

That approach gives the team a usable website sooner and produces real data about what shoppers and staff actually need. It also reduces the risk of paying to automate a process that has not been agreed internally.

A clear estimate starts with a clear boundary

A dealership website estimate should name the inventory sources, departments, page types, data fields, lead destinations, user roles, launch responsibilities, exclusions, and acceptance tests. It should show hours by workstream instead of hiding all uncertainty in one total.

Vertinus bills $49.99 per hour for time actually worked up to an approved estimate. The estimate can be split into discovery, design, implementation, integration, content migration, testing, and launch so the dealership can approve the next step with better information.