Regional vs enterprise auction software: choosing the right fit for your house
Why most regional auction houses end up overpaying for enterprise software built for global houses, and what the mid-market actually needs to convert consignments.
By Benjamin Davis
A regional auction house in Worcestershire spent fourteen months evaluating enterprise auction management software. Three vendors, eleven demo calls, two on-site workshops, and a procurement cycle that involved their accountant, their IT consultant, and a sixteen-page RFP document. When the quotes came back, the lowest was £32,000 per year, required a six-week implementation, and included features for multi-currency settlements, branch consolidation, and white-label bidding platforms they would never use.
They are still running their old system. The pipeline of consignment enquiries is still leaking. And they have lost a year and a half to vendor theatre.
This happens all the time. A regional house hits a growth ceiling, decides it needs better software, and ends up in a sales process designed for enterprises with £100M annual hammer and dedicated IT teams. The software is not bad. It is just the wrong fit. It solves problems the regional house does not have and ignores the ones it does.
This piece is about the split between regional and enterprise auction software, why the mid-market keeps getting priced out, and how to think about what your house actually needs.
The enterprise playbook, and why it does not fit
Enterprise auction software was built for Sotheby's, Christie's, Bonhams, and houses like them. Multi-site operations. Multi-currency settlements. Global client databases. Specialist IT support. Budgets in the hundreds of thousands. The software does what it was designed to do, which is handle front-to-back auction workflows at scale across geographies with compliance layers, API integrations, and white-label bidding infrastructure.
The problem is that the same vendors sell downmarket versions of the same software to regional houses with £10M annual hammer and five specialists, and the fit is terrible. The pricing is opaque (always "contact us for a quote"). The onboarding takes weeks. The features assume workflows that a regional house does not have. And the support model expects you to have an IT team on staff who can handle integrations and troubleshooting.
We have sat with dozens of regional houses over the past two years, and the story is always some version of this. The house knows it needs better software. It talks to the enterprise vendors because those are the names everyone knows. The vendors are polite, professional, and genuinely trying to help. But the software they are selling was not designed for a single-site house in the Cotswolds with three specialist departments and a saleroom manager who also handles IT.
The wedge is not that enterprise software is bad. It is that it solves the wrong problems. A £10M regional house does not need multi-currency settlement. It needs faster response time on consignment enquiries. It does not need white-label bidding infrastructure. It needs automatic routing so the head of jewellery sees jewellery enquiries and the head of furniture sees furniture enquiries without anyone having to manually triage. It does not need branch consolidation. It needs a weekly digest that shows the CEO which specialist queues are getting stale.
Enterprise vendors cannot easily offer those features because their product roadmap is driven by global houses paying six figures a year. The result is a mid-market gap where regional houses are stuck choosing between enterprise software that costs too much and solves the wrong problems, or free tools like spreadsheets and shared inboxes that do not scale past fifty enquiries a week.
What regional auction software actually needs to do
A regional auction house, at its operational core, has three problems that software ought to solve.
First, enquiry capture and routing. Sellers submit valuation enquiries via the website. Those enquiries need to land in front of the right specialist, fast, with enough context to draft a reply. If that process takes more than four hours, the house is losing consignments to competitors who reply faster. We have written separately about why response time decides the consignment, but the short version is: speed is not a nice-to-have. It is the strategy.
Second, specialist time management. Specialists at regional houses are covering multiple roles. The head of jewellery is also doing viewings, writing catalogue descriptions, and taking valuation appointments. Pre-drafted responses, automatic follow-up sequences, and smart routing that handles leave cover are the difference between a specialist who spends two hours a day on enquiry admin and one who spends twenty minutes.
Third, measurement. Most regional houses cannot tell you their average response time, their enquiry-to-consignment conversion rate, or which marketing channel is actually generating consignments. They guess. The guess is usually wrong by a factor of two or three. Software ought to measure those things automatically and surface them in a way the CEO or managing partner actually looks at. Not a dashboard. A Monday-morning email with five numbers.
That is it. Those are the three things regional auction software needs to do well. Everything else is secondary. Cataloguing, lot management, bidding infrastructure, post-sale settlement, those layers matter, but they are not where most regional houses are bleeding pipeline. The enquiry stage is.
Enterprise software does not prioritise those three things because the buyers it serves have already solved them with people. A global house has client-strategy teams, business-development coordinators, and entire administrative functions whose job is to ensure no enquiry slips. A regional house with £15M annual hammer cannot afford that machinery. It needs software that does what those teams do.
The pricing gap, and why it matters
Enterprise auction software is opaque on price. Every vendor we have looked at hides pricing behind a "contact us" form. The quotes, when they arrive, are typically £15,000 to £50,000 per year, sometimes higher, often structured as multi-year contracts with setup fees and ongoing support charges. For a house doing £10M to £20M annual hammer, that is 0.2 to 0.5 percent of revenue going to software before you have paid for marketing, specialist salaries, or saleroom costs.
Regional software, when it is priced transparently, sits at £1,000 to £6,000 per year for enquiry and consignment management. That is one-tenth to one-twentieth the cost of enterprise software, and it solves the actual bottleneck.
The reason the pricing gap exists is structural. Enterprise vendors sell through sales teams. Every deal requires multiple calls, custom quotes, and negotiation. That sales model works when the average contract is £30,000 a year and you are closing ten deals annually. It does not work when the contract is £3,000 and you need two hundred deals to hit revenue targets. So enterprise vendors stay upmarket, regional houses get priced out, and the mid-market gap widens.
The modern answer, which is what we have built ABSystems around, is product-led growth. Transparent pricing. Self-serve trial. A demo dashboard you can explore without booking a call. The buyer can evaluate the product on their own timeline, sign up when they are ready, and onboard without needing a six-week implementation cycle. That model only works if the software is simple enough to onboard yourself, which is a design constraint enterprise vendors do not have.
Want to see what regional-first software looks like? Explore the live demo dashboard on sample data. No signup, no call required. See routing, response-time tracking, and specialist queues in action.
Features that matter vs features that impress in demos
One of the traps regional houses fall into is buying software based on what impresses in a demo rather than what they will actually use. Enterprise vendors are very good at demos. They will show you multi-site dashboards, real-time bidding analytics, white-label apps, API integrations with fifteen third-party tools, and compliance modules for GDPR, PCI-DSS, and whatever else sounds serious.
Most of that will never get used. A single-site regional house does not need multi-site dashboards. It does not need white-label bidding apps because it is already using the-saleroom or EasyLive. It does not need API integrations with fifteen tools because it is only using three.
The features that actually matter for a regional house are boring. Automatic routing of enquiries to specialists. Pre-drafted responses that compress drafting time from five minutes to ninety seconds. Follow-up sequences so sellers who do not reply get a polite nudge at 48 hours, seven days, and twenty-one days. Response-time tracking so the CEO knows which queues are getting stale. UTM attribution so the house knows which marketing spend is generating consignments.
None of those features are flashy. They do not demo well. But they are the ones that move conversion from 12% to 30%, which is the difference between a house that is growing and a house that is stuck.
Self-serve vs sales-led, and why it matters for regional houses
Enterprise software is almost always sales-led. You cannot try it without booking a demo. You cannot see pricing without a call. You cannot onboard without a six-week implementation cycle and a dedicated account manager. That model works for enterprises with procurement teams and IT departments. It does not work for a regional house where the CEO is also the one evaluating software in the evenings after a viewing day.
Self-serve software, by contrast, assumes the buyer wants to evaluate the product on their own. Transparent pricing on the website. A demo dashboard you can explore without signing up. A free trial with no credit card required. Onboarding that takes twenty minutes, not six weeks. That model respects the buyer's time and removes the friction of a sales cycle.
The difference is not just convenience. It is strategic. A sales-led vendor makes money by closing large, multi-year contracts with enterprises. A self-serve vendor makes money by converting a high volume of smaller customers. The incentives are different, and they shape the product. Sales-led vendors optimise for features that impress in demos. Self-serve vendors optimise for features that actually get used.
ABSystems is self-serve by design. Pricing is public (£79, £199, £449 per month, or contact us for enterprise). The demo dashboard runs on sample data and you can explore it without booking anything. The trial is genuinely free, no credit card. Onboarding takes under an hour. That is the model we think regional houses deserve.
Integration with live bidding platforms
One of the most common questions we get from regional houses is whether ABSystems replaces their existing auction management system or sits alongside it. The answer is: it depends what you are using the auction management system for.
Most regional houses use a combination of tools. The cataloguing and lot management happens in one system (often something like Auction Mobility, Antiques Auction Software, or a custom-built tool). The live bidding happens on a platform like the-saleroom, EasyLive, Invaluable, or Bidlogix. The post-sale settlement and invoicing happens in accounting software like Xero or Sage. And the enquiry handling happens in shared inboxes or spreadsheets.
ABSystems is designed to replace the last part of that stack. Enquiry capture, routing, pre-drafted responses, follow-up sequences, response-time tracking, and conversion analytics. It does not replace your auction management system or your live bidding platform. It integrates with them where it makes sense (for example, syncing consignor data from ABSystems into your cataloguing system when an enquiry converts).
The wedge is narrower than enterprise software, and that is deliberate. We are not trying to be a front-to-back solution. We are solving the enquiry stage, which is where most regional houses are bleeding pipeline, and doing it better than anyone else. Once an enquiry converts to a consignment, you hand it off to your existing tools. That is the model that works for houses that do not want to rip out their entire stack.
Support and onboarding: UK-based vs offshore
This sounds like a small detail, but it matters more than people realise. Most enterprise auction software is built by vendors with offshore development teams and thin in-market support. That is fine for global houses with IT departments who can handle integrations and troubleshooting themselves. It is less fine for regional houses where the saleroom manager is also the IT person.
ABSystems is UK-based. Support is UK-based. Onboarding happens in your timezone, not at midnight because the support team is in Tbilisi or Manila. When something breaks, you get a reply in hours, not days. That is part of the product, and it is one of the reasons houses choose us over enterprise vendors with better-known names.
Frequently asked questions
What is the difference between regional and enterprise auction software?
Enterprise software is built for multi-site, multi-currency, global auction houses with dedicated IT teams and six-figure budgets. Regional software is built for single-site or small multi-site houses with simpler workflows and transparent pricing. The difference is scope, complexity, and price, not quality.
How much should a regional auction house pay for software?
For enquiry and consignment management, £80 to £500 per month is normal for regional houses. For full auction management (cataloguing, bidding, settlement), £1,000 to £3,000 per month depending on volume. Anything above that, you are paying for enterprise features you likely do not need.
Can a regional house use enterprise auction software?
Yes, but it usually means paying for features you will never use, longer setup cycles, opaque pricing, and a sales-led process where every question requires a demo call. For most regional houses, this is overkill.
What should I look for when choosing auction software?
Transparent pricing, self-serve trial, UK-based support, specialist routing, response-time tracking, and integration with the-saleroom or EasyLive for live bidding. If the vendor will not show you pricing without a call, walk away.
What to do if you are stuck in an enterprise sales cycle
If you are a regional house currently stuck in an enterprise software evaluation, here is what we would recommend. Ask the vendor three questions.
First, can you show me transparent pricing, right now, without a custom quote? If the answer is no, you are buying software designed for enterprises, not regional houses.
Second, can I try the product for free, without a credit card, without booking a call? If the answer is no, the vendor is sales-led, and you will spend weeks in a procurement cycle before you know if the product actually fits.
Third, what does onboarding look like? If the answer is "six-week implementation with a dedicated account manager", you are looking at enterprise software. If the answer is "twenty-minute self-serve setup", you are looking at regional software.
Those three questions will tell you immediately whether the software was built for you or for someone ten times your size. If the vendor cannot answer those questions the way you need, walk away. There are better options.
Where ABSystems fits
We built ABSystems for the 400 to 600 UK regional auction houses that enterprise vendors have priced out. Single-site or small multi-site. £2M to £40M annual hammer. Five to thirty staff. Mixed specialist sales. Running on email, spreadsheets, and the-saleroom for live bidding.
The wedge is enquiry and consignment management. We do that one thing better than anyone else. Transparent pricing. Self-serve trial. UK-based support. Onboarding in under an hour. Integration with your existing auction management and live bidding platforms.
If you are a regional house that has looked at enterprise software and decided it is too expensive, too complex, or too sales-heavy, we built ABSystems for you. See the live demo or book a 20-minute walkthrough when you are ready.
The mid-market deserves software that fits. That is what we are building.