SKNAT

A single product surface for discovery and operations — so agents aren’t stuck in one tool while buyers live in another.

SKNAT is a Thai real-estate platform built so buyers can explore properties with confidence while sellers and admins run the business from the same system.

The public side feels like a polished marketplace: search, map browsing, favorites, and compare. The private side covers inventory, inquiries, and sales workflows — without forcing a separate legacy admin forever.

Too many property products look great on the landing page and fall apart the moment an agent needs to update a listing or an admin needs to see what happened to a lead.

SKNAT’s bet was simple: one coherent product loop. If the buyer experience and the ops experience share models and UI language, the whole company moves faster.

I worked across the stack — from the public browsing experience to role-based portals and API routes that keep listings, members, and transactions honest.

The interesting part wasn’t any single widget. It was making filters, maps, and compare feel premium while still wiring CRUD, media, and permissions that hold up past a demo.

This project shows how I approach product engineering: start from user jobs (find a home, list a home, close a lead), then shape the data model and UI so those jobs don’t fight each other.

Sensitive business data and private credentials stay out of this write-up. What belongs here is the craft — architecture choices, UX decisions, and the ability to ship a multi-role marketplace shape.

SKNAT is the kind of build clients and employers recognize: a domain people understand, a surface that looks intentional, and a backend story that isn’t hand-wavy.

It demonstrates I can take a messy real-world workflow and turn it into something people can click through without apologizing for the admin side.