Xpillar Client Property Site
The public face of the Xpillar ecosystem: a true-listing property marketplace for the Malaysian market — industrial, commercial, residential, and agricultural — where every property appears exactly once, with an owner-verified section, agent directory, and buying guides.
Case study
Property ecosystem — web application · 2025
The starting point
The problem this system was built to solve.
Xpillar Sdn Bhd positions itself as a trusted partner in industrial real estate. Its public marketplace covers factories, industrial land, commercial, residential, and agricultural property across Malaysia — searchable by sale or rent, property type, and state.
The founding conviction is what Xpillar calls a true listing. On typical Malaysian property portals the same land or factory is advertised by five different agents at five different prices, and a consumer has no way to tell which version is real or current. Xpillar’s model is one property, one listing: ownership is verified, the canonical listing is the only one consumers ever see, and agent collaboration happens behind the scenes instead of as duplicate adverts.
Who uses it
The people the system serves.
Property seekers
Search factories, land, and premises by sale/rent, type, and state — and see each property exactly once, at one authoritative price.
Owners
Verify their property and publish through the owner-verified channel — “direct from owners” is a first-class section of the site.
Members
Save favourites, manage their profile, and submit proposals through an account area.
Agents
Appear in the public directory with their profile; their transaction tooling lives in the agent portal (its own case study).
The workflow
How work moves through it.
- 1
A seeker searches by sale/rent, property type (residential, commercial, industrial, agricultural), sub-type, and state.
- 2
The owner-verified section surfaces listings published directly from verified owners.
- 3
Each property resolves to ONE canonical listing — price, size, location, and photos — however many agents are involved behind the scenes.
- 4
Interested buyers contact the listing agent or browse the agent directory; members save favourites and submit proposals.
- 5
Property news and buying guides (e.g. what to check before renting a warehouse) keep the platform useful between transactions.
What we designed
Structure before screens.
- A search-first marketplace UX shaped around how Malaysian property is actually segmented — down to tender and “price on request” listings for large industrial land.
- The true-listing information architecture: one property, one page, one price — no duplicate cards competing for the same land.
- An owner-verified channel that makes “direct from owner” a visible, trustworthy category rather than a claim in a description.
What we developed
The engineering behind it.
- The public marketplace: search and filtering across categories and states, listing pages, agent directory, and property news.
- Member accounts with favourites, profiles, and proposal submission.
- The same backend that powers the agent portal, admin portal, and mobile app — a listing published once is correct on all four surfaces.
Key modules
The thought process
True listings — why one property means one listing
Malaysian property portals monetise volume, so the same factory can be advertised by every agent who has ever touched it — different photos, different prices, sometimes different sizes. The consumer experience is corrosive: you cannot tell which advert is current, which agent actually holds the mandate, or whether the “three results” are one property or three. For sellers it is worse — their asset looks stale and over-shopped.
Xpillar inverts that. A property enters the platform once, through owner verification, and becomes a single canonical listing. Price, size, and status live in one place, so a change by the mandated agent is instantly the truth everywhere — client site, app, and portals. Duplicate adverts are not filtered out after the fact; the data model simply has nowhere to put them.
Agent cooperation still happens — it just moves behind the scenes. Instead of re-advertising someone else’s property, an agent finds it in the agent portal’s co-share pool and requests to co-broke, with the fee split formalised through a co-agency agreement. The consumer never sees that machinery: they see one property, one price, one page. That is the trade Xpillar makes — less advert volume, more trust — and every surface of the ecosystem is built to protect it.
Inside the system
Screens from the shipped build.
Shown in the order a user actually moves through the system. Published with the client’s agreement — client data comes first, and only approved screens appear here. Read more about how we protect data in our privacy policy.






Technical constraints
What shaped the build.
The true-listing promise had to survive real marketplace pressure — the data model and workflows treat a duplicate listing as an error, not a growth metric.
Industrial property sells differently from condos: tenders, “price on request”, acreage, and zoning needed first-class treatment in search and on listing pages.
Four surfaces share one backend, so public content had to stay cleanly separated from agent and operator data.
Where it landed
The outcome, stated plainly.
We report what the system does in operation — not metrics we can’t verify.
- Consumers search a marketplace where each property appears exactly once, with owner-verified listings clearly marked.
- Owners have a verified channel to market directly; agents get a public profile and directory presence.
- The client site, agent portal, admin portal, and mobile app all read from the same source of truth, so a listing is never out of step across surfaces.
In the client’s words
“When we started Xpillar we were asking for a lot — a public property site, a portal for our agents, an admin system for our own team, and a mobile app, all working off the same data. Noctverse never made it feel like four separate projects. They took time to understand how listings, claims, and documents actually move in our business, and kept every surface consistent as the platform grew. What we appreciate most is that they’re not overly calculative: when priorities shifted they worked with us on what to build first instead of pushing everything at once, and they suggested practical workflows that will support our growth in the long run.”
Norman Soo
Director · XPillar
Services behind this build
Project enquiry
Running a similar operation?
Tell us how your workflow runs today — who is involved, what gets approved, where the delays are. We’ll map what should be built, and give you a concrete plan before any code is written.