Fixed quote after a free call

A car dealer website that sells stock and books the workshop

We build a car dealer or garage website with fast inventory pages generated from your stock feed, clean handling of sold vehicles, service and MOT booking, vehicle and business schema, and lead forms that send ADF leads straight into your CRM. Projects typically cost $5,000 to $15,000 and take eight to twelve weeks.

The problem

Why car dealer websites lose buyers

Buyers browse stock on their phones, and a forty-photo gallery straight from the camera makes pages crawl. Sold cars leave dead pages in search results, and lead forms often email a shared inbox rather than the CRM.

Garages compete for local searches such as MOT near me or car servicing in a town, and thin service pages with inconsistent addresses lose to better-organised competitors.

What we build

What our car dealer website design includes

Inventory from your feed

Vehicle pages generated from your DMS or stock feed, with compressed galleries and key specs.

Sold-car handling

Sold vehicles redirect to similar stock or keep a sold page, avoiding broken links.

Lead forms into the CRM

Enquiry, test drive, trade-in and finance enquiry forms sent as ADF leads to your CRM.

Service and MOT booking

Booking connected to your shop scheduler or a request form.

Vehicle and business schema

Car and AutoDealer or AutoRepair structured data with consistent contact details.

Speed and security

PageSpeed tested, HTTPS, security headers and a technical SEO audit before launch.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Shopper searches

    A buyer or driver finds you through search or a listing.

  2. 02 Automated

    Stock and services shown

    Inventory and service pages load fast with current data.

  3. 03 Automated

    Lead or booking

    Forms send ADF leads to the CRM and bookings to the scheduler.

  4. 04 Advisor review

    Team keeps it current

    Staff check stock photos, offers and service pages.

  5. 05 Advisor or manager decides

    Offers approved

    Advertised prices, finance wording and offers are approved by the dealer principal before publishing.

How it behaves

How the dealer website behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the shopper sees

  • Fast vehicle pages with clear photos on a phone
  • Easy enquiry, test drive and service booking
  • No dead pages for sold cars

What staff see

  • ADF leads arriving in the CRM
  • Service bookings in the scheduler
  • Stock updated from the feed

What the automation does

  • Imports stock and compresses galleries
  • Redirects sold vehicles
  • Keeps schema and sitemap current

Edge cases and fallbacks

Stock feed fails
The last good feed stays live and staff are alerted.
CRM rejects an ADF lead
The lead is emailed to the sales manager and logged.
Old URLs from the previous site
Redirected to the matching new page.

Architecture

A dealer website with inventory and booking at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Search, listings Google, maps Stock feed DMS inventory Dealer website Fast pages Lead forms ADF to CRM Service booking Scheduler Sales and service Follow up
  • Input
  • Logic and services
  • Output
  • People

How it flows

  1. 1 Shoppers arrive from search and listings; stock arrives from the DMS feed.
  2. 2 Fast inventory and service pages show current vehicles and services.
  3. 3 Lead forms send ADF leads to the CRM and service bookings to the scheduler.
  4. 4 Sales and service staff follow up; offers are approved before publishing.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Car dealer & garage website with inventory pages project plan

Typical time to launch: about 9 weeks, then support

  1. 01

    Discovery

    About 1 week

    Current site, stock feed, CRM, scheduler and local competitors.

  2. 02

    Content and design

    About 2 weeks

    Page plan, inventory templates, service pages and design.

  3. 03

    Build

    3 to 5 weeks

    Inventory import, galleries, forms, booking, schema and redirects.

  4. 04

    Test

    About 1 week

    Speed, accessibility, forms, ADF delivery and SEO audit.

  5. 05

    Launch

    2 to 3 days

    Go live, update Google Business Profile, submit the sitemap.

  6. 06

    Support

    Ongoing

    Optional monthly care and feed monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

Laravel or WordPress Tailwind CSS Your DMS or stock feed ADF XML lead delivery Schema.org Car and AutoDealer markup PageSpeed Insights and Search Console

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and audit

    Current site, feed, CRM and competitors.

    $500 – $1,200

  • Content and design

    Page plan, templates and design.

    $1,200 – $3,500

  • Build

    Inventory import, galleries, forms, booking and schema.

    $2,300 – $7,300

  • Integrations

    Stock feed, ADF to CRM and scheduler.

    $500 – $1,800

  • Testing and launch

    Speed, accessibility, redirects and launch.

    $500 – $1,200

  • Total project estimate

    $5,000 – $15,000

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. A garage site without inventory sits at the lower end. Hosting, domain and feed provider fees are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Hosting and domain: Billed by your hosting provider and registrar.
  • Stock feed: Your DMS or feed provider's own plan.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: honest advertising

With the CARS Rule vacated, federal and state unfair and deceptive practices law still governs advertised prices and offers.

Source: www.autoremarketing.com

US: Safeguards Rule for finance forms

Finance enquiry forms collect customer financial information, so they sit within the dealer's information security program.

Source: www.law.cornell.edu

Honest reviews

The FTC rule bans fake or bought reviews; review widgets show genuine reviews only.

Source: www.ftc.gov

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Car dealer & garage website with inventory pages questions, answered.

Fast inventory pages from your stock feed, clear vehicle details and photos, sold-car handling, lead forms into the CRM, service booking, finance enquiry routes and solid local SEO.

Platform providers offer templates and hosted inventory. We build a site you own, connected to your own CRM and workflows, and can also improve a provider site if you prefer to stay.

Not if handled well. Sold vehicles redirect to similar stock with a single 301 or keep a sold page, and we test redirects before launch.

Yes, as ADF XML or through the CRM's API, with source and vehicle recorded.

Yes. Service, MOT and repair pages with booking, local schema and consistent contact details, without inventory.

Leads and bookings by page and source, vehicle page speed and Search Console impressions for stock and service pages.

Free 20-minute call

Want this for your automotive?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call