Product strategy · PropTech · Indonesia

The operating system for residential communities.

Hunian Kita replaces the WhatsApp-group-and-Excel chaos of estate management with one platform that residents open every week — not once a month — and that management runs their entire operation on. This is the thinking behind the product and the portal.

Community Operations Platform Not a payment app · not a complaint app 100 – 10,000+ units Multi-tenant SaaS
North star

Vision & mission

Vision

Every residential community in Indonesia — from a 120-unit cluster to a 10,000-unit superblock — runs on one trusted platform that makes living there easier and managing it effortless.

Mission

Turn fragmented, manual estate operations into a single transparent system — so residents always know what's happening, and managers spend less time chasing and more time serving.

If a resident only opens the app to pay IPL once a month, we have already failed. The product must earn a place on the home screen through daily usefulness — security, visitors, and communication — and let payment ride along.
The operational reality

What actually goes wrong today

Estates don't lack software — they lack a system. Operations are scattered across WhatsApp groups, Excel sheets, paper forms, the security post, and a separate accounting tool. Nothing connects. Here are the problem clusters that matter most, rated by severity and how often they bite.

For residents

No clear way to report

High
  • Issues vanish into a 400-member WhatsApp group
  • No idea who is responsible or if anyone saw it
  • No status, no ETA, no proof it was handled

Payments are friction

Medium
  • Forget due dates, lose the paper invoice
  • Manual transfer, then chase admin for confirmation
  • No receipt, no payment history

Missed information

High
  • Water shutdown notice buried under 200 chats
  • Find out about an outage when the tap runs dry
  • Events, AGM, and alerts all in the same noisy group

Visitor & security gaps

High
  • Guests stuck at the gate, phone calls to verify
  • Deliveries left at the post, packages lost
  • No record of who entered and when

Shared facilities

Medium
  • Booking the hall means texting the manager
  • Double-bookings and unclear availability
  • No transparent rules or pricing

No sense of community

Medium
  • Don't know neighbors or the RT/RW structure
  • No trusted local marketplace or directory
  • Decisions made without resident input

For management

No operational visibility

High
  • Can't see what's open, overdue, or breaching SLA
  • Workload and team performance are invisible
  • Recurring problems never get spotted

IPL collection leaks

High
  • Manual billing, manual reconciliation in Excel
  • Chasing late payers one-by-one over WhatsApp
  • No aging view; cash-flow gaps appear by surprise

Broadcasting is hard

Medium
  • Posting to 6 WhatsApp groups, hoping it lands
  • No read receipts, no targeting by block
  • Emergencies compete with chit-chat

Staff coordination

Medium
  • Work assigned verbally, nothing logged
  • No SLA, no accountability, no audit trail
  • Handovers between shifts lose context

Asset & vendor chaos

Medium
  • No record of equipment, warranties, or service history
  • Vendor invoices and SLAs live in someone's inbox
  • Reactive maintenance, never preventive

Reporting to the board

Medium
  • Monthly report is days of manual Excel work
  • Numbers are stale and hard to trust
  • No data to justify budget or fee increases
Who we serve

The people on both sides of the gate

Two audiences, one platform. Residents range from a phone-native young professional to an elderly homeowner who opens an app only when needed. Management is a small team wearing many hats. The design has to make the same data feel simple to all of them.

Residents

AR
Adi Rahman
28 · Young professional, apartment tenant
"I just want to pre-approve my Gojek order and book the gym without calling anyone."
Goals
Fast, self-service everything. Pay in two taps. Skip the gate queue for guests.
Frustrations
Phone calls, paperwork, and waiting. Won't read a 400-message group.
Hooks
Visitor passPay IPLFacility booking
SW
Sri & Wahyu
39 · Family homeowners, landed cluster
"With two kids, safety and clean common areas matter more than anything."
Goals
Know the estate is safe and well-run. Report a broken playground and see it fixed.
Frustrations
Issues ignored, no follow-up, unclear where the IPL money goes.
Hooks
ComplaintsAnnouncementsCommunity events
BH
Bu Hartini
67 · Elderly resident, owner-occupier
"Make it big and simple. I only open it when something is wrong."
Goals
Reach security fast. Understand her bill. One obvious button per task.
Frustrations
Tiny text, hidden menus, jargon. Afraid of "pressing the wrong thing".
Hooks
Panic / call securityPay IPLEmergency alerts
DP
Dimas Putra
34 · Tenant + RT volunteer
"I help coordinate our block — give me a way to reach everyone that isn't WhatsApp."
Goals
Organize his block, run polls, share trusted info, escalate to management.
Frustrations
No tools for community organizing; everything is informal.
Hooks
Polls & votingDirectoryMarketplace

