Auction House Management Software: Build Custom or Buy Off the Shelf?
The threshold is not lot volume, it is how many of your lots carry negotiated rather than standard terms.
On this page
The threshold is not lot volume, it is how many of your lots carry negotiated rather than standard terms. Below roughly 3,000 lots a year with a standard commission structure, one tax jurisdiction and consignors who are individuals, buy AuctionFlex and a good bookkeeper: a build would be an expensive way to reach the same place, and the money belongs in marketing the next sale. Once more than about a quarter of lots carry negotiated terms, or you sell into two tax jurisdictions, or you take advances and guarantees, build. A first release covering the lot entity, the premium and tax rule engine and consignor settlement runs $55,000 to $120,000 in 12 to 16 weeks, with a full platform at $150,000 to $350,000 over 6 to 12 months.
When is off the shelf genuinely the right call here?
For a large share of salerooms, and we would rather say so on the call than take the project. If you run general line or estate sales with a standard commission structure, one tax jurisdiction, and consignors who are individuals rather than institutions, AuctionFlex covers that operation properly for a fraction of a build. Bidpath is a reasonable answer if the priority is running your own timed and live bidding rather than the back office. Both handle the classic general line and industrial auction workflow well.
At around 1,200 lots a year with standard terms, do not build anything. An off the shelf back office plus a bookkeeper does the job, and a custom settlement engine is money you should be spending on the catalogue and the mailing list.
The other buy decision is about audience rather than administration. If your actual problem is bidder reach, spend on the Auction Technology Group properties and Invaluable rather than on software. Those platforms exist to bring you bidders and they are good at it. No back office improvement has ever won anyone a bidder, and a house that fixes settlement while its sales are thinly attended has fixed the wrong thing.
When does a custom build actually pay off?
Build when two or more of these are true. More than a quarter of your lots carry negotiated rather than standard terms. You sell into more than one tax jurisdiction, or the artist resale right and the margin scheme apply to part of your catalogue. You take cash advances or guarantees against property. You are consigned to by institutions, estates or corporates whose statements and reporting requirements are their format rather than yours. Or settlement is taking a senior person more than a week per sale, which means you are already paying for the software and calling it salary.
The mechanism is worth being specific about, because it is not a feature gap. A lot exists as an intake receipt, a catalogue entry, a condition report, a listing on two or three bidding platforms, and a settlement line. Each lives in a different system with a different identifier. When a lot is withdrawn, re-catalogued into the next sale, or split from a group lot into three, the identifiers diverge permanently and somebody keeps a mapping sheet. That mapping sheet is why reconciliation exists as a job.
The second mechanism is the rule engine. Premium is tiered, and the tiers differ by sale, by department and sometimes by agreement with a specific buyer. Tax on the premium is not the same question as tax on the hammer. In the United States the delivery state decides sales tax treatment and the resale certificate is per state with an expiry date. In the United Kingdom the margin scheme and the standard rate produce different numbers on lots in the same sale depending on how property was acquired and whether it was imported under temporary admission. The artist resale right applies in bands, only to qualifying works, only above a threshold. That is not a percentage field. Modelled as one, plus a note, plus a person who remembers, the person is the risk.
How do they compare on the things that matter in this industry?
- The lot record. One entity with a stable internal identifier from the moment property arrives, with platform listings as child records carrying the external identifier, and group, split, withdraw, pass and re-catalogue as state transitions. Packaged back offices assume a lot belongs to a sale. Build assumes a lot belongs to a consignment and appears in sales, which is what actually happens.
- Premium and tax. A versioned rule set evaluated per lot per buyer, storing the full breakdown of every rule that fired immutably against the invoice. Test any product on this directly: take twenty awkward invoices from your last three sales and ask whether the system reproduces every number and can say which rule produced it.
- Bidder identity. Bidding platforms hand you a registration. They do not hold your paddle limit, your deposit policy, your identity file, your screening result, or the fact that this bidder still owes you for two lots from the March sale. Resolving every platform registration into one bidder record is a build job.
- Settlement. A ledger rather than a report. Every commission, charge, advance and receipt posts against a specific lot and consignor with a date, so a statement is a query rather than an assembly job. Buyer non payment triggers a defined unwind that reverses the settlement line, because non payment is normal rather than exceptional.
- Client money. If an auditor asked today how much of your bank balance is client money and how much is yours, how long would the answer take. This is a control rather than an efficiency saving, and it is the question that most often decides the project.
- Speed to running. Packaged wins outright. Next month against four months is not close, and for a house whose terms are standard that is the whole comparison.
What does total cost of ownership look like at your scale?
A first release covering the lot entity, consignment agreement terms as structured data, the buyer premium and tax rule engine, invoicing and consignor settlement as a ledger runs $55,000 to $120,000 over 12 to 16 weeks in Digital Heroes delivery experience. A full platform adding cataloguing with image handling, condition reports, bidder vetting with screening, client money accounting, a consignor portal and shipping and storage charges runs $150,000 to $350,000 phased across 6 to 12 months.
A worked case: a saleroom running about 6,000 lots a year across two departments, one tax jurisdiction, negotiated seller terms on roughly a third of lots, two bidding audiences. That comes to about $119,000, at the top of the first release band because of the second department and the second platform. A single department saleroom with one platform lands nearer $70,000 on the same functional scope. Adding the full platform takes that house to roughly $230,000 to $300,000 in total.
Running costs are modest and specific. Infrastructure is $300 to $900 a month for the core, rising once cataloguing images are held in the system, because high resolution photography at several thousand lots a year is the storage line that grows. Support and enhancement runs 12 to 18 percent of build cost annually, and cover should span sale days specifically: a settlement engine that fails on the Tuesday after a two session sale is a different problem from one that fails on a quiet Thursday. Tax rule maintenance recurs as rates and thresholds change, and bidding platform interfaces change on the platforms' schedules rather than yours.
Compare that against your real current cost, which is not your back office subscription. Take the days a senior administrator spends settling each sale, multiply by sales per year and by fully loaded cost. Add the charges queried per sale and the time spent reconstructing how a number was reached. If settlement regularly consumes more than a week of a senior person per sale, the salary line is already larger than the amortised build.
What does the hybrid look like, and when is it the honest answer?
The hybrid in this category is unusually well defined, and for many houses it is the entire answer.
Keep AuctionFlex or your existing back office. Keep every bidding platform relationship exactly as it is. Then build one thing: the premium and tax engine, evaluated per lot per buyer, taking the sale, the department, the hammer, the buyer's tax status and delivery address, the property's import status and the artist attributes, and producing a full breakdown stored immutably against the invoice. That runs $26,000 to $45,000 over six to eight weeks and slots between your back office and your invoicing.
It removes the most common source of disputed charges and gives you an answer when a buyer queries a number eighteen months later. It is versioned, so when you change your premium structure next season the old sales still compute the old way.
The second hybrid step, if the first proves itself, is the settlement ledger without replacing anything else. Build the unwind path at the same time as the settlement path rather than afterwards, and run one real sale in parallel with your existing spreadsheets before trusting it.
Where the hybrid runs out is the lot identifier. If your reconciliation pain comes from lots diverging across re-cataloguing, group splits and platform listings, no engine bolted to the side fixes that, because the problem is that nothing owns the lot. At that point the first release band applies.
Which should you choose, by operator size and stage?
Up to about 1,200 lots a year, standard terms, one jurisdiction: buy. AuctionFlex plus a bookkeeper. Spend the difference on the sale.
Between roughly 1,200 and 3,000 lots with mostly standard terms: still buy the back office, but if disputed charges or tax treatment are eating time, take the premium and tax engine at $26,000 to $45,000. It is the cheapest useful thing in this category and it does not disturb anything you already run.
Three thousand to 6,000 lots with negotiated terms on a quarter or more: the first release build at $55,000 to $120,000. Integrate one bidding platform in release one to prove the bidder resolution pattern, then add the second and third as discrete items at lower unit cost. Model one department properly rather than four thinly.
Two tax jurisdictions, advances or guarantees against property, or institutional consignors: the full platform at $150,000 to $350,000 is defensible. Expect the second jurisdiction to add substantially to the rule engine rather than a setting, and expect advances to turn settlement into a lending product with its own exposure reporting and unwind rules.
One preparation task applies whichever route you choose, and it is free. Write your commission, charge and tax rules down precisely, in your own time, before anyone quotes. In most houses that takes two to four weeks and it is the largest single saving available, because it is otherwise paid discovery. It also tells you something useful on its own: if the rules cannot be written down, they cannot be automated, by anybody, at any price.
If you want that decision made properly rather than quickly, Digital Heroes writes a product requirements document before any code exists, so the scope is fixed and priced rather than discovered later at a day rate. The document is yours whichever way you go.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- OECD research finds that digitalisation offers SMEs opportunities to improve performance, spur innovation, enhance productivity and compete more evenly with larger firms; it reports that increased use of online platforms produced significant multi-factor productivity gains in SME-heavy sectors such as hospitality and retail, while smaller firms lag in adoption due to skills, resource and financing gaps. Source: OECD (2021) →
- Retailers improving Core Web Vitals saw measurable gains: Vodafone improved LCP by 31% for 8% more sales, Lazada saw a 16.9% mobile conversion increase, and Cdiscount saw a 6% Black Friday revenue uplift. Source: web.dev (Google Chrome team) (2021) →
- Total US training expenditure rose 4.9% to $102.8 billion; learning management systems were used at 89% of organizations (90% of large, 97% of midsize, 84% of small companies), with average training at 40 hours per employee and $874 spent per learner. Source: Training Magazine (2025) →
- An earlier SHRM benchmarking report (reflecting fiscal year 2015, published 2016) established a widely cited baseline average cost-per-hire of $4,129, illustrating how recruiting costs have climbed over time (SHRM's separate 2025 Benchmarking Report shows $5,475 for nonexecutive roles). Note: the $5,475 figure is not on this linked page; it comes from SHRM's 2025 report. Source: SHRM (Society for Human Resource Management) (2016) →
Frequently asked questions
What does it cost to move off AuctionFlex if we build?
The commercial exit is straightforward. The work is in the data, and specifically in lot identifiers, because a decade of re-cataloguing, group splits and platform listings means the same physical object appears under several references.
Plan a partial migration rather than a perfect reconstruction: structured past results plus attached documents, typically $8,000 to $20,000 depending on how many systems the history lives across. Past results matter for estimates and provenance enquiries. Historical settlement arithmetic does not need to be reproducible in the new system, and trying to make it so is where migrations overrun.
What if a bidding platform changes its commission or its terms?
Treat platform economics and back office software as separate decisions, because they are. Your exposure to a platform commission change is a function of how much of your hammer comes through that audience, which you can measure per sale today.
What software affects is your ability to add or drop a platform cheaply. If bidder identity resolves into a record you own, adding a third audience or dropping one is an integration change rather than a disruption to vetting, paddle limits and outstanding balances. Budget $6,000 to $12,000 per platform, with the first costing more because it establishes the pattern.
How long does a build take before we settle a sale in it?
Twelve to 16 weeks for the first release covering consignment, premium and tax calculation, invoicing and settlement. The schedule risk is rarely engineering.
It is getting your own rules written down precisely, which takes two to four weeks because in most houses they exist as a mix of template agreements and one specialist's memory. Then settle one real sale in parallel with your existing spreadsheets before you trust the output, and expect that parallel sale to surface two or three rules nobody mentioned in discovery.
Is AuctionFlex genuinely enough, or is that just polite?
Genuinely enough for a defined shape of business: general line or estate sales, a standard commission structure, one tax jurisdiction, individual consignors. It handles that workflow properly and a build would arrive at the same place more slowly and more expensively.
Where it strains is verifiable rather than a matter of taste. Negotiated seller terms, guarantees and advances become notes and manual adjustments rather than modelled data, and multi jurisdiction tax with the resale right turns a percentage field into a rule engine. Test it against your own awkward lots rather than a demonstration set.
Can we build only the premium and tax engine and keep everything else?
Yes, and for a house happy with its back office it is the sensible first move. The engine runs $26,000 to $45,000 over six to eight weeks, sits between your existing system and your invoicing, and produces a stored breakdown showing which rule produced which number on which date.
The practical requirement is that your back office can accept a computed invoice line, or that invoicing can move to the new engine while everything else stays. Establish which in the first conversation, because it decides whether this is a clean insert or a partial replacement.
Why does a second tax jurisdiction cost so much?
Because it is a full rule set rather than a rate. Two jurisdictions means two tax models, two regulatory regimes, and cross border questions such as whether property was imported under temporary admission that neither model answers alone.
Expect it to add substantially to the rule engine work rather than a configuration flag, and treat any developer who describes it as a setting with caution. The same applies when evaluating a packaged product: ask it to compute a specific cross border lot rather than accepting that multi jurisdiction is supported.
How should buyer non payment be handled in the system?
As a defined unwind built at the same time as the settlement path, not as a manual correction someone remembers to make. Non payment reverses the settlement line and moves the lot to a re-offer or rescission state, and consignor payouts run as a batch with a hold rule for lots where the buyer has not cleared.
This is the detail that separates a settlement ledger from a settlement report. A report tells you what should have happened. A ledger survives the sale where three buyers do not pay and one lot goes back into the next catalogue.
Who owns the code if we hire a developer?
You should own the repository, the hosting accounts and the unrestricted right to hire anyone else, written down before kickoff. At Digital Heroes the code is yours from the first commit.
A saleroom that cannot change developer is a saleroom whose settlement engine belongs to somebody else, and settlement is where client money sits. If a developer hedges on this question, that is reason enough to end the conversation regardless of how good the demonstration was.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
How long does it take from first call to software my team can actually use?
Plan for four to six months: two to three weeks of discovery, two to four weeks of design, then a 10 to 16 week build with testing. In Digital Heroes delivery experience the schedule killer is not engineering speed but decision lag; a client who takes two weeks to approve wireframes adds two weeks to launch. Book a weekly 30-minute decision slot before kickoff and most of that risk disappears.
How do we get years of data out of our old system and into the new one?
Treat migration as a planned sub-project: a field-mapping document, at least one dry run on a copy of your data, then a cutover with the old system kept read-only for 30 days as a safety net. On Digital Heroes projects it consumes 10 to 15% of the budget when the old system has an export, and more when data must be pulled out screen by screen. Ask any vendor to walk you through their last migration before you sign.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
What happens if I stop paying for maintenance after launch?
Nothing breaks on day one, which is what makes it dangerous. Within 6 to 18 months, unpatched dependencies accumulate known vulnerabilities, an integrated API like Stripe ships a breaking change, and the first fix requires a developer to relearn a stale codebase at full price. Budget 15 to 20% of the build cost per year for upkeep; it is the difference between a $500 patch and a $15,000 emergency.
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 work out whether custom software will pay for itself?
Do the arithmetic on hours before anything else: if the system saves three staff eight hours a week at a $35 loaded hourly cost, that is about $43,700 a year against, say, a $70,000 build plus 15 to 20% annual maintenance, a payback around two years. Add revenue effects only if you can name them specifically, like faster quotes or fewer abandoned orders, not as vague growth. In our delivery experience the businesses that see payback inside 24 months are the ones automating a process they already measure.
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.
How many people should be working on my software project?
A typical $40,000 to $150,000 build runs on three to five people: a technical lead, one or two developers, a designer, and someone owning QA and project communication, often as overlapping part-time roles. More bodies do not make software arrive faster; past a point they slow it down with coordination overhead. The question that matters more than headcount is whether one named senior engineer is accountable for the outcome.
Does it matter which tech stack the agency wants to use?
Yes, but not in the way most buyers expect: the goal is boring, popular technology such as React, Node.js or Python, and PostgreSQL, because any future team can maintain it and hiring a replacement developer takes days, not months. The red flag is an agency-proprietary framework or an unusual language, which welds you to that one vendor no matter what your contract says about code ownership. A useful test: could you find three freelancers fluent in this stack within a week? If not, push back.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
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 Aria.
Senior Account Manager · Retail · Sydney · 2 posts on the site
Published · Last updated .
