Dealership Management Software: Build or Buy at Your Rooftop Count
The threshold is one rooftop. A single store dealer should buy and stay bought: Tekion, Dealertrack, CDK Global and Reynolds and Reynolds all cover that operation properly, and adapting to a good product costs less than owning a mediocre one.
On this page
The threshold is one rooftop. A single store dealer should buy and stay bought: Tekion, Dealertrack, CDK Global and Reynolds and Reynolds all cover that operation properly, and adapting to a good product costs less than owning a mediocre one. The build case starts at two to five rooftops with a used vehicle operation, and even then the honest first move is one module, usually multi lot inventory, at $60,000 to $110,000 over four to six months. A full replacement at $180,000 and up is right for very few, and most groups get the return they wanted without ever touching it.
When is off the shelf genuinely the right call here?
Buy first, and for most single rooftop dealers buy and stay bought. A packaged dealer management system is cheaper, faster and maintained by somebody else. Tekion, Dealertrack, CDK Global and Reynolds and Reynolds all handle a single store properly, and the discipline of adapting your process to a good product costs less than the freedom of owning a mediocre one.
Two more buy cases are worth naming precisely, because groups get them wrong in both directions. If repricing is your only complaint, buy the pricing tool. vAuto from Cox Automotive is the established product for used vehicle appraisal and repricing, and a group whose data is fine and whose decisions are merely slow will get further with it than with a custom engine. If your desk process is conventional, buy the customer system. VinSolutions and DealerSocket model a standard sales funnel, and building a customer database to house a workflow they already handle is the most avoidable spend in this category.
Keep your accounting ledger at any size. It works, it is audited, and replacing it inside a software project adds cost without touching the problem that started the conversation. Keep your syndication vendor too. Rebuilding feeds to the listing sites is possible and pointless. Pay for the feed and spend the budget on the inventory logic nobody sells you.
When does a custom build actually pay off?
It pays off when the packaged option is actively costing you deals rather than merely annoying you. The symptoms are specific and they arrive together. Staff run parallel spreadsheets because the platform cannot answer a question somebody asks daily. Adding a rooftop means renegotiating per seat licensing that scales badly. And a pricing or reconditioning decision that should take minutes takes a day because the data sits in four systems. If none of those bite, packaged software is the right call. If all three do, you have a case.
What you are buying with a build is a data model, not features. One vehicle moving between rooftops has to stay one record carrying its reconditioning cost, days in inventory and floor plan interest. One buyer walking three of your lots in a month has to be one customer. Those are structural decisions with consequences everywhere downstream, and they are exactly what a platform built for a single store handles weakly.
The bands are set by how much of your stack you keep, not by how many rooftops you run. An analytics or repricing layer over systems you keep runs $45,000 to $90,000 over three to five months. A single module such as multi lot inventory runs $60,000 to $110,000 over four to six months. Inventory plus customer system plus finance and insurance integrated runs $110,000 to $180,000 over six to eight months. A full replacement runs $180,000 to $250,000 and upward over eight to twelve months, and it is right for very few groups.
How do they compare on the things that matter in this industry?
- Cross rooftop identity. Packaged customer systems were built around a single store, so the same buyer walking three of your lots is three records unless somebody merges them by hand. That is an architectural boundary rather than a missing setting, and it is why groups end up with a spreadsheet answering the question of who is already in the funnel.
- Vehicle records across lots. A unit transferring between rooftops should carry its reconditioning cost, days in inventory and floor plan interest with it. Where the packaged system treats a transfer as a sale out and a purchase in, the days in inventory clock resets and the true cost of the unit is lost, which is exactly the number your repricing depends on.
- Repricing rules. vAuto handles market based repricing well and there is no reason to rebuild it. What a custom layer adds is rules that reach across rooftops, incorporate your own reconditioning and floor plan cost per unit, and carry an audit trail of who changed what and why. That is a different requirement from market pricing, and it is worth naming precisely before you spend, because conflating the two is how groups buy the wrong thing.
- Per seat economics. Packaged licensing climbs every time you add a rooftop or a desk. A build's cost is flat afterwards. That difference does not matter at one store and it compounds visibly past three.
- Finance and insurance re keying. Where menu selling, lender submission and product markup do not flow into the deal without retyping, the cost is not just labour, it is error rate in the part of the transaction where the money is made.
What does total cost of ownership look like at your scale?
Run this over three years and be honest about all four inputs. First, packaged licensing including the per seat costs that climb with every rooftop and desk. Second, the spreadsheets, meaning salaried hours spent maintaining parallel records because the platform cannot answer a daily question. Third, the re keying, meaning the deal that closes at six in the evening and still needs somebody to retype numbers into two systems the next morning, plus the errors that creates. Fourth, the decisions that take a day because the data lives in four places, priced as extra days of inventory on units that should already have been repriced.
On the build side, a four rooftop used vehicle group that kept its dealer management system and its ledger came to $236,000 all in, including $38,000 of migration and $26,000 of integration. Continuing engineering runs roughly a sixth of build cost annually, about $39,000 there, spent on lender interface changes, a new rooftop joining, captive finance products with different terms and repricing rules retuned as the market moves. Amortised over five years plus maintenance that is around $47,000 a year, and unlike per seat licensing it does not climb when you add a store.
Three running costs continue regardless of which path you take: market data subscriptions, syndication and listing fees, and your accounting platform. Add monitoring for lender portal connections, because a submission path that silently stops working costs deals on a Friday afternoon before anyone notices. If the build pays for itself inside three years and removes the per seat ceiling on growth, it is defensible. If it does not, it is a vanity project, and a developer worth hiring will say so during discovery rather than after the contract.
What does the hybrid look like, and when is it the honest answer?
It is the honest answer for almost every group that builds anything, and the worked example above is exactly it. That $236,000 never replaced the dealer management system. The group kept it, kept the accounting ledger, kept the syndication feeds, and spent the budget on the inventory, pricing and deal logic that packaged software would not shape around them.
Start with one module rather than a platform. Pick the workflow costing you the most, usually multi lot inventory or repricing, and build only that. It delivers value in months rather than a year, and it gives you a working system to judge the developer on before the larger commitment. If the first module lands well, you extend it. If it does not, you have spent a fraction of a replacement finding out.
Migrate in tiers when you do move data. Open inventory, active deals and roughly the last two years of history come across in full, and older records land in a read only archive that is searchable and never edited. Insisting on a complete history before go live is the single most common way this timeline slips a quarter, and it is a choice rather than a constraint.
Then insist on phased delivery with something in a salesperson's hands by roughly month three. A vendor who wants to disappear for eight months and return with a finished platform is the largest single risk in this category, and phasing is your protection against a build that drifts.
Which should you choose, by operator size and stage?
One rooftop, conventional new and used mix: buy. Tekion, Dealertrack, CDK Global or Reynolds and Reynolds, plus vAuto if repricing is the pain and VinSolutions or DealerSocket if the desk is. Spend the difference on inventory.
Two or three rooftops, mostly new vehicle: still buy, but start measuring. Count the hours your team spends maintaining parallel spreadsheets and ask what per seat licensing looks like at five stores rather than three. Those two numbers turn an instinct into a costed case, and plenty of groups run them and find nothing worth building yet.
Two to five rooftops, heavily used vehicle, units moving between lots: build one module. Multi lot inventory is where used operations lose the most, because a unit transferring between stores has to stay one record with its reconditioning and floor plan cost intact. Four to six months, $60,000 to $110,000, and it answers whether the developer understands your business before you commit anything larger.
Four or more rooftops where the module landed and the case held: extend into the customer system and finance and insurance, at $110,000 to $180,000 for the integrated shape. Count your lender connections before you budget rather than after, because a well documented portal is a week of work and an undocumented one with no test environment is a month.
Full replacement: only when the packaged platform is demonstrably costing you deals, and even then pilot on one rooftop for a full month including a month end close before it touches the group. Under scope integration and migration and the timeline slips there rather than in the code, every time.
If you want a second opinion before signing anything, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You keep the specification either way.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- This analysis cites IDC research that companies lose 20-30% of revenue annually to inefficiencies caused by data silos, Gartner's estimate that poor data quality costs organizations at least $12.9 million per year on average, and a Salesforce benchmark that 80% of IT leaders say data silos hinder digital transformation - illustrating the business case for integrating systems. Source: Cherry Bekaert (citing IDC, Gartner, Salesforce, DATAVERSITY) (2024) →
- McKinsey found personalization most often drives 10-15% revenue lift, and companies that grow faster drive roughly 40% more of their revenue from personalization than slower-growing peers. Source: McKinsey & Company (2021) →
- McKinsey found that currently demonstrated technologies can fully automate about 42% of finance activities and mostly automate a further 19%, indicating roughly 60% of finance work is technically automatable. Source: McKinsey & Company (2018) →
- 88% of customers say good customer service makes them more likely to purchase from a brand again in the future, quantifying the direct revenue link between support quality and retention. Source: HubSpot (2024) →
Frequently asked questions
What does it cost to migrate off CDK Global or Reynolds and Reynolds?
Migration is reconciliation rather than export, which is why it is the line most often left out of a quote. Historical deals, trade histories, reconditioning records and inventory movements carry years of local conventions a new data model does not share, so every category needs mapping and checking rather than loading. In one four rooftop example it came to $38,000.
The saving is tiering. Bring open inventory, active deals and roughly two years of history across in full, and put older records into a read only archive that is searchable and never edited. Demanding a complete history before go live is the most common way this timeline slips a quarter.
What happens if our dealer management vendor raises per seat pricing?
That is the exposure people underestimate, because it climbs with every rooftop and every desk you add rather than staying flat. It is also why some staff are not in the system at all, which is the hidden version of the same cost.
Two defences. Know what a full export of deals, inventory history and customer records looks like before you need it, and ask for a sample now rather than at renewal. And keep the logic you build in your own system, so a change of platform becomes an integration project rather than a rebuild.
How long does a dealership build take to reach production?
Four to six months for a single module, six to eight for inventory plus customer system plus finance and insurance, and eight to twelve for a full replacement. Discovery is three to five weeks of that and maps the workflows you actually run rather than the ones the organisation chart claims.
Insist on phased delivery with something in a salesperson's hands by roughly month three. Integration and migration run in parallel and are usually the long pole, so under scoping them means the timeline slips there rather than in the code.
Is a custom repricing layer better than vAuto?
Not if repricing is your only complaint. vAuto from Cox Automotive is the established product for used vehicle appraisal and repricing, and a group whose data is fine and whose decisions are merely slow will get further with it than with a custom engine.
A custom layer earns its place when the rules have to reach across rooftops, incorporate your own reconditioning and floor plan cost per unit, and carry an audit trail your managers are accountable to. That is a different requirement from market based pricing, and naming it precisely before you spend is what stops a group buying the wrong thing twice.
Can we build only the inventory module and keep everything else?
Yes, and for most groups that is the right first move. Multi lot inventory is where used vehicle operations lose the most, because one unit moving between rooftops has to stay one record carrying its reconditioning cost, days in inventory and floor plan interest.
It costs $60,000 to $110,000, reaches production in four to six months, and gives you a working system to judge the developer on before you commit to anything larger. If it lands well you extend. If it does not, you have spent a fraction of a replacement finding out.
How much does the finance and insurance module add?
Around $40,000 to $55,000 for menu selling, lender submission and product markup flowing into the deal without re keying. It carries the heaviest testing burden in the build, because it is where the money is made and where a re entry error costs the most.
The integration side is what moves the range. A well documented lender portal is a week of work and an undocumented one with no test environment is a month, so count your lender connections before you budget rather than after.
Should a single rooftop dealer build anything at all?
Usually nothing. Packaged platforms cover a single store properly, they are cheaper and faster, and someone else maintains them, so the capital returns more in inventory or in people.
Build only when packaged software is actively costing you deals, forcing headcount to paper over gaps, or capping growth through per seat pricing. Run the three year comparison first, and if the build does not pay for itself inside that window, stay packaged.
How do we judge whether a developer understands dealership work?
Ask them to describe, in your terms, how a used vehicle moves from auction through reconditioning to the lot to sold. If they cannot, they will learn it on your budget. Then ask what dealership problem they solved and how they knew it was solved.
Confirm three things in writing before kickoff: that integration and migration are scoped as first class work rather than bolted on at the end, that you own the code and the data outright, and that delivery is phased with working software early. The cheapest quote that misreads your workflow is the most expensive path to a system you abandon.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
We run everything on Airtable and spreadsheets. When is it time to go custom?
The switch usually makes sense when you hit one of two walls: Airtable's record caps (125,000 records per base on the Business plan) or logic the tool cannot express, like multi-step approvals with conditional pricing. There is also a simple cost signal: 25 people on Business at roughly $45 per seat per month is about $13,500 a year, forever, for a tool you are already fighting. Custom is worth it when the workflow is core to how you make money; for peripheral processes, staying on Airtable is the right call.
Couldn't I just build my app in Bubble or another no-code tool instead of hiring an agency?
For validating an idea with real users, yes, and we tell clients that honestly. The walls come later: Bubble apps cannot be exported as code to run anywhere else, performance drops on complex data operations, and usage-based pricing climbs as you grow. A meaningful share of Digital Heroes custom builds are rebuilds of no-code MVPs that proved the business worked, which is the system operating as intended: validate cheap, then build the version that scales.
How do I make sure custom software is secure and compliant with rules like HIPAA?
Start with the baseline every business system should have: encryption in transit and at rest, role-based access control, and audit logs. If HIPAA applies, the hosting provider must sign a Business Associate Agreement, which AWS, Azure, and Google Cloud all offer, and access controls have to be designed in from day one, not bolted on. SOC 2 certifies a company's operating practices, not a codebase, so ask vendors what they have shipped in your regulated domain rather than which logos are on their website.
How do I calculate whether custom software will pay for itself?
Divide the build cost by the monthly benefit, where benefit is hours saved times loaded hourly cost, plus subscription fees replaced, plus any revenue the software unlocks. Three staff saving 10 hours a week each at a $40 loaded rate is about $62,000 a year, which pays back a $60,000 build in roughly 12 months. Across Digital Heroes internal-tool projects, 12 to 24 months is the normal payback range, and anything projecting under 6 months usually means the spreadsheet is hiding costs.
Is it cheaper to customize Salesforce than to build a custom CRM from scratch?
If you use less than a third of what Salesforce does, a custom CRM is often cheaper by year three. Salesforce Enterprise lists at $165 per user per month, so 25 seats cost about $49,500 a year before admin and consultant fees, while a focused custom CRM runs $60,000 to $100,000 once plus 15 to 20% a year in maintenance. If you genuinely need Salesforce's ecosystem, reporting, and app marketplace, customizing it beats rebuilding it; the mistake is paying enterprise prices to use it as a glorified contact list.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Tara.
React Native Lead · Delhi · 5 posts on the site
Published · Last updated .
