Why this page exists
A portfolio shows what a studio made once. This shows what it sustains.
Most web studios present a portfolio: finished projects, handed over, no longer their concern. Whether a site still works, still loads quickly, still converts — none of that is visible from a case study written the week it launched. We can show something harder to assemble and much harder to fake: an operating estate of property platforms and development showrooms that we built, host, update and answer for. Nothing on this page is a mock-up or a rendering. It is what we run.
Running it is the part that matters commercially, and it is worth being precise about why. Daily operation puts us on the receiving end of every decision we make. A plan table that confuses a buyer does not generate a polite note from a client six months later — it generates silence in our own enquiry inbox, this week. A gallery that loads slowly on a phone shows up in our own bounce figures. A payment computation a buyer does not trust produces a question we personally have to answer. The feedback is immediate, unflattering and ours to fix.
That is a materially different position from a studio that delivers and departs. The components a client engagement starts from — plan viewers, unit comparison tables, payment computations, gallery systems, qualified enquiry paths — were not designed in the abstract and signed off by a committee. They reached their current form because we watched them fail on real property traffic and kept correcting them. By the time any of it reaches a client project, the expensive mistakes have already been made at our own expense.
It also keeps the practice current in a way that reading cannot. Hosting, security patching, performance, Core Web Vitals, structured data, and how AI assistants actually cite a property page — these shift constantly, and the only reliable way to know where they stand is to be responsible for a live estate when they move. We are not describing best practice from a distance. We are maintaining it on our own domains before charging anyone for it.
One codebase
Every platform and showroom hand-coded in PHP, HTML, CSS and JavaScript, sharing one modular component library
Structured data
Unit plans, floor plates, payment terms and availability held as editable data rather than baked into pages
Proven, not new
Components corrected against live property traffic before any of them reach a client project
Repeatable
A new showroom starts from tested parts, which is why a first working version can be live within a day
Operated daily
We host, patch, monitor and update this estate ourselves — the same care a client engagement receives
Accountable
Every entry on this page opens a live site. Nothing here is work that does not exist
