Booking intake
A public booking page per photographer collects the property, the services and the contact details, and turns the request into a real job record.

Platform
RELMX connects booking, scheduling, RAW upload, editing, revisions, delivery, payments and editor payouts into one workflow — so a job carries its own history from the first request to the final payout.
The problem
Most real estate photographers do not lose their evenings to photography. They lose them to the coordination around it.
A single listing can touch a booking message, a calendar, a folder of brackets, an editor, a revision thread, a delivery link, an invoice and a payout note. Each of those steps is simple. The cost is that none of them know about each other, so the information gets re-entered by hand at every hand-off — and every re-entry is a place where the address, the brief or the count can go wrong.
That overhead is fixed per job, which is why it hurts most when volume grows. Ten shoots a week means ten of everything above. Software only helps if it removes hand-offs rather than adding another tab.
The connected workflow
Every step below writes to the same project. Nothing has to be re-typed to move to the next stage.
A booking request comes in from your public photographer page with the property address, the services wanted and the client's contact details — instead of a text message you have to re-type later.
The request lands on a calendar you control, with blocked days and availability respected, so the date on the job is the date the job actually happens.
Nothing changes about your camera work. The job already exists in the system with the address, the client and the ordered services attached to it.
Bracket sets and video source clips upload straight to the project — resumable, built for large files, and grouped by the property rather than dumped in a dated folder.
Work is assigned to an editor with the brief and style notes attached. The editor never has to ask which folder, which listing, or which client this belongs to.
Finals come back into the same project. Revision notes are written against the job, not scattered across email, so the history of what was asked and what changed stays in one place.
You review the set before the client ever sees it, and send it back for another pass if it is not on style.
Approved photos and video go out as a delivery the client can view and download, with marketing extras attached to the same property.
Client payment and editor payout are recorded against the same job, so what you charged and what the work cost sit next to each other instead of in two spreadsheets.
What's inside
These are the parts of the platform photographers use today. Deeper feature pages cover the four that carry the most weight.
A public booking page per photographer collects the property, the services and the contact details, and turns the request into a real job record.
A shoot calendar with blocked time and day availability, so bookings land on days you can actually work.
Chunked, resumable uploads for full bracket sets and video source footage, sized for the reality of a multi-gigabyte listing.
Assignment, style notes, revision rounds and delivery approval — the production side of the business, not just a hand-off folder.
Delivered galleries with downloads and marketing extras attached to the property, instead of a bare cloud-drive link.
Card payment through Stripe on the client side and editor payout tracking on the production side, both tied to the job.
Every shoot is filed under the property and the client, so past media for an address stays findable long after the listing sells.
Project-level messaging so questions about a specific job stay attached to that job.
Photographers, business clients, editors and admins each see their own surface, enforced server-side rather than hidden in the UI.
Editing, connected
Editing inside RELMX is not a detached vendor relationship. It runs against the same job the booking created.
When editing sits outside your operations, the file becomes the only thing that travels — and the brief, the client, the address, the revision history and the cost stay behind. Keeping production connected means an editor opens a job that already knows what it is, and the finished set returns to the project the client is waiting on.
RELMX is built to be the system a real estate media company runs on end to end. The workflow above — booking, scheduling, upload, editing, revisions, approval, delivery, payments and payout tracking — is what the platform does today. We are direct about the difference between what is live and what is on the roadmap, because a workflow claim you cannot rely on is worse than no claim at all.
FAQ
It is the software a photographer or media company runs the business on: taking bookings, scheduling shoots, moving RAW files to editors, tracking revisions, delivering finished media to the client, and keeping payments, clients and properties connected to the job. Standalone tools each solve one slice; the point of a platform is that the job carries its own history from booking through payout.
No. Editing is the busiest part of the platform and the easiest place to start, but RELMX is built to run the surrounding operation too — booking pages, scheduling, uploads, editor assignment, revisions, client delivery, payments and payout tracking. You can use the editing service on its own and add the operational side when you want it.
No. Most photographers start by sending one job's brackets through the platform, keep their existing camera and shooting workflow untouched, and expand into booking, scheduling and client delivery once the editing side is running the way they want.
Yes. Roles are separated: photographers and business clients see their own projects, editors see the work assigned to them, and admins see the operational picture. Everyone works against the same project record instead of a shared drive folder and an email thread.
Clients can be added to a project and receive delivered galleries, and delivery links can be shared without pulling anyone into a raw file-storage tool.
Related
Turn a booking request into a real job record with the address and services attached.
ReadAssignment, style notes, revisions, QC and payout tracking for a production team.
ReadHDR production runs against the job instead of a detached folder.
ReadCreate a workspace, send one job through, and see what it feels like when the booking, the brackets, the edit and the delivery all know about each other.