01Capture
The message becomes a ticket.
Stu asks for the missing detail and attaches the photo, unit, access, and history.
AI operations teammate
Scale without adding headcount.
Stu handles maintenance coordination end-to-end, so your team stays focused on judgment.
You keep judgment. Stu handles coordination.
Built by a Cornell engineerCornell Tech roots
Stu Maintenance OS
Operations desk
8 active repairs
Ticket M-1048
Unit 4B kitchen leak
Stu has intake, access, vendor history, and the next decision in one operating record.
Repeat issueKitchen sinkThu 5-7Mike's Plumbing
Resident
Leak under sink. Home Thu 5-7.
History
P-trap serviced 41 days ago.
Access
Tenant prefers text, rear gate lockbox.
Next messages queued
ready after approval
Resident
Mike's Plumbing can come Thursday 5-7. I can confirm that window.
Vendor
Confirm Thu 5-7. Tenant can provide access and rear gate lockbox.
Operating rail
Stu gives every repair a route.
A maintenance request no longer sits between inboxes. Stu gives it a route: resident message, vendor window, owner update, and one prepared manager decision.
Stu is the quiet route between every party.
Unit 4B route
One operating path, four outcomes.
The manager enters only where judgment matters.
Resident reply ready
Vendor window held
Owner status drafted
Manager approval prepared
The loop
Maintenance creates the headcount pressure.
One leak becomes resident follow-up, access notes, vendor scheduling, owner status, and an approval question. Stu keeps that loop in one operating record.
Without Stu
One leak becomes four separate threads.
Resident
Water under the kitchen sink again. Home Thu 5-7.
History
Same P-trap leak was serviced 41 days ago.
Vendor
Mike's Plumbing wants inspection approval first.
Owner
Needs a short status update before the weekly call.
With Stu
Stu turns the thread into a ticket.
Context
Unit, photo, history, vendor, and access live together.
Schedule
Mike has Thu 5-7 ready after approval.
Decision
$180 inspection is routed to the manager with the reason.
The manager stops being the follow-up desk and becomes the decision-maker.
Stu at work
One repair. One clear next step.
Stu turns the Unit 4B repair into state your team can trust.
01
Intake received
Resident reports the repeat leak and confirms Thu 5-7 access.
02
Context attached
Stu links the photo, P-trap history, lockbox note, and owner preference.
03
Vendor packet sent
Mike's Plumbing gets the issue, history, access, and proposed window.
04
Updates drafted
Resident and owner messages are ready from the live ticket state.
05
Approval requested
Only the $180 inspection decision reaches the manager.
Live ticket
Kitchen P-trap leak
Unit 4B. Repeat P-trap issue. Access Thu 5-7.
Resident
Thu 5-7 offered
Vendor
packet sent
Owner
status drafted
Manager
$180 approval
Human handoff
Approve camera inspection.
Control
Stu carries the coordination. Your team keeps control.
Routine maintenance keeps moving without a manager chasing every thread. Cost, urgency, access, and policy decisions still come back to your team with context attached.
What Stu handles
Tenants
Answered
Stu replies, asks for the missing detail, and keeps the resident updated without your team becoming the status board.
Mike from Mike's Plumbing can come Thursday 5-7 to inspect the P-trap. I can confirm that window for you.
Vendors
Scheduled
Stu sends the issue history, access notes, photos, and proposed windows so the vendor can accept without a callback.
Unit 4B · 225 W 26th · kitchen P-trap leak · tenant available Thu 5-7 · photo + history attached · reply Y to accept.
Owners
Summarized
Stu turns noisy execution into a short owner-ready update: what happened, what it costs, and what is waiting.
This week: routine repairs are moving, one vendor estimate is waiting, and Unit 2A may need your call.
Your team
Protected
Stu keeps routine work moving and interrupts the team only when a judgment call, repeat issue, or approval is needed.
3rd noise complaint about Unit 2A in 6 weeks. Not routine anymore, tagging the manager for a call.
Meet Stu live
Give Stu one maintenance scenario.
Walk through the Unit 4B repair live: intake, vendor scheduling, owner update, and one manager decision.
See the same repair move from resident intake to vendor window, owner update, and one prepared manager decision.
FAQ
Clear answers for operators.
What is Stu?
Stu is Steward's AI operations teammate for property managers. It starts with maintenance coordination.
What does Stu actually do today?
Stu handles intake, vendor scheduling, tickets, tenant follow-up, owner updates, and escalation to your team.
Is this replacing AppFolio or Buildium?
No. Your PM software stays the system of record. Stu handles the coordination around it.
Do managers stay in control?
Yes. Stu moves routine coordination and keeps humans in the loop for approvals, repeat issues, sensitive tenant situations, and anything that requires judgment.
Who is this for?
Steward is aimed at property management operators and funds that want to add doors without adding another coordinator for every new batch of units.
What comes after maintenance?
Maintenance comes first because it is frequent and coordination-heavy. The same model can expand after operators trust it.