Real estate · Architecture · Shifting requirements
Real Estate Platform from Zero
- Period
- 2024
- Role
- Frontend Engineer
- Industry
- Real Estate
- Result
- 0missed deadlines
The challenge
What was actually broken
A new platform without documented requirements, a fixed launch date committed to an external partner, and stakeholders whose priorities changed week to week. The first meeting I attended contained three conflicting definitions of the minimum viable version — each actively defended by a different stakeholder.
The approach
How I addressed it
- Ran two workshops in the first week to align on requirements. Left with a single prioritised list that served as the reference point whenever priorities shifted
- Chose an architecture that absorbs change cheaply. A clear structure, no premature abstractions, and screens kept self-contained so edits stay local
- Shipped one complete feature each week, end to end, rather than building several in parallel at partial completion. Stakeholders reacted to working software instead of written specifications
- Locked the launch scope two weeks before the deadline. New requests went into a follow-up plan rather than putting the release at risk
- Wrote every significant technical decision on a single page, including the reasoning behind it, so whoever picks this up next understands *why*, not just *what*
Stack
The tools behind it
- Next.js
- React
- TypeScript
- Tailwind CSS
- PostgreSQL
- Vercel
The outcome
What was delivered
- Translated raw stakeholder input into concrete, prioritised business goals within the first week
- Designed and built the platform from the ground up alongside the team
- Requirements continued to evolve throughout the build. The launch date held.
- Launched on the committed date, with the agreed scope, and no critical incidents in the first week
Facing a similar situation?
A 30-minute call, no sales. We will quickly know whether I am the right person for the job.