Everything included in a BidWebStudio website
Every feature of a BidWebStudio website for online and hybrid auction platforms, and which of the three plans carries it.
Catalog pages built for lots, not blog posts
A sale catalog with filters by category, closing time and status, not a generic list of posts.
Why a catalog page is not a blog archive
A sale catalog needs to answer a different question than a blog archive: which lots are open, which are closing soonest, and which category a bidder actually came for. The catalog template is built with filters for category, closing time and status from day one, so a sale with five lots and a sale with five hundred lots both stay usable. Lot cards carry a photo, current status and a link to the full lot page, and the layout holds up whether you run one sale a month or several sale rooms at once.
One template, many sale types
The same catalog structure adapts to an estate sale, a farm equipment sale or a fine art sale, because the fields that change, such as condition notes, provenance or equipment hours, live on the lot page template rather than the catalog page itself. That means a revision to add a new spec field for one sale type does not touch the catalog layout everyone else depends on.
Available on:PaddleRostrumBlock
Pages that open instantly during a live sale
Custom-coded pages served from the edge, 90+ PageSpeed guaranteed, even under a closing-time traffic spike.
Why speed matters most in the last five minutes
Traffic to a catalog or lot page peaks in the minutes before a sale closes, exactly when a slow page costs a bidder their last look at a lot. Every page is custom coded, ships almost no JavaScript, and is served from Cloudflare's global edge, so the site holds up under that spike rather than slowing down when it matters most. Ninety-plus PageSpeed is a guarantee we hold ourselves to, not a target.
Available on:PaddleRostrumBlock
Paddle and bidder registration built into the site
A registration page that collects what your sale needs before a bidder ever reaches the floor or the feed.
What the registration page collects
A bidder registration page asks for contact details, payment on file where your process requires it, and any sale-specific terms a bidder needs to accept, then confirms a paddle number or bidder ID back to them. It is built as a real page on your site rather than a PDF attachment, so it works the same on a phone as it does on a desktop, and it can link straight into the bidding or payment platform you already use to finish the process.
One flow, reused per sale
The registration flow is a page template, not a one-off form, so a new sale reuses the same structure with updated terms rather than starting from scratch. Changes to the fields you collect, such as adding a buyer premium acknowledgment, are a standard revision.
Available on:PaddleRostrumBlock
Live sale status and countdown
A visible countdown and current-bid status on catalog and lot pages, so nobody is guessing when a lot closes.
Why a countdown belongs on the page itself
Bidders should never have to calculate a closing time from a listed date and a stated time zone. The catalog and lot page templates carry a visible countdown and a status label, such as open, closing soon or closed, so the state of a sale is obvious at a glance. The countdown updates the display only; the authoritative bid data and closing logic still live in your bidding platform, and the website reflects what that platform reports.
Available on:PaddleRostrumBlock
Settlement and results pages
A clean page for invoices, pickup terms and past results once a sale closes.
What happens once the hammer falls
A settlement page lays out what a winning bidder owes, the buyer premium if one applies, payment instructions and the pickup or shipping window, in one place rather than a follow-up email that can get missed. A results archive page keeps closed sales visible after the fact, which sellers use to gauge value and search engines use to index your sale history.
Built to reuse after every sale
The settlement and archive pages are templates that take a new sale's results as a normal update, so publishing results after Saturday's sale does not require a developer or a rebuild.
Available on:PaddleRostrumBlock
Search visibility for the sale types and areas you serve
Pages structured so search engines can tell what you sell, where, and to whom.
What actually gets a sale room found online
A search engine ranks a page for "farm equipment auction near me" or "estate sale auctioneer in [area]" when the page structure makes that clear: a dedicated page per sale type, a stated service area, and schema markup describing the business and its sales. That structure is built into every page from launch rather than bolted on later.
Available on:PaddleRostrumBlock
The AI Engine
AI agents that answer bidder questions and route consignment inquiries, without giving bidding or legal advice.
What the AI Engine handles
On Rostrum and above, an AI agent answers the questions bidders ask most, such as pickup windows, payment methods and how registration works, directly on the site. It can also take the first details of a consignment inquiry and route them to your team, so a seller reaching out at midnight is not waiting until morning for a reply. It is configured to hand off anything resembling bidding strategy, valuation or legal guidance to a person.
Billed at cost, not marked up
AI usage is billed monthly in arrears at what our providers charge us, on top of the flat monthly fee, so the cost tracks how much the agent is actually used rather than a flat guess.
Available on:Paddle (not included)RostrumBlock
The Content Engine
An expanded article program on Block, publishing three researched pieces a week instead of two.
Why more articles matter for a sale calendar
Block runs three researched articles a week instead of two, each 2,500 to 3,200 words and cited to real sources, which matters for an operation running frequent sales across several categories where there is simply more ground to cover: buyer premiums, condition grading, consignment processes and regional sale calendars all become their own articles rather than competing for the same two weekly slots.
Available on:Paddle (not included)Rostrum (not included)Block
Managed hosting and security
Cloudflare hosting with SSL, CDN, DDoS protection and unmetered bandwidth, included on every plan.
What is included and never billed separately
Every site runs on Cloudflare's global network with SSL, a content delivery network, DDoS protection and unmetered bandwidth, all inside the monthly fee. There is no hosting invoice, no SSL renewal fee and no bandwidth overage charge, including during the traffic spike a closing sale or a widely shared lot can bring.
Available on:PaddleRostrumBlock
Feature availability at a glance
| Feature | Paddle | Rostrum | Block |
|---|---|---|---|
| Catalog pages built for lots, not blog posts | |||
| Pages that open instantly during a live sale | |||
| Paddle and bidder registration built into the site | |||
| Live sale status and countdown | |||
| Settlement and results pages | |||
| Search visibility for the sale types and areas you serve | |||
| The AI Engine | |||
| The Content Engine | |||
| Managed hosting and security |
The paddle to settlement flow
Every plan is built around this sequence: a bidder registers, gets a paddle number, watches the sale, wins a lot, and is settled, and the website has a specific job to do at each step.
Registration
A bidder fills in the registration page: contact details, payment on file where your process requires it, and the terms for that sale.
The website owes: A fast, mobile-first registration page that confirms what was submitted, not a PDF nobody can finish on a phone.
Paddle number issued
Your platform confirms a paddle or bidder ID once registration is complete, and the site reflects that confirmation back.
The website owes: An on-screen confirmation the moment it happens, so a bidder is not left refreshing an inbox to know they are in.
Bidding
The bidder watches the catalog and lot pages as the sale runs, checking status, current bid and time remaining.
The website owes: An accurate live status and countdown on every lot, reflecting what your bidding platform reports in real time.
Winning bid
A lot closes and a winning bid is recorded by your bidding platform, with the buyer premium calculated against it.
The website owes: A lot page that updates to a closed, sold status clearly, with no ambiguity about whether a bid was the winner.
Invoice and settlement
The winning bidder needs to see exactly what they owe: hammer price, buyer premium, tax where it applies, and how to pay.
The website owes: A settlement page laying out the invoice, payment method and pickup or shipping window in one place, not a follow-up email.
Results and archive
Once settled, the sale becomes part of your public record, useful to sellers deciding whether to consign and to search engines indexing your history.
The website owes: A searchable results archive that updates automatically, without a manual rebuild after every sale.
Questions about features
What does the AI Engine do for an auction site?
On Rostrum and above, the AI Engine answers common bidder questions on the site, such as pickup windows or how registration works, and can route a consignment inquiry to your team. It is configured to hand off anything that resembles bidding advice, valuation or legal guidance to a person rather than answering it, because that is not something we or the AI Engine are positioned to give.
Is AI usage billed separately?
Yes. Rostrum is priced $267 a month plus AI usage, billed monthly in arrears at what our providers charge us. There is no markup and no flat AI fee hidden in the base price.
What does BidWebStudio actually build?
A website for your auction operation: a home page listing current and upcoming sales, a catalog page for lots, individual lot pages, a paddle or bidder registration page, terms of sale, and a settlement or results page once a sale closes. We do not run the bidding itself; the site presents your sales and links or embeds the bidding platform, CRM or payment processor you already use.
How long until my site is live?
7 days on Paddle, 10 on Rostrum while the AI agents are trained, and 15 on Block with the content engine running. The clock starts at the onboarding call, not at purchase, so the sooner the onboarding form is in, the sooner the site is live.
Can the site carry more than one sale at a time?
Yes. The catalog structure is built to list several active or upcoming sales on the home page, each linking to its own set of lots, closing times and terms, which matters for an operation running more than one sale room or event.
See these features on your own sale
A live walk-through of the full page set, built for your kind of sale.
Book a demo