Operational software prototype
Functional prototype
Property operations system
A role-scoped maintenance platform for agents, owners, tenants, and vendors, designed to make work orders, communication, recurring jobs, and completion visible in one system.
- Role
- Product design and full-stack engineering
- Scope
- Role-scoped functional prototype
- Users
- Agents, owners, tenants, and vendors
- Status
- Demo environment, not a production rollout
Context
Every role sees one work order differently.
Property maintenance moves through several people who each need a different view of the same work. A tenant reports an issue, staff triage and assign it, a vendor completes field work, an owner needs visibility, and finance may need to review the resulting invoice.
I built a functional prototype to test how that operation could live in one role-aware product. The prototype focuses on the working journeys and the system model. It does not present proposed integrations or future production infrastructure as already shipped.
The operation needs a shared source of truth without exposing every internal detail to every participant. Staff need queues and assignment controls, vendors need a focused field workflow, tenants need clear communication, and owners need visibility without operational noise.
Recurring maintenance, conversations, attachments, status changes, vendor completion, and invoice review also need to remain connected. If those records split across email and spreadsheets, the team loses context and cannot reliably see what is waiting, late, or complete.
System
What the prototype demonstrates
01
Role-scoped workspaces
Different navigation, records, and available actions for agents, owners, tenants, and vendors, backed by role-aware access rather than presentation alone.
02
Work-order intake and dispatch
Property-linked requests, triage details, priorities, assignments, status movement, and saved operational views for the staff coordinating work.
03
Real-time conversations
Work-order communication that keeps messages and operational context attached to the record instead of separating the discussion from the task.
04
Recurring maintenance
Scheduled maintenance definitions and background execution that create future work while preserving the relationship to the recurring plan.
05
Vendor field completion
A mobile-focused path for assigned vendors to review work, communicate, record completion, and provide the information staff need for review.
06
Invoice review and notifications
Operational follow-through after completion, including review states and event-driven notifications that keep the next responsible person informed.
Architecture
Product decisions tested in the prototype
Use one record across every role
Each participant sees an appropriate projection of the same work order, reducing duplicate updates and preserving a coherent history.
Design queues around decisions
Saved views and filters focus on what needs assignment, response, approval, or follow-up instead of treating the dashboard as a passive summary.
Keep communication in context
Messages belong to the work order and remain available beside status, assignment, property, and completion details.
Separate demonstrated and proposed scope
The case study labels the system as a prototype and limits claims to behavior implemented in the demo environment.
Result
A concrete model for a complicated service workflow.
- The prototype demonstrates how one operational record can support staff coordination, tenant reporting, owner visibility, and vendor field work without giving every role the same interface.
- Recurring work, conversations, completion, notifications, and invoice review remain connected to the maintenance lifecycle.
- The demo creates a reviewable foundation for deciding what belongs in a production release and which proposed integrations still require validation.
- The work remains explicitly framed as a functional prototype, with production authentication, integration, and rollout decisions left for a later delivery phase.
Related services
Building something with similar complexity?
Show me what you're buildingShare the roles, workflows, or integrations that need to work together. I'll help turn the difficult parts into a clear, buildable system.