About us
APM Web Solutions was founded in 2023 in Austin, Texas by a group who had spent years on both sides of the problem — running property operations, and building machine learning systems for companies that had far more engineers than we did.
Origin
Two of our founding group were running operations for a mid-sized third-party management company. The portfolio had grown from 600 doors to just under 3,000 in three years. Headcount on the service desk had gone from four people to five.
The failure mode was always the same and it was never dramatic. A prospect called on Sunday afternoon and rented somewhere else by Tuesday. A resident texted about a leak at midnight and got an answer at nine the next morning, after the ceiling came down. Month-end reporting swallowed the last weekend of every month, and the reports still went out two days late.
None of that was anyone's fault. There simply wasn't a person available at the moment the work arrived. Everything else — the software, the process, the training — was downstream of that one gap.
The bottleneck was never skill. It was availability.
The other half of the founding group had spent years shipping production machine learning at companies where the model was the product. By late 2022 it was obvious that language models had crossed the line from demo to dependable for exactly this class of work: reading a messy human request, asking the right follow-up, and taking a bounded action against a system of record.
We spent 2023 building against one real portfolio, in production, with real residents and real consequences. That constraint shaped everything. APM escalates aggressively, logs obsessively, and never takes an action it can't explain — because the first version had to survive an owner asking why a vendor was dispatched at 2 AM.
Four people, one design partner portfolio of 2,900 units, and a single question: can this answer a resident better than a voicemail box?
Severity scoring and vendor dispatch go live across 11 portfolios. First month where overnight work orders were dispatched before staff logged in.
Automated reporting launches. APM crosses 200 management companies and 300,000 units under AI management, with SOC 2 Type II completed.
Sixteen people supporting 240 management companies and 9.8 million resident conversations handled to date.
Mission & principles
Our mission is narrow on purpose: every resident, prospect, and owner should get a competent answer the moment they ask, no matter the hour or the size of the team. Three principles keep us honest about how we get there.
The person on the other end of the conversation is having a bad day about a broken thing in the place they live. If a decision improves the operator's metrics but makes that conversation worse, we don't ship it. Every feature gets judged from the resident's side of the thread before the dashboard's.
Autonomy is earned per action, per customer, and it is always reversible. We would rather escalate a hundred conversations that didn't need it than automate one decision that should have had a person on it. Everything APM does is logged with its reasoning attached.
We baseline every portfolio before cutover and report against that baseline, not against an industry average that flatters us. If a customer's numbers don't move, we say so on the QBR and fix it or refund it. Claims on this site come from that data.
The team
We hire operators alongside engineers deliberately. Every model behavior, escalation rule, and default policy in APM was argued over by someone who has personally handled the call it's about to answer.
Our operations team came out of third-party management, institutional single-family, and student housing. Between them they have handled somewhere north of a quarter million maintenance requests the manual way, and they still take live escalations from customer portfolios during onboarding — partly because it's the fastest way to learn a new policy, and partly because it keeps us honest about what the product can't do yet.
Our engineers came from infrastructure, applied research, and one very long stretch of building call-center software. We work in Austin three days a week and remotely the rest, and the whole company sits in the same support channel. Everyone, including the founders, takes a rotation reading real conversations.
We're hiring
We're growing engineering, implementation, and support in 2026. Roles are posted as they open; we read every note that comes in, including the ones that don't match a posting.
Write to [email protected] with what you've operated or built. Skip the cover letter.
Where we are
Figures are drawn from production usage across every customer portfolio, not from pilots or trials. We publish the same numbers to investors that we publish here.
Get in touch
Whether you're evaluating, hiring, writing about the category, or just want to argue about maintenance SLAs — the same inbox reaches all of us.
Austin, Texas · We answer within one business day.