How it works
Seven steps, in the order they happen.
How Exclusivo works, step by step: recording a property and its owners, generating and signing the exclusive mandate, preparing and publishing a property experience, sharing it, and receiving the enquiries it produces.
Property
It starts as a property, not a listing.
Record the property and the people who legally own it: one of them, or four of them, with their roles. Everything that follows hangs off that relationship, which is why the platform asks for it first and refuses to publish without it.
properties · property_partiesOwner
The owner gets their own way in.
Invite an owner and they see their property, and only their property. No account sprawl, no CRM vocabulary, nothing belonging to anyone else. The relationship is the product.
owner portal · property owner invitationsMandate
The agreement is generated, not assembled.
The mandate is produced from the property's own terms as a deterministic document. The same terms always render the same bytes, and the document carries a hash it cannot disagree with.
mandates · mandate_versions · document hashSign
Signed, with the evidence kept.
Owners sign electronically from a secure link, with no account required. What is recorded is the signature, the consent given, and the exact document it was given against. If the document changes, the signature no longer matches it, and the platform says so.
signing sessions · signature evidenceExperience
The property becomes an experience.
Photographs are validated from their bytes, originals kept private and never altered, public copies stripped of the location and device data a camera writes into them. Then it publishes, but only once every owner has approved what is about to go live.
media pipeline · experiences · /e/{slug}Close
And the enquiry comes back to you.
A visitor enquires from the property page and it arrives as a lead the agency owns, carrying the link it came through. Assign it, work it, close it, reopen it. Nothing is lost and nothing about it can be quietly rewritten.
leads · lead_events · attribution
What is built, and what is not
Planned capabilities are labelled. Nothing on this site describes something the product does not do.
Exclusive mandates
A mandate is generated as a deterministic document, hashed, and signed electronically by the owners recorded against the property, for a property to sell or to let. Rental terms of their own are next.
Property experiences
A published property gets its own public page, built from a frozen copy of exactly what the owners approved.
Smart Links and QR codes
One canonical share link per property experience: it can expire, it can be revoked, and it records how the enquiry it produced arrived. Every link also renders as a QR code for a window card, a brochure or a board.
Lead capture
Enquiries from a property page arrive as leads owned by the agency, attributed to the link the visitor arrived through, and worked through a status pipeline.
Calls and viewings that update the recordPlanned
Designed so that a call with a seller or a buyer, or a viewing and an appraisal in person, recorded only with everyone's permission and transcribed, lands on the property and the contact as notes, feedback and next actions. Next in the product.
Works alongside your CRMPlanned
Exclusivo runs the mandate; your CRM keeps the relationship. Designed to sit above it: sign in with your CRM, property and contact sync, mandate status pushed as it changes, a webhook for every event, an embed for your website and an API over the canonical objects, so an agency plugs in rather than logs in. The first connectors are next.
Immersive walkthroughsPlanned
A walk through a property on a phone becomes an immersive walkthrough: published on the property experience, shared through the Smart Link, and exported for the other tools an agent already uses. Today an agent supplies the media and the page presents it.