Tenant Maintenance Request Clarifier / Work-Order Intake
Build a lightweight tenant-maintenance intake layer for small property managers that turns vague texts like “the sink is broken” into dispatch-ready work orders with photos, fixture/model details, urgency, access permission, and vendor-ready diagnosis before anyone rolls a truck.
Best first buyer: independent residential property managers, small multifamily operators, and landlord-operators managing roughly 25-300 doors who are too small for a heavy maintenance coordination service but large enough that bad intake creates recurring vendor waste. The daily user is the owner/operator, maintenance coordinator, or admin who receives tenant texts, portal messages, and calls, then decides whether to dispatch an in-house tech, outside vendor, or ask follow-up questions.
A fresh Reddit seed in r/PropertyManagement described the exact failure mode: a tenant texts “the sink is broken,” then goes quiet for two days; the vendor arrives without model number or photos and cannot do anything. Comments framed it as an intake-funnel failure: require more details before dispatch, keep the issue pending until photos/location/fixture/symptom data are complete, and give repair people enough information to act.
This is not just one complaint. Kiara’s maintenance-intake article uses almost the same example — “the thingy under the sink is dripping” — and lists the missing questions: which sink, what part is leaking, speed of leak, water damage, and start time. It also states the current alternatives are phone “twenty questions” or a diagnostic handyman visit costing $75-$150 just to learn what is wrong.
Paid-market validators show budget and workflow density. Property Meld sells property-maintenance operations software with a resident portal, conversational repair intake, diagnostics, scheduling, workflow automation, vendor coordination, and invoice capture; its public pricing is $1.60-$2.00 per unit plus a MAX On-Call add-on at $1.50 per unit, with a $160/month minimum. Latchel sells outsourced 24/7 maintenance coordination, promising residents can call/text/message and that its team gets to the bottom of service requests. Apartments.com and AppFolio also market maintenance dashboards, online maintenance requests, photos, prioritization, and dispatch/work-order flows.
The wedge is therefore narrow: not “property management software,” and not “full maintenance coordination.” It is a pre-dispatch clarification gate that plugs into where small operators already work: SMS, email, tenant portal, Google Forms, AppFolio/Buildium exports, or a simple share link.
Property managers are already trained to expect resident portals, photos, and maintenance dashboards, but many small teams still receive tenant texts and incomplete portal submissions. LLMs and phone-friendly web forms make it cheap to ask dynamic follow-up questions in tenant language, classify urgency, and produce a vendor-ready work order. The buyer does not need a new PMS; they need fewer dead-end dispatches, fewer tenant follow-up loops, and cleaner documentation.
Weekend-buildable v1:
Avoid in v1: full rent ledger, owner accounting, vendor marketplace, emergency-call liability, guaranteed diagnosis, and replacing Property Meld/Latchel.
Start with “stop sending vendors to mystery repairs” language, not generic AI property management. Channels:
| Substitute | What it covers | Gap for this wedge |
|---|---|---|
| Property Meld | Full maintenance operations, resident portal, repair intake, diagnostics, scheduling, vendor coordination, analytics | Strong incumbent for 100+ doors; heavier and broader than a simple intake clarifier for small operators |
| Latchel | 24/7 maintenance coordination and resident response | Done-for-you service, not a self-serve intake layer; may be too expensive/heavy for smaller managers |
| AppFolio / Buildium / Apartments.com portals | Online maintenance requests, photos, work orders, dashboards | Many teams still get incomplete requests; the wedge is dynamic clarification and pending-state enforcement before dispatch |
| Google Forms / Typeform / Jotform | Cheap forms | Static forms do not ask issue-specific follow-ups, classify urgency, or produce vendor packets |
| Texting tenants manually | Flexible and free | Creates delays, forgotten details, and undocumented back-and-forth; fails when tenant goes quiet |
The biggest uncertainty is whether small property managers will pay separately when their PMS already has a maintenance portal. The strongest counterargument is that “vague request clarification” is a feature, not a company. The way around that is to make the product distribution-led and integration-light: a fast SMS/photo intake gate that works even when tenants text, email, or bypass the portal. Another uncertainty is freshness metadata: Reddit JSON was blocked/rate-limited, so the report uses exact-thread Reddit Atom metadata and content, not snippets, to verify the post timestamp and seed text.
Strong SMB workflow-automation wedge: reduce dead-end maintenance dispatches by turning vague tenant requests into vendor-ready work orders.