Management

RW
Rani Wibowo
Estate Manager
Needs
One screen that says what needs her now: incidents, SLA, collection.
FA
Finance Admin
Billing & collection
Needs
Auto-billing, reconciliation, aging, one-tap reminders.
CS
CS Officer
Resident-facing
Needs
Triage complaints, route to teams, keep residents updated.
SC
Security Coord.
Gate & patrol
Needs
Verify visitors fast, log entries, respond to panic alerts.
The core principle

Designed around frequency of use

We prioritize features by how often a resident touches them — because frequency drives habit, habit drives adoption, and adoption is what makes a community platform defensible. Payment alone is monthly; it can't carry the product. Daily features do.

Daily

The reason to open it
  • Security & patrol updates
  • Visitor passes & gate
  • Resident notices / chat
  • Package & delivery alerts
  • Today's bookings

Weekly

Staying in the loop
  • Community announcements
  • Service requests
  • Facility booking
  • Marketplace & directory
  • Polls & surveys

Monthly

The money
  • IPL payment & receipt
  • Financial statements
  • Community reports
  • Meter readings

Occasional

When it matters
  • Complaints & issues
  • Emergency / panic button
  • Document requests
  • Move & renovation permits
  • Vehicle registration

What to build, and what to resist

High-value, build early

Visitor management is the sleeper hit — daily, social, and instantly useful. Announcements with read receipts end the WhatsApp problem. Complaints with live tracking build trust. One-tap IPL + receipt removes the biggest admin headache. Package hold alerts create a small daily reason to open the app.

Tempting, but phase carefully

Marketplace and local business directory need critical mass — great for retention, wrong for MVP. Voting & permits are high-trust, lower-frequency — Phase 2/3. Avoid over-building asset management into a CMMS; managers want a log, not SAP. Resist any feature that adds a menu without adding a weekly reason to return.

Signature workflow

Complaint & issue resolution

The goal: a resident reports in under 30 seconds, and from that moment everyone can see exactly what's happening. Behind the scenes it becomes a tracked work-order with an SLA clock.

Resident side — report in 30 seconds

1

Pick category

Big icon grid — water, power, security, road. No typing required.

2

Snap a photo

Photo or short video, optional voice note for non-typers.

3

Auto-location

GPS + unit pre-filled. Confirm or drop a pin on the map.

4

Submit

Priority auto-suggested. One tap sends it. Ticket ID issued.

5

Track & rate

Live status, push updates, then a 1-tap satisfaction rating.

Management side — triage to resolution

1

Auto-triage

Category + keywords route to the right team and set SLA.

2

Assign

One click to a team and lead; workload is visible.

3

SLA clock

Countdown per priority; at-risk and breached surface on the dashboard.

4

Update

Each status change notifies the resident automatically.

5

Resolve & learn

Close, capture the rating, and feed recurring-issue analytics.

Signature workflow

IPL billing & collection

Make paying effortless and make chasing automatic. Higher collection rates are the single clearest ROI we can show a management body — it often pays for the platform several times over.

1

Auto-generate

Invoices created monthly from the unit register — fixed dues, meters, arrears.

2

Smart reminders

Before due date, on due date, and escalating after — push + WhatsApp.

3

One-tap pay

Local rails — Midtrans/Xendit, VA, QRIS, e-wallet. Instant receipt.

4

Auto-reconcile

Payments matched automatically; aging & cash-flow update live.

The collection lever. Most estates sit at 80–90% collection. Automated reminders plus frictionless payment routinely move that up several points. On a 1,240-unit estate at Rp 700,000/month, a 5-point improvement is roughly Rp 43 million recovered every month — the kind of number that closes the deal with a management body.

Structure

Architecture & information design

Two front doors onto one system. The resident app is a flat, tab-based "super app". The management portal is a role-aware operations console. Both read and write the same multi-tenant data.

Resident app · 5 tabs, nothing hidden

Home
Personalized feed: alerts, my bills, quick actions
Services
Complaints, requests, facility booking, permits, documents
Gate
Visitor passes, packages, vehicle, panic button
Community
Announcements, events, polls, marketplace, directory
Pay
IPL, history, receipts, statements

Management portal · operations console

Command center
What needs me now — incidents, SLA, collection, today
Complaints & work-orders
Triage, assign, SLA, recurring-issue analytics
Finance & IPL
Billing, reconciliation, aging, reminders, reports
Broadcast · Facilities · Visitors
Targeted announcements, approvals, gate log
Residents & assets
Unit register, households, assets, vendors, settings

