Real estate · Architecture · Ambiguity
Real Estate Platform from Zero
- Period
- 2024
- Role
- Frontend Engineer
- Industry
- Real Estate
- Result
- 0missed deadlines
The challenge
What was the problem
A new platform with no clear requirements, a hard launch date set by an external partnership, and stakeholders who kept changing their minds week to week. The first stand-up I joined had three different definitions of "MVP" in the room.
The approach
How I solved it
- Ran two requirement-mapping workshops in the first week — turned vague ideas into a single priority-ordered list everyone could point at
- Picked an architecture that absorbed change cheaply — file-based routing, server actions, no premature abstractions, every screen owned by one component tree
- Built in vertical slices, not horizontal layers — each slice shipped end-to-end weekly so stakeholders could react to working software, not specs
- Locked the launch scope two weeks before the deadline; everything else moved to a follow-up backlog instead of derailing the release
- Documented every architecture call as a one-page ADR so future contributors understand *why*, not just *what*
Stack
Tools that did the work
- Next.js
- React
- TypeScript
- Tailwind CSS
- PostgreSQL
- Vercel
The outcome
What was delivered
- Translated raw ideas into concrete, prioritised business goals in week one
- Architected and built the platform from zero with the team
- Requirements kept shifting throughout the build — the deadline never moved
- Launched on the agreed date with the agreed scope, zero P0 incidents in week one
Have a similar problem?
30-minute call, no pitch — let's see if I'm the right fit.