Skip to content
RoomAMD

RoomAMD Marketplace

A two-sided booking platform, built end to end.

Listings, request-to-book, itemised pricing, cancellation and refund rules, split payouts, messaging and an admin console with tiered authority. Built first for practitioners booking clinical space by the hour, day or month, and configurable for other sectors.

Built by RoomAMDOur own product

Build something like this

Live demo 01

Pick a time. Watch the total build.

Choose how long, which day and which extras. The rate, cleaning fee, tax and service fee are itemised as you go, by the same rules that set the charge. Requesting places a hold on the card and nothing more until the host accepts.

Interactive demo on invented data. Nothing here connects to a live system. These are the marketplace's own screens and rules.

The problem

A marketplace is won or lost in the edge cases

The money has to split correctly
One booking is several amounts for several parties: the rate, add-ons, tax, the host's share and the platform fee. A refund has to unwind every one of them, to the cent.
Every listing has its own rules
Hourly or monthly rates, cleaning fees, cancellation terms, the documents a host needs to see. Rules written into the code break on the second host.
Disputes need a record
When a booking goes wrong, someone has to see who agreed to what, who viewed which document, and who refunded whom, with a limit on what each staff member can do.

Live demo 02

Cancel earlier or later. See what comes back.

Each listing carries one of three cancellation tiers. Move the moment of cancellation and the refund, the host's share and the fees follow the tier's rules, with the reason stated in a sentence.

Interactive demo on invented data. Nothing here connects to a live system. The refund rules and their wording are the marketplace's own.

Live demo 03

A booking of months, charged and paid out a month at a time.

The first month is charged when the host accepts. Each later month is charged shortly before it starts, and the host's share of a month is released after it ends. Cancel part-way and the remaining months stop.

Interactive demo on invented data. Nothing here connects to a live system. These are the marketplace's own screens and rules.

Live demo 04

What was booked, what was kept, what was paid.

Hosts see what each booking brought in beside what they receive after the platform fee, with a payout history. Hosts who hold the platform's host badge pay a lower fee, and every figure follows.

Interactive demo on invented data. Nothing here connects to a live system. These are the marketplace's own screens and rules.

What is built

Everything a booking passes through.

Listings and search
Hosts publish spaces through a four-step wizard and a sectioned editor. Visitors search by place, date and duration on a list or a map, and the exact address is shown only after a booking is confirmed.
Pricing to the cent
Rates by the hour, half day, day, week or month, with add-ons, cleaning fee, tax and service fee itemised. The preview and the charge run on the same rules.
Request to book
A request places a hold on the card. The charge happens only when the host accepts, and the hold is released if the host declines or the request expires.
Split payouts
The platform fee comes off each booking and the host's share is released after a hold period. A refund claws back in proportion.
Cancellation and refunds
Three cancellation tiers with a free-cancellation grace period. One set of rules drives the policy page, the listing editor and the refund itself.
Long bookings in instalments
Month-by-month charging and payout for multi-month bookings, with later months stopping cleanly on a cancellation. Developed and tested; switched off by default.
Credential exchange
Hosts set the documents a booking needs. Practitioners share them per booking, every view is watermarked and logged, and expiry reminders run on a schedule.
Agreements on record
Click-to-acknowledge agreements tied to the exact version accepted, with a content hash, a timestamp and a PDF record. A new version asks for acknowledgement again.
Listing writer
An optional AI writer drafts three titles or descriptions from the listing's facts and one note from the host, only when the host asks. The host picks one and edits it.
Messaging
Conversations with an automatic card for each booking step, saved replies with merge fields, and sends scheduled against the booking's own dates.
Admin console
Queues for disputes, refund requests, expiring documents and account deletions, user and listing management, and an audit log of every action.
Tiered authority
Four staff levels. Fee-returning refunds, forced cancellations, bans, platform settings and revenue figures each belong to a level, checked on every screen and every action.
Scheduled work
Background jobs decline stale requests, send reminders, charge instalments, release payouts after the hold and flag expiring insurance.
Security foundations
Row-level security on every table, private file storage with signed links, and an append-only audit log.
English and French
A bilingual interface, with language and time zone chosen per account.

Live demo 05

Three drafts, from the listing's own facts.

An optional AI writer drafts a title or a description when the host asks: three options from the listing's facts and one note in the host's own words, told never to invent amenities, prices or medical claims. The host picks one and edits it. Here the drafts for this listing are written in advance, and nothing is sent anywhere.

Interactive demo on invented data. Nothing here connects to a live system. These are the marketplace's own screens and rules.

Live demo 06

A refund in three guided steps, with fee refunds kept for senior staff.

The assistant offers the policy amount first, with a reply ready to send. Any staff member can refund up to the amount that costs the platform nothing. Returning the platform's own fees, or cancelling a booking outright, goes to a senior admin.

Interactive demo on invented data. Nothing here connects to a live system. These are the marketplace's own screens and rules.

Live demo 07

One console. Each level sees what it is allowed to.

Queues, volumes and recent audit events on one dashboard. Switch the staff level and revenue figures, tax and platform settings appear and disappear, exactly as the permission rules decide.

Interactive demo on invented data. Nothing here connects to a live system. These are the marketplace's own screens and rules.

Where it fits

Built for clinical space. Configurable for others.

Rates, fees, cancellation tiers, required documents and staff levels are settings, not code. A build for another sector is a configuration and custom software engagement.

Clinical and studio space
Rooms booked by the hour, day or month, with the documents a host needs before saying yes. This is the build shown on this page.
Equipment and asset hire
The same card holds, cancellation tiers and payouts would apply to things instead of rooms. Not built today: it would be a configured build.
Shared facilities
Labs, kitchens, workshops and bays offered by one organisation to many, with a platform fee and an admin console. Not built today: it would be a configured build.

What this is, and isn't

RoomAMD built this marketplace end to end and tested it on demonstration data. Payments run through a payment processor, which holds and moves the money; the platform decides when to hold, charge, refund and pay out. The platform does not check credentials itself: it structures the exchange between host and practitioner and keeps the record.

See the marketplace with your own listings in mind.

We'll walk a booking from search to payout with you, and what a build for your sector would need.