Screen inventory at a glance — Resident: ~22 screens across 5 tabs. Management: ~16 primary views plus detail drawers. MVP ships a focused subset (see roadmap).

Business model

Monetization & pricing

We evaluated per-resident, per-property, and per-unit. Per registered unit, billed monthly to the management body, wins: units are stable and known (residents churn, properties are too coarse), it aligns price with value, and it scales cleanly from a 120-unit cluster to a 10,000-unit superblock.

Komunitas
Small estates · 100–500 units
Rp 4.000 / unit / mo
  • Complaints, IPL, announcements
  • Visitor passes & gate log
  • Resident app + 3 staff seats
  • Standard payment rails
Most estates
Pro
Medium · 500–2,000 units
Rp 3.000 / unit / mo
  • Everything in Komunitas
  • Facility booking, packages, polls
  • SLA tracking + analytics dashboard
  • Unlimited staff, role permissions
Enterprise
Large · 2,000–10,000+ units
Custom
  • Everything in Pro
  • Multi-estate / developer console
  • API, SSO, custom branding
  • Dedicated success manager

Revenue streams

SaaS subscription
Per-unit recurring — the core, predictable revenue.
~70% of revenue
Payment processing
Small take-rate / convenience fee on IPL and bookings.
Volume-based
Marketplace & ads
Commission on vetted local vendors; sponsored directory placement.
Phase 2+
Premium add-ons
CCTV/IoT integrations, accounting export, advanced analytics.
Upsell
Retention is the whole game. Switching cost is high once an estate's residents, history, and finances live here — so we win by driving weekly active residents, not just signed contracts.
How it's built

Technical architecture

A multi-tenant SaaS where each estate is an isolated tenant, mobile-first for residents and web for management, built on proven, scalable, Indonesia-ready infrastructure.

Resident appiOS + Android
React Native (or Flutter) — one codebase, native feel. Offline-tolerant, push via FCM, lightweight for older devices and patchy networks.
Management portalWeb
React + TypeScript SPA. Responsive, role-aware, real-time dashboards. The console you see in this prototype.
BackendAPI
Node/NestJS or Go, REST + WebSockets for live updates. Background workers for billing runs, reminders, and notifications.
DataStorage
PostgreSQL with row-level tenant isolation; object storage (S3-compatible) for photos/videos; Redis for caching & queues.
IntegrationsLocal rails
Midtrans / Xendit (VA, QRIS, e-wallet), WhatsApp Business API, FCM push, maps & optional CCTV/IoT.
FoundationsSecurity & scale
Tenant isolation, RBAC, encryption at rest/in transit, audit logs, autoscaling, regional hosting for data residency.

Core data entities

Tenant/EstateUnitResidentHouseholdMembership/RoleStaffUser ComplaintWorkOrderSLAPolicyTeamAssetVendor InvoicePaymentTransactionAnnouncementDelivery FacilityBookingVisitorVisitorPassVehiclePermit PollDocumentNotificationAuditLog
Sequencing

Product roadmap

Ship a sharp MVP that proves daily value and the collection lever, then layer on the features that deepen habit and create network effects.

MVP

Prove the core loop

Months 0–4 · pilot estates
  • Complaints with photo, GPS & tracking
  • IPL billing, online pay & receipts
  • Announcements with read receipts
  • Visitor passes + gate log
  • Management command center
Goal: daily-active residents > weekly logins per unit; collection +3–5 pts.
Phase 2

Deepen the habit

Months 4–9 · scale-up
  • Facility booking + approvals
  • Package & delivery management
  • Polls, surveys & events
  • Analytics & SLA reporting
  • Asset & vendor log, permits
Goal: multi-feature weekly engagement; expand to 50+ estates.
Phase 3

Network effects

Months 9–18 · platform
  • Community marketplace & directory
  • Panic button & neighborhood watch
  • Resident voting / digital AGM
  • Developer / multi-estate console
  • CCTV/IoT & open API
Goal: become the default — switching cost & cross-estate network value.
How we'll know it's working

Success metrics

≥ 60%
Weekly active residents / unit
The real adoption signal — not monthly payers.
+5 pts
IPL collection rate
Clearest hard-ROI for the management body.
< 24h
Median complaint resolution
Trust is built one resolved ticket at a time.
≥ 4.5
Resident satisfaction (CSAT)
Captured at the end of every resolved issue.
> 95%
Net revenue retention
High switching cost → durable recurring revenue.
−40%
Manager admin hours
Less chasing, more serving — the operator's win.
Hunian Kita — product strategy · design exploration Overview · Open the portal →