Buildium vs AppFolio vs a Custom Workflow Layer: What an 800-Unit Property Manager Pays in 2026

An 800-unit property management company pays about $14,300 a year for AppFolio Core at its published $1.49 per unit per month, about $30,700 for Plus at $3.20, and about $48,000 for Max at $5.00 (prices read 19 October 2026; minimum spend applies). Buildium's published plans start at $62, $192 and $400 a month for its smallest unit tier, so an 800-unit firm pays more than the starting price and gets the real figure from a quote. Nobody should rebuild either platform. The custom question is narrower: one workflow the platform cannot model, built on top of it through its API, for $20,000 to $50,000, and the API itself is a plan decision before it is a build decision.

Key facts (prices read 19 October 2026)

• AppFolio Core from $1.49 per unit per month, Plus from $3.20, Max from $5.00; 50-unit minimum and minimum spend; API read-only on Plus, read and write on Max
• Buildium Essential from $62 a month, Growth from $192, Premium from $400 (starting prices for the smallest unit tier); Open API on Premium only; eSignature $5, $1 or unlimited per plan; incoming EFT $2.35, $1.35 or $0.60 per transaction
• A custom workflow layer that reads and writes platform data needs AppFolio Max or Buildium Premium, so the plan upgrade is part of the custom cost
• A custom layer for one workflow: $20,000 to $50,000; several workflows with an owner or vendor portal: $50,000 to $100,000; ongoing engineering $5,000 to $10,000 per month if you have no engineers
• Standard tool wins for accounting, rent collection, leasing and resident portals every time; custom is justified only by a workflow with your own rules across more than one system

Who this is for

A property management company with 15 to 40 staff running 500 to 2,000 doors across single-family, small multifamily or associations. Trust accounting, rent collection, leasing and the resident portal already run on Buildium or AppFolio and should stay there. The pain is somewhere else: maintenance intake that still arrives by phone and text and gets re-keyed, vendor dispatch and approvals that live in a spreadsheet because the owner's approval threshold differs per property, owner reporting that someone assembles by hand every month, or an onboarding checklist for new doors that no one can see the status of. Those are workflows, and workflows are where a custom layer earns its cost.

What the platforms cost at 800 units

How to read these numbers. Subscription prices are the vendors' published list prices on the date shown, before taxes, overages, add-ons and seat growth. The custom-build figures are KUMO's published bands for the build only: hosting, model usage, third-party fees and ongoing engineering ($5,000 to $10,000 per month if you have no engineers) sit on top, and we say so wherever a total is compared. A standard tool is the right answer when your workflow fits it; configuration is enough when the gap is small; a custom build is justified only by a specific complexity named on this page, not by preference.

Buildium's per-month figures are published as starting prices and rise with unit count, and its page does not state the billing basis, so treat them as a floor; AppFolio's per-unit prices are published with a minimum spend that the quote sets. Transaction fees are real money at 800 doors: 800 incoming rent payments a month at $2.35 is $1,880 a month on Buildium Essential and $480 on Premium, which by itself can pay for the plan upgrade.

The API is the hidden line item

A custom layer only works if it can read units, tenants, work orders and ledgers from the platform and write back the result. Buildium opens its API on Premium. AppFolio gives read-only access on Plus and read and write on Max. So an 800-unit firm on AppFolio Core that wants a custom maintenance dispatch workflow is not looking at $20,000; it is looking at $20,000 plus the step from Core to Max, about $33,700 a year more. On Buildium the step to Premium is smaller and the unlimited eSignature and cheaper EFT partly pay for it. Price the plan step first. If it does not clear, the custom layer should wait or run on exports and email rather than the API, which is slower and good enough for owner reporting but not for dispatch.

Three routes, one honest recommendation

The platform is enough. Most firms under 500 doors with one owner-approval rule and in-house maintenance should configure the platform's own automation (AppFolio Realm-X Flows on Plus, Buildium's workflow automations on Growth and Premium) and stop there. Configuration, not code.

Configure plus connect. If the gap is one notification or one hand-off, an automation tool on the platform's API or webhooks closes it for a few hundred dollars a month. The n8n vs Make vs Zapier comparison prices that route.

Custom workflow layer. Justified by a specific complexity, not preference: approval thresholds that differ per owner and per property, vendor dispatch with SLAs and photo proof, a multi-step onboarding for new doors with document checks, or owner reporting that pulls from the platform plus a bank feed plus an inspection tool. KUMO builds that as a small application on the platform's API: an intake form or phone-to-ticket step, a rules engine for approvals, a vendor and owner view, and a nightly reconciliation back into the platform so the ledger stays the system of record. $20,000 to $50,000 for one workflow; $50,000 to $100,000 when it is several workflows with a portal. The Softr vs Bubble client portal comparison covers the portal half; the field-service app comparison covers dispatch.

What the build includes and what it does not

Included: discovery against your real work orders and approvals, the application, API integration with Buildium or AppFolio, the owner or vendor view, tests against last quarter's tickets, handover. Not included and on top: the platform plan, hosting (a few hundred dollars a month), any AI model usage if intake is read by a model, and ongoing engineering at $5,000 to $10,000 per month if you have no engineers. Run your own numbers in the AI development cost calculator, or send a short brief and get a scoped estimate in two working days.

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 for a B2B equipment rental business: item-level orders, asset identity, delivery-gated invoicing and auditable deposit and credit-note ledgers, which is the closest shape to units, work orders and owner ledgers. FLIN is a production portal build from scoped brief to launch. 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. KUMO is a software engineering studio that builds custom AI agents, workflow apps and portals for 10 to 100 person companies.

Questions property managers ask

Should an 800-unit property manager replace Buildium or AppFolio with custom software? No. Trust accounting, rent collection and leasing are regulated, mature and cheap per unit on either platform. Build only the one workflow the platform cannot model and keep the platform as the system of record.

Which AppFolio plan do I need for a custom integration? Plus gives read-only API access, which is enough for reporting; Max gives read and write, which dispatch and approvals need. Price that step before the build.

Does Buildium have an API? 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 dispatch workflow cost on top of AppFolio? Typically $20,000 to $50,000 for intake, approval rules per owner, vendor assignment with SLAs and write-back to AppFolio, plus the Max plan if you are not on it and hosting after launch.

Is a no-code tool enough for owner reporting? Often yes. If the report is the platform's data plus one bank feed on a monthly schedule, an automation tool or the platform's own reporting automation does it. Custom becomes worth it when the report needs reconciliation rules or data from three or more systems.

How long does a custom layer take? 8 to 12 weeks for one workflow on an existing platform API, longer if the platform plan change and data clean-up come first.

See AI workflow automation for how KUMO scopes a workflow layer, or book a 30-minute call with the two workflows that hurt most.