Residents
Self-service for access, amenities, payments, requests, and notices.
Platform
From mobile app to condominium operating platform.
The platform connects the people and workflows that keep the property running. Each surface is purpose-built. The data is shared. The community remains the owner.
Who it connects
Four audiences, one system of record.
Property management
Directory, assignments, SLAs, communications, finance, and reports.
Security
QR validation, scan history, incidents, and station-based duty.
Board / trustees
Approvals, meetings, resolutions, documents, and audit.
Visitors & gateWork permitsMove-in / move-outAmenitiesRequests & ticketsAnnouncementsDocumentsReports & audit
Product surfaces
Built as four coordinated products — not four disconnected tools.
- Resident app
- Flutter client for households: home feed, visitors, amenities, pay, requests, documents, household members, events, and notifications with preferences.
- Staff / security app
- Separate bundle and tokens from the resident app. Guards scan. Officers handle incidents. Inspectors review. Managers resolve. Tabs appear by permission — a guard never sees a manager’s inbox.
- Admin web portal
- SvelteKit operations desk: property structure, residents and verifications, work orders, complaints, finance, communications, parking, facilities, IAM, and reports.
- Board portal
- A distinct login and shell for trustees: dashboard, approvals, meetings with agenda and minutes, resolutions, documents, members, and decision history.
Shared foundation
One property record. Cross-app journeys that actually complete.
Shared data
Mobile and web share the same operational database. A resident who links a unit on the phone appears in the admin verification inbox. Approving it activates the household.
Role-based access
Residents, admin, security, board, and staff roles receive only the permissions they need. Dual-control exists for sensitive IAM changes.
Continuity
The platform remains with the community when the property manager or board leadership changes. Data export and transition assistance are contractual principles — not afterthoughts.
Start with the workflows that create measurable value.
Confirm interest, run a discovery workshop, agree Phase 1, then pilot. The objective is not to buy an app — it is to establish a reliable, community-controlled operating platform.