The short answer
Gavel Platform is all-in-one auction software and marketing infrastructure with an AI Employee built into the operating system. It connects the auction company's private back office to its branded public website and bidding experience, so leads, projects, listings, bidders, bids, awards, reports, invoices, and settlement do not become disconnected islands.
What Is the Gavel Platform?
Most people see an auction company at its most dramatic moment: the auctioneer, the bidder, the countdown, the winning bid. But sale day is the visible edge of a much larger operation. Long before the first bid, someone has to answer the seller, understand the asset, research the property, prepare an appraisal, secure an agreement, coordinate staff, collect documents, build the catalog, photograph the sale, write the marketing, publish the auction, register bidders, explain the terms, and make sure the company is ready.
After the gavel falls, the work continues through awards, buyer premiums, invoices, settlement, results, seller reporting, records, and follow-up. Auction companies have traditionally managed that chain with a mixture of bidding software, spreadsheets, shared drives, email, paper checklists, website vendors, separate CRMs, and the institutional memory of a few experienced people.
Gavel Platform replaces that patchwork with one connected operating system. It was developed by Cloud Radix alongside the auction professionals at Metzger Property Services, a multigenerational Indiana auction, real-estate, appraisal, and property-management company. Metzger supplied real operating knowledge. Cloud Radix turned that knowledge into software, public infrastructure, controlled automation, and a working AI Employee.
Why Auction Software Breaks at the Handoffs
The central problem in auction technology is not that every individual tool is bad. The problem is that the important context falls through the gaps between them. A seller conversation lives in email. The appraisal notes live in a document. The photos live in a folder. The auction record lives in a bidding platform. The marketing company copies pieces onto the website. Settlement starts again in a spreadsheet.
The seller repeats the same information
Intake, appraisal, contracts, cataloging, and marketing each rebuild a version of the same story.
Marketing drifts from operations
A changed date, tract, reserve, inspection, or term can be correct internally and stale publicly.
Bidder support lacks context
The person answering a question may not see registration, approval, watchlist, bid, or auction-status history together.
Settlement begins with reconciliation
When the bidding platform, clerking record, invoice workflow, and buyer data are separate, people must prove the result again.
The product is the handoff
Two Experiences, One Auction Operating System
Gavel is intentionally split into two experiences because auction staff and the public should not use the same interface. They do, however, need to work from the same underlying truth.
Gavel Back Office
The private control plane for leads, contacts, projects, appraisals, contracts, tasks, calendars, documents, auction setup, lots and tracts, bidder review, live monitoring, reports, awards, invoices, settlement, and operational history.
The platform controls.
Branded Public Experience
The auction company's website, service and authority content, searchable auction catalog, bidder account, registration flow, live bidding board, lot pages, results, inquiry forms, reviews, and education—under the auction company's own brand.
The website surfaces.
One shared database is the source of truth. Staff do not have to re-enter an auction into a disconnected marketing site, and the website does not invent operational facts. Approved records can move outward to the public experience; bidder activity and inquiries can move inward to the right controlled workflow.
The Complete Auction Lifecycle Gavel Connects
Stage 01
Win the seller
Capture inquiries, connect contacts, qualify the opportunity, schedule discovery, preserve notes and attachments, and route the lead to the right person.
Stage 02
Build the project
Coordinate appraisals, contracts, property research, documents, staff assignments, dependencies, and readiness milestones before marketing begins.
Stage 03
Go to market
Turn approved source data into auction pages, catalogs, photos, maps, terms, advertising drafts, email, social content, and a campaign schedule.
Stage 04
Run the auction
Register and approve bidders, open bidding, protect confidential maximums, resolve standings, monitor activity, handle soft closes, and control release.
Stage 05
Settle the sale
Freeze awards, calculate buyer premiums, prepare clerking reports and invoices, track settlement status, release results, and preserve the record.
Stage 06
Improve the next one
Carry forward institutional memory, cycle-time evidence, bidder and seller history, reusable content, and the lessons that make every future sale stronger.
This lifecycle is what separates an auction operating system from a bidding vendor. Bidding is mission-critical, but it is one part of the company. Gavel is designed around the business that earns the seller, prepares the sale, serves the bidder, produces the result, and builds the next opportunity.
Multi-Parcel Maximum Proxy Bidding: The Hard Problem Inside Gavel
A normal timed lot has one target. The highest valid bidder leads that lot. A multi-parcel real-estate auction is mathematically different. One bidder may want tract 1. Another may want tracts 1 and 2 together. A third may bid on the whole farm. The platform has to find the compatible set of bids that produces the strongest result without awarding the same land twice.
Gavel's server-authoritative multi-parcel engine evaluates individual tracts, preset combinations, bidder-created combinations, and whole-property bids as one changing board. It resolves the highest-yielding compatible scenario after every accepted bid, uses deterministic tie handling, and keeps the authoritative money logic on the server instead of trusting the browser.
The platform also supports confidential maximum proxy bidding across that board. A bidder can authorize a ceiling rather than manually chasing every movement. Gavel raises the effective standing only as much as required to remain ahead, up to the bidder's maximum, while re-solving the combination landscape when competing bids change what can win together.
Differentiated—without an inflated world-first claim
- Confidential ceilings are not exposed to other bidders.
- A bidder's maximum is authorization, not an immediate jump to that amount.
- The current leader does not bid against itself; another valid challenge is required to move the effective price.
- Every accepted bid is serialized under a server-side auction lock before standings are recalculated.
- The public board receives safe effective standings rather than private bidder identity or hidden ceiling data.
Timed Online Lots Without the Patchwork
The same platform also supports traditional timed online auctions for estates, personal property, equipment, consignments, and other catalog sales. Each lot can carry its own media, order, description, terms, opening amount, increment, reserve, buyer premium, close time, and soft-close behavior.
Straight and hidden maximum bids
Per-lot soft close and staggered endings
Reserve-aware sold or passed outcomes
Live updates with polling self-heal
Masked public bid history
Watchlists and bidder account context
Staff monitoring and intervention controls
Awards, buyer premiums, and results
Invoice and settlement handoff
The operational advantage is continuity. When a lot closes, the award is not stranded in a vendor export. It is already connected to the approved bidder, auction record, premium calculation, reporting workflow, invoice preparation, and settlement state.
The Gavel AI Employee Works Inside the Platform
An ordinary chatbot waits for a question and returns text. Gavel's AI Employee is designed to work with the same structured records, approved tools, operating policies, and handoffs the auction company uses. The AI Employee is not the database and does not replace the auctioneer. It is the intelligent operating layer that helps the team move the work.
Intake and discovery
Organize inquiry details, summarize conversations, identify missing facts, suggest the next action, and prepare a useful staff briefing.
Appraisal and project preparation
Help structure research, attachments, checklists, milestones, notes, and communications without pretending to replace licensed judgment.
Listing and marketing production
Draft auction descriptions, advertising variations, email and social copy, and website content from the approved source record.
Operations and follow-through
Surface blocked tasks, overdue work, bidder or seller communication needs, deployment issues, and exception queues.
Reporting and institutional memory
Prepare summaries and reports, retain standing rules, and carry lessons from one auction into the next.
Website and platform stewardship
Support content, search visibility, quality checks, release verification, and the ongoing improvement of the connected software.
Human authority is part of the product
Built With Metzger Industry Expertise—Not From a Generic SaaS Checklist
Auction software can look complete in a feature list and still fail inside a real company. That is why the collaboration with Metzger Property Services matters. The platform was shaped around actual auction lanes, seller conversations, staff roles, appraisal work, readiness states, parcel research, marketing dependencies, bidder behavior, close-day pressure, and post-sale realities.
Metzger's public website is not a decorative shell over someone else's marketplace. It is the branded public surface of the same operating architecture: auction discovery, service inquiries, searchable content, team authority, bidder education, registration, auction detail, live participation, and results. The Gavel back office supplies the controlled record and staff workflow behind it.
That partnership produced a platform Cloud Radix can now adapt for other auction companies without pretending every company operates the same way. The reusable product is the secure foundation, auction engines, workflow model, AI Employee architecture, and deployment method. Discovery determines the company-specific policies, roles, content, integrations, auction formats, data migration, and approval gates.
What Another Auction Company Gets
Gavel is not sold as a login to a generic screen with your logo swapped into the corner. A serious deployment begins by mapping how your company wins sellers, evaluates assets, prepares sales, markets auctions, registers bidders, runs each auction format, handles exceptions, settles, communicates, and measures success.
- Discovery and workflow map. We document roles, approval authority, auction types, policies, data, systems, pain points, and the handoffs that must not fail.
- Branded public platform. Your domain, brand, service authority, auction catalog, bidder experience, inquiries, content, and demo or seller-conversion paths.
- Configured back office. Contacts, leads, projects, templates, tasks, auction setup, staff controls, reports, documents, and integrations shaped around the company.
- Auction engines. The appropriate multi-parcel, timed-lot, live-support, or phased format plan—with load, close, and exception testing proportional to the money at risk.
- AI Employee deployment. A named AI Employee with scoped access, memory, skills, approval boundaries, proof logs, monitoring, and a scorecard tied to actual business outcomes.
- Training and release gates. Staff rehearsal, legal and policy sign-off, account and notification testing, backup and recovery planning, and a supervised first sale.
Software readiness and first-sale readiness are different
What We Show in a Gavel Platform Demo
A Gavel demo is not a slide deck full of future promises. We walk through the connected product and focus on the parts that matter to your auction company:
- The seller journey from inquiry, contact history, and discovery into an active project
- Appraisal, contract, task, document, readiness, and marketing workflows
- The branded public website, auction catalog, account, registration, and bidder experience
- Multi-parcel bidding across tracts, combinations, and the whole property
- Confidential maximum proxy bidding and how the board re-solves
- Timed lots, hidden max bids, reserves, soft closes, results, and watchlists
- Staff monitoring, awards, reports, invoices, communications, and settlement handoff
- Where the AI Employee works, where humans approve, and how access is governed
- A practical deployment path for your auction formats, team, brand, and current data
See the whole auction company—not only the bid button.
Tell us what you sell, how you run auctions today, and where the handoffs slow you down. We will tailor the walkthrough to your operation.
Schedule a Gavel Platform DemoFrequently Asked Questions
Q1.What is the Gavel Platform?
Gavel is an all-in-one auction software, marketing, and AI Employee platform. It connects seller intake, contacts, projects, appraisals, contracts, tasks, marketing, a branded public website, bidder accounts, multi-parcel and timed online bidding, awards, reporting, invoices, and settlement in one operating system.
Q2.Is Gavel real software or a product concept?
It is deployed software. Cloud Radix reviewed the current Gavel operations repository and the connected Metzger public-auction repository for this article. The multi-parcel and timed-lot engines, bidder workflows, staff controls, awards, reporting, invoicing, settlement, notifications, monitoring, and public website are implemented. A new auction-company deployment still requires discovery, configuration, data migration, training, and release gates.
Q3.Does Gavel support multi-parcel real-estate auctions?
Yes. Bidders can compete on individual tracts, combinations, or the whole property. The server-authoritative engine continually calculates the highest-yielding compatible scenario and supports confidential maximum proxy ceilings across the active board.
Q4.Does Gavel support timed online personal-property auctions?
Yes. Timed lots support straight bids, hidden maximum bids, configurable increments, reserves, buyer premiums, per-lot soft closes, staggered endings, automatic sold-or-passed outcomes, results, and settlement handoff.
Q5.What does the Gavel AI Employee do?
The AI Employee works inside the operating system. It can help organize intake, prepare discovery and appraisal work, draft listing and advertising copy, surface missing information and next actions, prepare communications and reports, maintain the public website, and preserve operational context. Authorized humans retain control over terms, publication, bidder approval, financial outcomes, legal commitments, and other consequential actions.
Q6.Can Gavel run on an auction company's own domain and brand?
Yes. The product is designed around the auction company's brand, domain, content, bidder relationships, and operating policies. Gavel is not intended to make every auction house look identical; it provides a connected foundation that is configured around how the company sells.
Q7.Is Gavel claiming to be the first multi-parcel platform with max proxy bids?
No public world-first claim is being made without broader independent and patent research. The capability is meaningfully differentiated: BidWrangler's current multi-par support documentation explicitly says max bids are unavailable for multi-par auctions, while Gavel implements combination-aware confidential proxy ceilings. That is strong evidence of an unusual capability, not proof that no one anywhere has ever built it.
Sources and Product Verification
This article was prepared after pulling and reviewing the current Gavel operations and Metzger public-auction repositories on July 19, 2026. Product statements were checked against the implemented application routes, auction logic, database migrations, tests, workers, and current deployment documentation.
The verification run completed with 153 of 153 Gavel Platform tests passing and 37 of 37 Metzger public-platform tests passing. The Cloud Radix article integration also passed its 32-test suite, TypeScript, static schema validation, and a 381-route production build.
- Gavel Platform product page
- Metzger Auction and Gavel case study
- BidWrangler: Creating and Managing Multi-Par Real Estate Auctions
Capability language describes the current shared product foundation. Availability in a specific customer deployment depends on discovery, configuration, integrations, policies, training, legal review, and release approval.
