Real Estate2026UA
ORIEL Development
Four residential complexes, 522 apartments, monthly construction progress — one platform where availability and price are always the live ones.
- Web App
- Catalog
- Backend
- CRM integration
- Industry
- Real Estate
- Engagement
- 12 weeks
- Team
- 1 designer · 2 engineers
- Platforms
- Public platform · Apartment catalog · Progress reporting
01
Challenge
A developer selling four complexes at once has an inventory problem disguised as a marketing problem. Five hundred apartments across four projects change status daily, and a PDF price list is out of date the week it is published.
Buyers also need to trust that a building under construction will be finished — which is a communication problem no amount of rendering solves.
- Projects
- VERDE · SOLEA · CORTE · RIVA
- Inventory
- 522 apartments
- Price range
- ₴1.78M – ₴7.93M
02
Solution
A single normalised inventory model behind all four complexes — project, building, floor, apartment, layout, status — so one catalog serves every project and a new complex is data rather than a new site section.
Monthly construction reports with photography and completion percentages are a first-class content type, not a news post. Progress is something a buyer can check, which is what actually builds confidence.
Purchase options — full payment, instalments, mortgage, trade-in — are modelled per apartment, so the financing conversation starts from what is genuinely available for that unit.
- Inventory model
- Project → building → floor → apartment
- Progress
- Dated reports with completion %
- Financing
- Options resolved per unit
03
Architecture
- L0Public siteISRApartment catalogFilters
- L1API layerService
- L2Inventory serviceStatus + pricingContentProjects, progress
- L3PostgreSQLData
- L4Sales CRMSource of truthMap providerExternalLead notificationsExternal
Connections (8)
- Public site → API layer
- Apartment catalog → API layer · availability
- API layer → Inventory service
- API layer → Content
- Inventory service → PostgreSQL
- Inventory service → Sales CRM · sync
- API layer → Lead notifications · enquiry
- Public site → Map provider
04
UX
People shop for apartments by constraint — budget, rooms, floor, completion date — so the catalog leads with filters and the marketing narrative sits alongside rather than in front of it.
Every apartment and filter combination is addressable by URL, so a sales agent can send a link to exactly the unit they discussed.
- Entry
- Filter-first catalog
- Sharing
- Every unit has a permanent URL
05
UI
Architectural restraint — the buildings are the visual material, the interface stays quiet around them. Typography carries the hierarchy, not colour.
The design philosophy content (sound insulation, natural light, material longevity) is treated as editorial rather than as feature bullets, because that is the register the buyer responds to.
06
Development
Project and unit pages are statically generated and revalidated when inventory changes, so a five-hundred-unit catalog stays fast without a rebuild per status change.
Availability reads come from a cache that is reconciled against the sales system on a schedule, so a missed webhook costs freshness rather than correctness.
07
What it does
Four project sites in one
VERDE, SOLEA, CORTE and RIVA share an inventory model and a component system.
Apartment catalog
522 units filterable by project, rooms, floor, area, price and status.
Construction progress
Monthly dated reports with photography and completion percentages.
Purchase options
Full payment, instalments, mortgage and trade-in resolved per apartment.
Location map
All projects with surrounding infrastructure context.
Commercial spaces
Separate inventory track for commercial units.
Lead capture
Enquiries routed to the sales team with the unit context attached.
08
Integrations & stack
Integrations
- Sales CRM
- Map provider
- Email + messenger notifications
- Analytics
Frontend
- Next.js
- TypeScript
- Tailwind CSS
- next/image
Backend
- Node.js
- PostgreSQL
- ISR revalidation
Platform
- CDN
- Image optimisation
- Analytics
09
Where it landed
- 4
- Complexes
- 522
- Units published
- Monthly
- Progress reporting
- Data, not a rebuild
- New project
One platform, one inventory model
Filterable and individually addressable
Photography and completion %
Marketing and sales work from the same inventory. Adding the fifth complex is a content operation, not a project.
Every build is designed for the phone as its own experience, not as a narrowed desktop layout.
Got a product that should exist by now?Tell us about it.
Describe what has to change in your business. We will work out what that actually takes — including when it takes less than you think.