Multi-property operations dashboard.
A single screen that replaces three spreadsheets and two weekly ops meetings.
Status
Sector
Real Estate · Multi-property operator
Client
Operator · 47 properties, CDMX
Year
2026
Hook ─ Position
Operators with 20–80 units live in Excel and WhatsApp. Every decision costs a phone call. The opportunity isn't to modernize the spreadsheet — it's to build the command surface they never had.
Anzures · 14 con vacancia > 60 días.
Sugerido: revisión de precio.
Theory ─ How we think
An internal system shouldn't feel like software — it should feel like a tool. If the operator has to learn how to use it, we've already lost. If they open it on Monday and understand everything in 30 seconds, we win.
- 01
Single data model
Property → unit → contract → charge → ticket. One source of truth. Historical spreadsheets are imported, validated, and archived — they don't coexist.
- 02
View by role
The administrator doesn't see what the owner sees. The owner doesn't see what maintenance sees. Each view is designed for the decision that person makes at 9am.
- 03
Actionable alerts, not notifications
An alert is worth something if it leads to a concrete action in less than 60 seconds. Otherwise, it's noise. The system only alerts when there's something to decide.
- 04
Zero high-frequency forms
Capturing a received payment is one click. Capturing a maintenance ticket is a photo. Any flow that happens more than once a day was reduced to 2 taps.
Visual ─ Architecture
Capture · Model · View · Alert.
Web dashboard
responsive · roles
API
Server Actions
Jobs
alerts + reports
Postgres
single model
Every capture enters the single model. Nightly jobs calculate KPIs, generate monthly reports for owners, and trigger actionable alerts. Each role only sees what they need to decide.
How it shipped.
14 days → 0
real time
+22%
vs prior quarter
−11h/wk
reported by team · 6 people
─ Deliverables
- ✓Responsive web operations dashboard
- ✓Importers from historical Excel with validation
- ✓Actionable SMS/email alert pipeline
- ✓Auto-generated monthly reports per owner
- ✓Maintenance ticket system with photo and geolocation
─ Stack
- Next.js 15
- Server Components
- Tremor charts
- Postgres + Prisma
- Server Actions
- Trigger.dev
- Vercel
- Resend + Twilio
- Cloudflare R2
─ Timeline
8 weeks · MVP in 4, refinement with feedback in 4
Testimonial ─ Client
“By Monday morning I already know exactly which property needs attention that week. That's worth more than the whole system.”
— Director of operations · 47 properties CDMX
Does your case look like this?