01 / The problem
What was actually hard.
Portals are paid by listing volume, so nothing in their economics rewards removing a stale or duplicated listing. The result is a search experience where the buyer's real work is filtering out noise, and the honest agent is punished for competing against inflated inventory.
Contact is the second failure. Submitting an enquiry usually means handing a phone number to several brokers at once, which is why buyers stop enquiring. Keeping the conversation inside the platform changes both the buyer's experience and what the platform can moderate.
02 / What we built
The system.
- Verification as a first-class object
- A listing carries a verification with evidence attached and inspectable, rather than a self-declared badge — so 'verified' means something specific and reviewable.
- Structured location and property model
- City, locality, project, property and listing modelled separately, so the same physical unit relisted twice is detectable instead of appearing as two homes.
- In-app messaging with revocation
- Buyers and sellers talk inside the platform, and a buyer can revoke a conversation — so an enquiry is not a permanent handover of a phone number.
- Shortlists and saved searches
- The two things buyers actually do repeatedly over a months-long search, treated as core features rather than afterthoughts.
- Visit scheduling
- Requesting and tracking viewings against a listing, which is where a marketplace either becomes useful or gets abandoned for WhatsApp.
- Organisations and role-based access
- Agencies and developers as organisations with roles beneath them, so a brokerage manages its own inventory without seeing anyone else's.
- Project listings
- Developer projects modelled distinctly from resale units, because they are a different purchase with different questions.
03 / What carried over
Decisions worth reusing.
The parts of this build that we would apply again on a different problem in a different sector.
- Trust is a data model decision
- You cannot bolt verification onto a listing table. Evidence, reviewer and outcome have to be modelled from the start or 'verified' degrades into a badge.
- Deduplication needs structure
- Detecting the same unit listed twice depends on modelling locality and project properly. Free-text addresses make it effectively impossible.
- Protect the enquiry
- Keeping contact inside the platform is what makes moderation possible at all — and it is the feature buyers notice first.
04 / More work
Other builds.
Different sectors, the same delivery discipline.
Bits N Pixels
A software consultancy's site rebuilt as a platform — CMS, client portal, invoicing and multi-gateway payment links, with no CSS framework anywhere.
Encore Episode
A vertically-integrated event commerce platform — ticketing, gate control, cashless payments and vendor settlement in one system.
eSign Platform
An e-signature platform with envelopes, templates, a REST API and a tamper-evident certificate of completion behind every signed document.
Next step
Have something like this to build?
Start with a diagnostic. It is fixed-fee, time-boxed, and it will tell you honestly whether the thing is worth building — including when the answer is no.