What We Would Build on Top of AppFolio or Buildium: Maintenance Dispatch With Per-Owner Approvals, Scoped and Priced (2026)
A worked scope for the one workflow property managers keep in spreadsheets next to AppFolio or Buildium: maintenance intake, vendor dispatch and approvals that differ per owner. What the platform does, where it stops, the API plan you need, what KUMO would build, and what it costs.
Oct 24, 2026
If you manage 500 to 2,000 doors on AppFolio or Buildium, the workflow most likely living in a spreadsheet next to the platform is maintenance: a request comes in by phone or text, someone re-keys it, a vendor is chosen by memory, and the approval depends on which owner holds the property and how much the job costs. The platform records the work order; it does not run that decision. This page is the scope we would propose for exactly that gap: an intake and dispatch layer with approval rules per owner, written back into the platform through its API, for $20,000 to $50,000 over 8 to 12 weeks. The first line item is not ours: the API is a plan upgrade on both platforms (AppFolio read and write on Max at $5.00 per unit per month; Buildium Open API on Premium from $400 a month; prices read 19 October 2026), and that step is priced before anything is built.
Key facts (updated 20 October 2026; platform prices read 19 October 2026)
- The gap: per-owner approval thresholds, vendor rules and SLAs, and an audit trail across intake, dispatch and the ledger
- API access: AppFolio Core none, Plus read-only, Max read and write (from $1.49, $3.20 and $5.00 per unit per month, 50-unit minimum); Buildium Open API on Premium only (from $400 a month for the smallest unit tier)
- Build: $20,000 to $50,000 for the single workflow; $50,000 to $100,000 if an owner portal and vendor portal are added; 8 to 12 weeks
- Running costs on top: hosting (a few hundred dollars a month), any AI model usage if intake is read by a model (under $100 a month at this volume), and $5,000 to $10,000 per month of engineering if you have no engineers
- Standard tool wins when one approval rule covers every owner and maintenance is in-house; configuration (AppFolio Realm-X Flows, Buildium workflow automations) covers the middle; custom is justified by rules that differ per record
Who this is for
A property management company with 15 to 40 staff and 500 to 2,000 units, mixed owners, outsourced maintenance vendors, and a maintenance coordinator who spends the day in three places: the phone, a spreadsheet of exceptions, and the platform. The owner of the company has usually already asked the platform vendor and been told the feature is on the roadmap.
Where the platform stops
Both platforms handle the work order itself: create it, assign a vendor, track status, bill the owner. What neither runs today for a multi-owner portfolio: an intake that takes a tenant's text or call and creates a structured request; a rule like "under $500 and the vendor is on this owner's approved list, auto-approve; between $500 and $2,000, approve by the property manager; above $2,000 or any plumbing or roof job, route to the owner with photos and two quotes"; vendor selection by trade, zone and SLA; an audit trail that answers "who approved this, when, on what evidence" without reading email. The platform vendors' own AI features (read 19 October 2026 from their pages) summarise, draft and answer; they do not run per-owner approval logic across the ledger.
What we would build
| Part | What it does | Writes to the platform |
|---|---|---|
| Intake | Tenant request by text, email, portal form or a phone transcript becomes a structured request: unit, category, urgency, photos; duplicates matched to open work orders | Creates the work order in AppFolio or Buildium |
| Rules engine | Approval thresholds and vendor lists per owner and per property; emergency overrides; SLA clocks per trade | Reads owners, properties and vendors from the platform |
| Dispatch | Picks the vendor by trade, zone, SLA and owner list; sends the job; collects acceptance, ETA and completion photos | Updates the work order status and assigned vendor |
| Approval queue | One screen for the coordinator and one for each owner: approve, request a quote, reject, with the evidence attached | Posts the approved amount and the invoice reference back to the ledger |
| Audit and reporting | Every decision logged with who, when, what evidence; monthly per-owner report of jobs, spend, SLA hits and misses | Reads the ledger; exports to the owner statement |
Not built: accounting, rent collection, leasing, the resident portal. Those stay on the platform. The custom layer is the one workflow with rules of its own, and the platform remains the system of record.
What it costs, step by step
| Line | Amount | Note |
|---|---|---|
| API plan step, AppFolio | Core to Max at 800 units: from $14,304 to $48,000 a year (about $33,700 more) | Plus gives read-only, enough for reporting but not dispatch |
| API plan step, Buildium | Growth to Premium: from $192 to $400 a month starting price, more at 800 units | Premium also includes unlimited eSignature and cheaper EFT, which partly pay for it |
| Build (one workflow: intake, rules, dispatch, approvals, audit) | $20,000 to $50,000 once | 8 to 12 weeks; discovery against last quarter's real work orders |
| Owner portal and vendor portal added | $50,000 to $100,000 once | 12 to 20 weeks |
| Hosting | a few hundred dollars a month | |
| AI model usage if intake is read by a model | under $100 a month at a few thousand requests | Anthropic and OpenAI per-token prices read 19 October 2026 |
| Ongoing engineering if you have no engineers | $5,000 to $10,000 per month | month to month |
If the API step does not clear, the layer can run on scheduled exports and email for owner reporting, which is slower and good enough for reports but not for dispatch; the estimate says which.
How the first 12 weeks run
Weeks 1 to 2: a call with the coordinator and two owners, read access to the platform or exports, and last quarter's work orders turned into test cases (which should have auto-approved, which should have routed, which went wrong). Weeks 3 to 7: intake, rules and dispatch built and run in shadow mode next to the coordinator. Weeks 8 to 10: approval queue and owner screens, audit log, write-back to the ledger, tests on the real cases. Weeks 11 to 12: phased rollout by owner, runbook, handover of code and infrastructure to you.
Proof, labelled
KUMO has not published a property-management case study, so the proof here is adjacent. Equipp is a rental operations platform KUMO built: item-level orders, asset identity, delivery-gated invoicing and auditable deposit and credit-note ledgers, the closest shape to units, work orders and owner ledgers. KUMO's founders built Volopay's first production version as its founding engineers, a finance product where every approval and every payment had to be traceable, which is the discipline per-owner approval rules need. CampaignHQ is KUMO's own workflow product, in production since 2022. KUMO is a software engineering studio that builds custom AI agents, workflow apps and portals for 10 to 100 person companies, and a Registered Partner in the OpenAI Partner Network.
Questions property managers ask
Can you build custom software on top of AppFolio? Yes, through the AppFolio API, which is read-only on Plus and read and write on Max (read 19 October 2026). Dispatch and approvals need write access, so the Max plan is part of the cost; reporting can run on Plus.
Does Buildium have an API for custom integrations? Yes, Buildium's Open API is included on the Premium plan (from $400 a month, read 19 October 2026); Essential and Growth do not include it.
What does a custom maintenance approval workflow cost on top of AppFolio or Buildium? $20,000 to $50,000 for intake, per-owner rules, vendor dispatch, approval queue and audit log with write-back; $50,000 to $100,000 with owner and vendor portals; plus the plan step, hosting and ongoing engineering.
Should we replace AppFolio or Buildium instead? No. Accounting, rent collection, leasing and the resident portal are mature and cheap per unit; build only the workflow the platform cannot run and keep the platform as the system of record.
Can the platform's own AI do this? Their AI features summarise, draft and answer questions (read 19 October 2026). Per-owner approval rules across intake, dispatch and the ledger, with an audit trail, are not what they run today.
How do we start? Send three lines: how many doors and owners, what the maintenance process looks like today, and which platform plan you are on. A senior engineer replies within two working days with a band and the questions we would ask on a call.
Send the three lines here, compare the platforms in Buildium vs AppFolio vs a custom workflow layer, see AI workflow automation, or book a 30-minute call.
