AppFolio automates what happens inside AppFolio. We build the rest.
Realm-X is real, and for work that starts and ends inside the platform it keeps getting better. But your operation does not end at the tab: the phone line, the owner's inbox, the vendor thread, and the corporate books all live outside it. We design, build, and run the layer that connects them, and we tell you plainly when a native feature means you should not pay us.
The platform is not the operation.
AppFolio is where the record lives. The work arrives everywhere else, and somebody on your team is the bridge: listening, retyping, reconciling, chasing. Every door you add makes the bridge longer.
- The 11pm maintenance call lands in voicemail, and AppFolio finds out on Monday when someone types it in
- Leasing inquiries answered the next business day, guest cards created by hand from an inbox
- Realm-X can draft and route inside the platform, but the work that starts on a phone line or in a vendor text still crosses the boundary through a person
- The corporate books in QuickBooks and the AppFolio ledger agree only after someone spends a day at month end making them agree
- Delinquencies, expiring leases, and stale work orders discovered by running reports, not because anything flagged them
What we build around AppFolio.
Each of these is a boundary crossing: work that starts outside the platform and has to land in it accurately, or data inside it that has to reach a person in time to matter. Every one has a trigger, an action, and a named human gate.
- After hours calls become structured tickets. The phone rings at 6pm or 2am and nobody in the office can take it. A voice agent answers, works out the caller, the unit, and the urgency, and files a structured ticket with a callback number instead of a voicemail. Genuine emergencies ring your on call phone under rules you wrote; the phone layer in full is our property management answering service.
- Leasing inquiries become guest cards. A prospect calls or writes about a listing. The system answers in minutes, qualifies against your criteria, writes the guest card, and books the showing. A person approves every application; the agent never decides who gets the unit.
- Maintenance triage under your emergency rules. A tenant reports a problem by phone, portal, or email. The system asks the follow up questions a good dispatcher would ask, classifies urgency against your written rules, and drafts the work order matched to the unit and its history. A flood wakes your on call person immediately; your coordinator approves before any vendor is dispatched.
- Owner reports assembled, not written. Month end arrives, or a work order closes. The system pulls the ledger activity and the maintenance record and assembles the owner update your manager would otherwise write by hand. Nothing reaches an owner until a person has read it and pressed send.
- Delinquency and exception flags, gated. Rent not in by the day you set, a lease drifting toward expiry, a work order stale for a week. The system watches for the exceptions and puts them in front of the right person with context and a drafted next step. Anything touching money or a tenancy is a human decision, and in Ontario, notices and legal steps stay with people, full stop.
- Sync with the tools AppFolio does not talk to. A lead lands in the CRM, an invoice hits the corporate books, a thread starts in Slack. The system keeps AppFolio and the stack around it in step, through the API where your plan reaches and through supported channels where it does not. Every sync is logged, and a person owns the exception queue instead of discovering mismatches at month end.
The first thing we sell you is a shorter scope.
If Realm-X or a Stack partner already covers the job, paying us to rebuild it would be a bad deal. We say so, in writing, before you sign.
AppFolio is serious about AI. Realm-X, its native layer, includes an assistant that pulls reports and runs bulk actions, a central inbox called Realm-X Messages, workflow automation called Realm-X Flows, and agentic Performers for leasing, maintenance, and resident messaging. When your problem starts and ends inside the platform, our advice is usually to configure what you already pay for, and an audit that tells you that costs a great deal less than a build you did not need.
The gap is everything that has to cross the platform's edge. Work that begins on your phone line, in an owner's inbox, in a vendor's text thread, in corporate books AppFolio does not hold, or in a CRM it has never heard of gets carried across that boundary by somebody, and today that somebody is usually a coordinator retyping. That connective layer, and the workflows AppFolio does not consider its job, is the work we do. The phone side of it is measured: at a Toronto property management and brokerage operation we run voice agents for, a 277 call production sample had zero missed calls, and the method is in the impact study.
Crossing the boundary is governed by AppFolio's rules, so we scope against them honestly. Today, direct API access depends on your subscription: Core has none, Plus is read only, and read and write access is a Max feature, with most third party tools routed through the Stack Marketplace instead. None of that is a complaint. It is the terrain, and it is why an AppFolio build gets priced after we know your plan and your stack, not off a services list, and why we will tell you when the safe route is a supported channel rather than a clever one.
The reason you can trust the refusal is the shape of the engagement. The audit is paid, so the recommendation is the product rather than bait for a build. The build is fixed scope and you own the code on day one. And the operate retainer is judged on whether the system keeps working, so when AppFolio ships a native feature that covers something we built, the retainer's job is to retire our version, not defend it.
Who this is for.
- Managers on Plus or Max. Where the API reach makes the deeper builds possible: live sync, owner reporting, and exception flags read straight from the database instead of from exports.
- Operations with a stack around the platform. A brokerage CRM, corporate QuickBooks, Slack, a phone line that actually rings. The more systems AppFolio has to coexist with, the more a connective layer pays.
- Teams that bought the tools and still retype. Stack partners solve point problems well. The workflow between them is nobody's product, and it is usually where your coordinator's day goes.
- Not for: problems that live entirely inside AppFolio. If your pain is clicks inside the platform, Realm-X plus a competent admin probably solves it without us. We will tell you that on the discovery call, which is free, and you can spend the budget on something that needs it.
Questions, answered straight
Does AppFolio already have AI? What is Realm-X? Yes, and it is real. Realm-X is AppFolio's native AI layer: an assistant for reports and bulk actions, a central inbox called Realm-X Messages, workflow automation called Realm-X Flows, and agentic Performers for leasing, maintenance, and resident messaging. AppFolio's own launch material claims users save over ten hours a week with it. Take a vendor number as a vendor number, but the direction is right: for work inside the platform, use it.
If Realm-X keeps improving, why pay for custom automation at all? Because Realm-X automates AppFolio's side of the boundary, and your operation crosses that boundary all day: the phone line, the owner email, the vendor thread, the corporate books, the brokerage CRM. We build the layer that carries work across it accurately. And when AppFolio ships something native that covers a piece we built, we retire our piece rather than defend it. That is part of what the operate retainer is for.
What actually integrates with AppFolio? Two supported routes. The Stack Marketplace is AppFolio's partner program, with pre built connections to specific third party tools. Direct API access depends on your plan today: Core has none, Plus gets read only access, and read and write is a Max feature. We scope against what your subscription can actually reach, and where a tool has no safe way in, we say so up front instead of building something fragile.
We are on AppFolio Core. Can you automate anything? Some things, honestly not everything. The phone layer, intake automation, and workflows that live in the stack around AppFolio do not need its API at all. The deeper builds, live sync and exception flags read straight from the database, want Plus or Max. Whether your plan supports what you want is exactly the kind of question the free discovery call exists to answer before you spend anything.
What does AppFolio automation cost? The figures are published. An audit runs $3,000 to $5,000. A single system build runs $8,000 to $15,000, and work spanning several systems $15,000 to $30,000. Voice agents are a setup fee, then about $1,000 a month. There is also a second bill, the software the system runs on, and we quote it separately before you sign. The full price list and the reasoning behind it are in the rate card post.
What happens if we leave AppFolio for Buildium or something else someday? You own the code from day one, and the AppFolio specific part of any system we build is the connector, not the system. Moving platforms means rewiring that edge, a bounded job rather than a rebuild. We do the same work on Buildium today, where the API terrain is different but the boundary problem is identical, so if a migration is in your future we can scope both sides of it.
Will this replace our property managers or coordinators? No, and we do not take engagements whose purpose is cutting headcount. The system takes the after hours calls, the retyping, and the report assembly off the people you already have. The judgment stays with them: approvals, applications, anything that touches a tenancy or moves money. If what you want is a smaller team, we are the wrong firm.
Run Buildium instead? We build there too. For the broad vertical picture, see AI for property management, and for how the platform tools compare, the operator's guide.