Custom web applications for car dealerships
Websites for new and used car dealerships
In the car dealerships industry, custom web applications isn't a stylistic exercise: it's the tool that solves the real problems of your vertical. Here you'll find how we apply it specifically, what you take away, and how much it costs to get started.
The problems we see every time in the car dealerships industry
If at least one of these sounds familiar, custom web applications is the right lever.
The concrete results
- Software tailored to your real process, not the other way around
- A modern stack (Next.js, Postgres) maintainable long-term
- Native integrations with Odoo, Stripe, AWS, external systems
- Sprint-based development with weekly demos: see progress, steer as you go
- Your code, zero lock-in: the GitHub repository is under your control
- Technical and functional documentation delivered with the project
The features you simply can't go without
We include them by default on every custom web applications project for the car dealerships industry.
- Vehicle listings with advanced filters (make, model, mileage, year, fuel, price)
- Feed synchronization with portals (AutoScout24, Automobile.it, Subito Motori)
- Car pages with gallery, video, service history, full technical data
- Online trade-in valuation with plate + mileage form
- Test drive request with calendar
- New-car configurator for official brands
- Financing simulator (integration with FCA Bank, Santander, Findomestic)
- DMS and automotive CRM integration (Infocar, Dealer.com, Opteven)
What we work with
We choose the stack on a case-by-case basis, not by personal preference.
- Next.js 15 App Router
- TypeScript
- tRPC
- Postgres
- Drizzle ORM / Prisma
- NextAuth / Auth.js
- Stripe
- Docker
- Tailwind CSS
- AWS S3 / Cloudflare R2
- Odoo JSON-RPC
Where it starts
VAT excluded
The exact price depends on the scale of the project (pages, languages, integrations). For a typical car dealerships business, our dedicated package is the simplest route.
Highway Code and MCTC (vehicle registration authority) rules for vehicle documentation. Mandatory CO2 consumption disclosure per EU Reg. 2019/631 and Presidential Decree 84/2003. Margin VAT scheme for used vehicles (art. 36, Decree-Law 41/1995). 2-year statutory warranty on used cars (reducible to 12 months by agreement). Consumer Code for B2C sales. Financing: mandatory APR/ISC disclosure and Bank of Italy transparency rules.
Frequently asked questions
custom web applications for a car dealerships: how long does a project typically take?
It depends on the scale, but for most cases we're talking about 2-4 weeks from sign-off to going live, content included. For complex cases (many languages, integrations with industry software) it can take 6-8 weeks.
Can I start even if I don't have all my content (text, photos) ready?
Yes. We offer copy support and image selection as a separate package, or we proceed with placeholders and swap them in along the way. The important thing is to nail the positioning before the design phase.
Can I update the site on my own after delivery?
Yes. We deliver with a simple editorial panel (organised by content type) and 2 hours of training included. For structural changes (new sections, new templates) we step in.
Does the site comply with car dealerships industry regulations?
Yes. For this industry we take into account: Highway Code and MCTC (vehicle registration authority) rules for vehicle documentation. Mandatory CO2 consumption disclosure per EU Reg. 2019/631 and Presidential Decree 84/2003. Margin VAT scheme for used vehicles (art. 36, Decree-Law 41/1995). 2-year statutory warranty on used cars (reducible to 12 months by agreement). Consumer Code for B2C sales. Financing: mandatory APR/ISC disclosure and Bank of Italy transparency rules. We always start from compliance, we don't add it afterwards.
Why does a car dealerships project cost more than a generic site?
The car dealerships industry requires specific features, regulatory compliance and an architecture that works for its audience. What's optional on a generic site is included by default here — and it's cheaper to do it right from the start than to fix it later.
What does a custom application really cost?
It depends on the scope, and any serious quote comes after a 1-2 day discovery where we map processes, users, and integrations. Realistic ranges: €5-10k for a simple client portal, €13-20k for an industry-specific management system with workflows and roles, €20-30k for platforms with multiple integrations. Below €5k the risk is an underestimated scope and an incomplete project; above €30k we move into enterprise scope with a dedicated team. Be wary of anyone who quotes you by email without a scoping call: the price is either inflated for cover, or it's low and the project overruns.
Why Next.js and not Bubble/Retool/other low-code?
Bubble, Retool, FlutterFlow work perfectly well for prototypes and MVPs up to 50-200 users. Above those volumes the limits show: performance, rising platform costs, customisation constraints, total lock-in (you can't 'export' a Bubble app). Next.js + Postgres is a stack that handles millions of requests, runs on any hosting, and the code is yours. If the use case is simple and temporary, low-code is fine. If the software becomes core business, custom is the right investment.
How are the sprints structured?
Two-week sprints. Sprint start: planning and priorities with you. During: development, internal testing, async daily updates via Slack/email. Sprint end: live demo of what's been built plus a retrospective (what's working, what we change). You have full visibility on progress and priorities: no surprises at go-live. The code is available from day one on GitHub, accessible to you.
Do you maintain the app after go-live?
Yes, with a dedicated Care contract. Maintenance covers: dependency updates, security patches, uptime monitoring, bug fixes within SLA, minor enhancements. The fee starts at €290/month for small apps and rises based on complexity and the SLA required. Alternatively, if your in-house team feels ready to handle it, we do a full technical handover and stay available on call.
Does it integrate with Odoo / my management system?
Yes, it's one of the most frequent use cases. Odoo exposes complete JSON-RPC APIs; we connect to sync contacts, orders, products, invoices. For other systems (SAP, Zucchetti, TeamSystem) it depends on the available APIs: some have modern REST APIs, others require file export/import or dedicated connectors. We check during discovery: if your system exposes reasonable APIs, we integrate natively; if it doesn't, we build a sync layer.
Can I hire another supplier later, if I need to?
Always. The code lives on GitHub under your account, the technical and functional documentation is delivered, and the stack (Next.js, Postgres, Tailwind) is mainstream and known to any competent developer. No proprietary lock-in, no code held hostage. If tomorrow you want to bring the project in-house or switch agencies, you can do so without rewrites.
Ready for custom web applications in your car dealerships?
Tell us in 3 lines what you need. We reply within 24 working hours with a concrete proposal and transparent prices.
You might also like
- Custom web applications for Industrial B2Bcombo
- Custom web applications for Real estate agenciescombo
- Web design & UX/UI for Car dealershipsWebsites that get noticed and that convertcombo
- SEO — Search Engine Optimization for Car dealershipsGet found by the people searching for what you offercombo
- All Custom web applications servicesservice