PM Software Landscape 2026 — What to Learn, What to Avoid, and the AAMG Build Path

Research date: July 25, 2026. Synthesized from five deep-dive workstreams: enterprise incumbents (AppFolio/Yardi/RealPage), SMB/mid-market (Buildium/Rent Manager/Propertyware/ResMan/Entrata), the challenger tier (DoorLoop/Rentvine/prosumer tools/AI-native newcomers), the accounting core (trust accounting + fintech ledger architecture), operations/resident-facing functionality, the API/integration ecosystem, the plugin-vendor ecosystem, and two voice-of-customer mining passes (review sites + practitioner forums). Every claim carries its source URL from those workstreams. Pricing figures are vendor-published or third-party estimates — directional, not quotable.

Context: AAMG = 3 El Paso multifamily properties, 640 units, ~33 staff, on AppFolio. Assets in hand: a nightly-refreshed read-only AppFolio mirror (Reports API v2 → Postgres bronze/silver, 2.58M GL rows 2015→present, 15-min incremental), a planned Rust double-entry ledger with roles + audit trail, the LTM semantic document brain (99k+ docs), and two product theses: rent-flex (landlord-controlled resident payment flexibility) and a capital/debt platform.

1. Executive Summary

The market is bifurcating, and the split defines the opportunity. Value in PM software has migrated to two places: (a) the transaction layer — payments, screening, insurance, utilities — and (b) AI agents on top of the data. AppFolio’s value-added services run ~3.5x its software subscription (Q3 2025: $192M services vs $54M core — 10-Q); Entrata’s S-1 shows 117% net revenue retention built on bundled transactional layers (S-1 breakdown); products that are “just software” (Propertyware, ResMan) are the ones bleeding share. The winners charge for money movement, not software.

Every incumbent shares one architectural corner-cut: a mutable relational GL where integrity is a report you run, not a property of the system. None offers immutable posted entries, bitemporal reconstruction, event-level provenance from statement line to source document, or posting-time trust invariants (Modern Treasury, TigerBeetle). The fintech world solved this a decade ago; PM software never imported it. That is precisely the gap the Rust ledger targets.

API access is the industry’s toll booth — and its most-requested missing feature. Yardi charges ~$25K/yr per interface with a 3-existing-clients prerequisite (Truto); Entrata charges $5K–$50K+/yr since April 2024 (Transforming Cities); AppFolio gates writes behind Max tier and blessed Stack partners. Operators at exactly AAMG’s scale called AppFolio, Yardi, and Entrata and were refused API access below ~10k units (r/PropertyManagement). Meanwhile Rentvine shipped the industry’s first native MCP server (May 2026 — PRWeb) and Yardi’s Virtuoso now uses Claude via MCP (usehaven) — the market just validated Marc’s exact mirror→Postgres→agents architecture, from both ends.

The verdict in one paragraph: Build the AAMG replacement, replica-first, on the assets already in hand — the mirror is functionally a pre-built migration (the moat that protects incumbents is ~$30K/3 months of migration pain and lost attachments; Marc has already neutralized it). Benchmark the ledger against Yardi Voyager, not AppFolio — Voyager-grade multi-entity auditability is what lenders trust and what the PFS command center needs. Buy every licensing-walled capability (screening data, insurance policies, payment rails, post-move-out collections) and build the thin deterministic/LLM layers over ledger data (RUBS, payments orchestration, pre-delinquency outreach, leasing AI, reporting). Replacing AppFolio for AAMG’s own 640 units requires zero certification from anyone — the integration-tax problem is a product-distribution problem, not a self-hosting problem. Productization is a later, separate decision; the field evidence (pitch-hostile forums, taken “transparent pricing + support” slot) says validate on AAMG first.

2. The Field in One Table

3. What the Best Implementations Teach Us, Feature by Feature

Accounting/GL — learn from Yardi Voyager. True multi-entity GL, intercompany, accrual+cash books, segregation of duties, document-attached journal entries with second-review workflow, Voyager 8’s Period Close Dashboard (Yardi). This is why institutions and lenders trust Yardi output — and it’s the acceptance bar for the Rust ledger. Also steal AppFolio’s triple tie-out bank rec screen (Adjusted Cash = Cleared Bank = GL Ending, mismatch flagged red — AppFolio Bookkeeping) and its Financial Diagnostics health report; steal Buildium’s 1099 e-file validation workflow (Buildium).

Ledger architecture — learn from fintech, not PM. Modern Treasury: immutability as a hard rule (corrections = new linked transactions, never UPDATE), pending→posted two-state entries, bitemporality (effective_at vs posted_at) so any historical balance reconstructs exactly (MT immutability, Scaling Pt V). TigerBeetle: invariants enforced by the datastore itself (docs). Stripe: append-only event log, balances = SUM(entries), hash-chained tamper evidence, 99.99% of dollar volume verified within 4 days against settlement files (Hubifi).

Developer experience — learn from Buildium + Rentvine. Buildium proves a self-serve public dev portal is possible in this industry (developer.buildium.com); Rentvine proves “free open API + native MCP” is a winning wedge that closes switches (Rentvine open API). RealPage’s RPX proves REST + event framework is the modern integration shape (RPX). Copy all three; drop the toll booths.

Maintenance — learn from Property Meld + HappyCo. Meld’s metric obsession (published speed benchmarks: 0.5-hr acceptance, 6.9-day completion; $1.60/unit/mo — Research.com) and HappyCo’s make-ready turn boards + photo inspections synced to the PMS (happy.co). The winning loop: resident submits with media → AI triage that provably doesn’t drop multi-issue detail (AppFolio’s documented BBB failure mode — usehaven) → vendor gets full context → per-tech SLA metrics.

Leasing — learn from EliseAI + Funnel, cautiously. EliseAI defines the category (omnichannel incl. voice in 33 languages, deep PMS write-back — eliseai.com); Funnel’s resolution-based pricing (pay per completed outcome) is the honest pricing innovation (Funnel). But heed the counter-evidence: −11pp renewal where AI is primary, ADA legal risk emerging, prospects with complex situations hitting bot walls (Propmodo, Multifamily Dive). Constrained generation (approved-response library + retrieval) with a fast human-escape hatch, not freeform.

Resident experience — learn from Entrata Homebody + Stessa + Flex. Homebody is the bar: payments, service requests, insurance, rent→credit reporting, community in one app (Entrata). Stessa’s Plaid-fed ~85% auto-categorization is the enrichment-pipeline reference (stessa.com). Flex proves residents will pay for payment timing flexibility (getflex.com/rent) — and RealPage buying Livble validated the space.

Screening — learn from TransUnion+Snappt and the SafeRent settlement. Bank-linked income verification (Plaid) is un-fakeable and kills the doc-fraud vector cheaply (Plaid). SafeRent’s $2.3M settlement (algorithmic score discriminated against voucher holders — Cohen Milstein) plus AppFolio’s own $8.75M in FCRA actions define the design rule: transparent documented criteria, no opaque scores, vouchers handled explicitly, adverse-action letters generated with provenance.

Business model — learn from everyone. All-inclusive per-unit pricing with no module upsells (Rentvine, MagicDoor) is the modern tier’s direct attack on module-and-minimums. Price-locked-in-writing was named as a switch-closing factor (r/PropertyManagement). And the retention anchor everywhere is consolidation: every platform users love is loved for all-in-one workflow, not features — a replacement that fragments workflows loses even with better accounting.

4. Universal Pain Points = the Opportunity List

Ranked by cross-source frequency (review mining + forum mining + module deep-dives):

1. Fee creep on payment rails — the #1 anger driver industry-wide. AppFolio’s 2023 eCheck monetization ($2.49/payment, NACHA quietly removed for new customers) instantly triggered competitor demo cycles (Reddit 143p744); DoorLoop’s per-ACH fees, Buildium’s forced payment holds. Opportunity: $0-fee ACH at wholesale cost (~$0.25 flat) under an owned ledger.
2. Support collapse at mid-market scale — 2–4-day AppFolio waits, AI chatbot deflection loops, RealPage 45-min holds; the counter-examples (Rent Manager, DoorLoop, Rentvine) win business on support alone. Opportunity: for an internal system, support = the builder; for a product, a human who answers is a stated switching trigger.
3. Accounting rigidity and workarounds — porous period close (AppFolio reopen-everything), manual pseudo-reversals (Buildium), dummy-property hacks (DoorLoop), undeletable GL codes, invisible ledgers. Accounting depth is a top-2 complaint on four of five SMB platforms. Opportunity: the entire Section 5 agenda.
4. No dual-book accounting — trust/property books + corporate books in one system exists nowhere below Yardi; everyone runs a QuickBooks side-car with no integration (AppFolio’s own customer story). Opportunity: first-class entities including the management company — already the Rust ledger’s design.
5. API gatekeeping at exactly AAMG’s scale — refused below ~10k units at AppFolio/Yardi/Entrata (Reddit 1jvbren). Opportunity: radical openness is the one differentiator incumbents structurally cannot match without cannibalizing integration-fee revenue.
6. Migration terror — ~$30K/3 months of labor; lost attachments; unreconciled opening balances (Far Out Solutions, Reddit 1gg6n3w). Opportunity: the mirror already neutralizes this for AAMG; migration tooling would be the product if productized.
7. Cross-system insight vacuum — operators explicitly wish for one queryable view over data scattered across PMS + Excel + point tools; exported CSVs go nowhere (Reddit CSV thread). Opportunity: this is literally LTM + the mirror, already built.
8. Point-solution sprawl — 9–15+ paid apps per operator, none sharing a ledger (Reddit 1kcz7ne). Opportunity: one audited spine under work orders, comms consent, payment schedules, and screening decisions.
9. Named feature white space operators say nobody offers: rent-increase intelligence (last increase vs portfolio comps), vacancy-as-zero-rent rows, automated %-based fee billing, non-unit lease objects (parking/storage), insurance additional-insured verification, mixed-use handling, professional shared-meter bill-back (forum mining §4). All are gold-layer views or small modules over data Marc already mirrors.
10. Statements are renders, not provable derivations — the CAM industry runs ~40% material error rates and $5–15B/yr leakage because recovery structures are keyed as configuration, not derived from lease terms (PredictAP). Opportunity: statements as pure functions over ledger + contract terms, every line drillable to source.

5. The Accounting-Core Verdict: What “Superior and Audited” Actually Requires

The regulatory floor is trust accounting: segregated fiduciary funds, no commingling, deposit-timing rules, 4–6-year retention, and auditors hunting negative beneficiary balances (Propertese state guide). The gold-standard control is three-way reconciliation — bank statement = trust GL = Σ(beneficiary sub-ledgers), to the penny (Rentvine). In every incumbent this is a report you run monthly. The keystone design decision:

Integrity must be an invariant enforced at posting time, not a report. A transaction that would push a beneficiary sub-ledger negative, break bank = book = sub-ledger equality, or post unbalanced simply cannot commit.

The seven requirements, each fixing a documented incumbent failure:

1. Append-only immutability — posted entries never mutate; corrections are linked reversal+repost transactions (Modern Treasury). Fixes: AppFolio’s reopen-the-whole-period edit flow; Buildium’s fake reversals; AppFolio’s documented permanent-data-loss cases.
2. Two-state posting (pending → posted) — maps directly onto NSF rent, ACH returns, undeposited funds. Fixes: Buildium’s “failed deposits recorded as received” rec bug.
3. Bitemporality + versioning — effective_at vs posted_at; any historical balance reconstructs exactly (MT Pt V). Fixes: “the owner statement changed after we sent it.”
4. Datastore-enforced invariants (TigerBeetle pattern) — debits=credits, no negative trust beneficiary, continuous three-way equality. Fixes: the two-years-unreconciled-under-state-audit case (AppFolio Bookkeeping).
5. Event sourcing with an accounting projection — mutable business objects (lease, work order, bill) separate from immutable accounting objects; ledger = replayable projection of domain events (Architecture Weekly). This is also the validation strategy: re-derive AppFolio’s books from events and diff to $0.00.
6. Maker-checker + hash-chained audit trail — draft→approved→posted state machine per entry class, per-role posting rights by GL section (AppFolio’s sectioned close as permissions, not a monthly toggle), Stripe-style hash-chained batches for tamper evidence. Matches and exceeds Yardi’s activity-attached JE review.
7. Derived artifacts with provenance — owner statements, CAM recs, 1099s as pure functions over ledger + contract-terms-as-data; reproducible bit-for-bit from a ledger version; every line drillable to invoice→GL entry→bank line→approval. Fixes: AppFolio’s unadjustable 1099 totals (APM Help) and the CAM 40%-error problem.
8. Dual-book from day one — trust/property entities AND the management company’s corporate books as first-class entities with intercompany. This is the single most-requested thing no sub-Yardi platform does.

Honest credit where due: AppFolio’s operational integration (bank feeds, tie-out, diagnostics) is genuinely good and is why it wins its market; a superior ledger with worse bank-feed matching loses in practice. The two make-or-break outputs practitioners name are NACHA files to the bank and correct 1099s (Reddit 143p744) — unglamorous, non-negotiable.

The validation asset nobody else has: shadow-ledger replay of the 2.58M-row mirror. Re-derive AppFolio’s books from events, diff to $0.00 (feasibility already proven by the loan-amortization reconciliation to $0.00 against the GL), then parallel-run before any cutover. This converts “trust our new system” into “here is a machine-checked proof our books equal the old books.”

6. Build-vs-Buy Map

The boundary is licensing walls vs thin layers over ledger data. Everything worth building is a deterministic or LLM layer over data already mirrored; everything worth buying is regulated entry (CRA/FCRA, insurance DOI, money transmission, FDCPA) that no engineering purchases.

7. The AAMG Build Roadmap — Replica-First, with Exit Tests

The strategy exploits an asymmetry: AppFolio keeps running while each phase proves itself. No big-bang cutover, ever. Each phase ships value even if the next phase never happens.

Phase 0 — Replica-first: dashboards and KPIs on the mirror (largely in hand)

Read-only. Gold-layer views over the bronze/silver mirror: portfolio KPIs, delinquency curves, vacancy-inclusive rent rolls, rent-increase intelligence, EDDIE-DEBT-SHEET-style debt reporting, LTM-backed document Q&A, PFS command-center feeds. This phase alone delivers the “cross-system queryable insight” operators say nobody offers — and it’s zero-risk because AppFolio remains the system of record. Exit test: staff and lenders routinely consume reports from the replica instead of AppFolio; every number on a replica report spot-checks against the AppFolio original; the 15-min incremental has run ≥30 days without silent divergence.

Phase 1 — Shadow ledger: replay history, diff to zero

Implement the Rust ledger core (§5 architecture: append-only, two-state, bitemporal, invariants, event projection). Replay the 2.58M GL rows as domain events; post them through the new ledger’s rules. Exit test: trial balance, per-property sub-ledgers, and bank-account balances diff to $0.00 against the mirror for every month 2015→present (the amortization work already proved this bar is reachable); three-way rec invariant holds continuously on replayed history; a full replay is deterministic and reproducible.

Phase 2 — Parallel-run: live dual-posting

Every new AppFolio transaction (via the 15-min incremental) auto-posts to the Rust ledger in near-real-time. Monthly close happens in both; owner statements and financials generated from both and diffed. Wire the first module-grade integrations: bank feeds (Plaid) into pending-state matching, Blue Moon lease data capture. Exit test: three consecutive monthly closes with $0.00 diff between systems, closed on the new ledger first; 1099 dry-run for the year matches or provably improves on AppFolio’s; the accountant/controller signs off that the new statements are the ones they’d hand a lender.

Phase 3 — First operational takeovers: the modules AppFolio monetizes worst

In order: (a) RUBS/utility billing (pure calculation, $38–61K/yr recaptured, charges still posted into AppFolio during transition); (b) maintenance/work orders (own intake with media + non-lossy AI triage + per-tech SLA metrics; staff-facing only at first); (c) comms layer (10DLC registered, consent-native, transactional first). Each module writes to the Rust ledger as truth and syncs summaries to AppFolio. Exit test per module: 60 days of staff using the new module exclusively without reverting; TCEQ-rule unit tests green on RUBS; zero dropped-detail work-order incidents (tested against AppFolio’s documented failure mode).

Phase 4 — Resident-facing cutover: portal + payments (the hard one)

Resident portal + $0-fee ACH rails (Plaid Auth + flat-fee originator), rent-flex scheduling built in, insurance-compliance tracking, Homebody-bar app experience. This is the sticky lock-in layer — plan re-enrollment of ~600 paying households as a managed campaign (staggered by property; the $0-fee pitch vs AppFolio’s $2.49 is the carrot; cash-pay/money-order path preserved for the El Paso workforce demographic). Exit test: ≥90% of previously-electronic payers enrolled and paying on the new rails at one pilot property for two full cycles; NSF/return handling proven through the pending→posted flow; delinquency no worse than the AppFolio baseline; then roll the remaining properties.

Phase 5 — Leasing + screening takeover, then decommission

Leasing funnel (ILS syndication partnerships, constrained-AI lead response, TU+Plaid screening with documented criteria and adverse-action provenance, Blue Moon e-sign). When the last module is live: full attachment/document export into LTM (the known AppFolio exit pain — grab everything before downgrading), then drop AppFolio to minimum/cancel. Exit test: one full leasing season (applications → move-ins) run end-to-end on the new stack; every legacy AppFolio attachment accounted for in LTM with checksums; final AppFolio statement reconciles to the Rust ledger to $0.00.

Only after Phase 4 is stable does productization deserve a decision — at which point the assets are: a proven parallel-run migration methodology (the product’s wedge), audited dual-book accounting (the moat challengers keep failing), $0-fee rails + rent-flex (the economics), and native MCP-openness (the differentiation Rentvine just proved the market wants). The forum evidence says lead with migration fidelity + accounting + price-lock, not features — and expect Yardi/RealPage/Entrata API tolls plus Propexo-class middleware (~$18–78K/yr) as the go-to-market cost of reaching customers on incumbent platforms.

8. Risks — Named Honestly

1. Data migration integrity. Attachments/documents are the biggest loss category in every migration horror story, and report-level export loses provenance (Far Out Solutions). Mitigation: the mirror covers structured data; run a dedicated attachment-harvest workstream (checksummed, into LTM) early, not at decommission time — AppFolio has no bulk export and documented no-restore data-loss cases.
2. Trust-accounting / regulatory compliance lands on Marc. Vendors currently absorb compliance-change monitoring (TCEQ RUBS rules, state trust rules, 1099 regime changes, TCPA). An owner-operator collecting own rent avoids the worst walls, but Texas trust rules, TX Fin. Code ch. 392 conduct rules on collections outreach, FCRA adverse-action mechanics, and 10DLC/TCPA are now internal obligations with real penalty exposure ($500–$1,500/message TCPA). Mitigation: compliance-as-code (unit-tested rules, consent as audited data), plus counsel review at Phase 3 (comms) and Phase 4 (payments/rent-flex — custody and lending perimeters specifically).
3. Payments risk transfer. Fee-model comps (Flex, Best Egg) exist because the lender model moves delinquency risk off the landlord; rent-flex keeps it. NSF/return operational handling, float, and fraud become AAMG problems. Mitigation: pending→posted ledger states are designed for exactly this; pilot one property; price flexibility from AAMG’s own delinquency curves.
4. Staff adoption and the labor market. Operators stay on incumbents because processes, training, and hiring are built around them — AppFolio is the labor-market standard (Reddit 1h7t2rh). 33 staff retrained on a bespoke system is a real cost, and every future hire needs onboarding no YouTube tutorial covers. Mitigation: module-by-module rollout with 60-day exit tests; keep UX conventions AppFolio-familiar where there’s no reason to differ; the −11pp AI-renewal finding argues for keeping humans reachable in every resident flow.
5. Bus factor / key-person concentration. The incumbents’ genuine advantage over any internal build: they exist independently of one person. A bespoke Rust ledger running 640 units of fiduciary money is critical infrastructure. Mitigation: boring technology at the edges, exhaustive replay-based tests, documentation as a first-class deliverable, and the mirror kept running indefinitely as an independent check even after cutover.
6. Scope gravity. The field data is unambiguous: challengers die on accounting depth, not feature count — and consolidation, not novelty, is what retains users. The temptation to build leasing AI before the ledger closes clean is the classic failure. Mitigation: the phase gates are ordered so the boring parts (ledger, close, NACHA, 1099s) block everything else — on purpose.
7. Incumbent countermoves. AppFolio could restrict the Reports API, change rate limits, or reprice tiers mid-build (it has form: eCheck monetization, NACHA removal). Mitigation: the mirror’s full history is already captured and independently stored; each phase reduces dependency; Phase 2 onward, AppFolio losing data access hurts less every month.
8. Productization is a different business. Practitioner forums are openly hostile to pitches; the “transparent pricing + good support” slot is taken (Rentvine/DoorLoop); distribution runs on fee shocks, NARPM referrals, and migration trust, not marketing (Reddit 1kipivk). Mitigation: AAMG-first is the validated strategy; treat any external sale as a separate venture decision with its own capital, compliance (money transmission the moment funds are collected for others), and integration-toll budget.

Keystone synthesis of the July 2026 research program. All source URLs inline; underlying workstream documents contain the full evidence base.

Appendix A — Top 10 Takeaways

1. The money is in the transaction layer, not software: AppFolio’s value-added services (payments/screening/insurance) run ~3.5x its subscription revenue, and Entrata’s 117% NDR is built on bundled transactional fees — any AAMG system that only replicates the ledger forfeits the economics, and any productization must plan payments/screening margins from day one.

2. Every incumbent shares the same architectural corner-cut: a mutable GL where integrity is a report you run, not a system property. None has immutable posted entries, bitemporal reconstruction, event provenance, or posting-time trust invariants — the fintech canon (Modern Treasury, TigerBeetle, Stripe) already solved this, and importing it is the Rust ledger’s entire differentiation.

3. Benchmark the ledger against Yardi Voyager, not AppFolio: Voyager-grade multi-entity, SoD-controlled, lender-trusted books are the acceptance bar — and dual-book (trust + corporate in one system) is the single most-requested capability no sub-Yardi platform offers; everyone runs an unintegrated QuickBooks side-car.

4. The 2.58M-row AppFolio mirror is a strategic weapon twice over: it neutralizes the ~$30K/3-month migration moat that protects incumbents, and it is the validation harness — shadow-replay AppFolio’s books through the new ledger and diff to $0.00 (feasibility already proven by the loan-amortization reconciliation) before any cutover.

5. API openness is the industry’s toll booth (Yardi ~$25K/yr/interface + 3-client prerequisite, Entrata $5K–$50K/yr, RealPage per-customer certification, AppFolio Max-tier writes) and simultaneously the most-requested missing feature at exactly 640-unit scale — radical customer-owned openness is the one position incumbents structurally cannot copy.

6. The market just validated Marc’s architecture from both ends: Rentvine shipped the industry’s first native MCP server (May 2026) and Yardi’s Virtuoso uses Claude via MCP — ‘PMS as agent-accessible data platform’ is where the industry is converging, and mirror→Postgres→LTM→agents is already that.

7. Payment rails are the incumbent’s soft underbelly: AppFolio’s $2.49 eCheck fee and NACHA removal are the single biggest documented switching trigger; $0-fee ACH at wholesale (~$0.25 flat) under an owned ledger beats the incumbent resident experience instantly — but resident-side re-enrollment of ~600 households is the genuinely hard part of any exit, so plan it as a staged campaign with a pilot property.

8. Build-vs-buy follows the licensing wall, not feature count: build the thin deterministic/LLM layers over mirrored ledger data (RUBS saves $38–61K/yr under Texas’s no-markup rule, payments orchestration, pre-delinquency outreach, constrained leasing AI, reporting) and buy every regulated core (screening data via applicant-pays TU + Plaid, insurance master policies, payment rails, post-move-out collections on contingency). Blue Moon/TAA e-sign integration is mandatory for Texas.

9. Pricing algorithms are radioactive unless single-tenant: the DOJ-RealPage consent decree (no pooled nonpublic competitor data, 12-month-old training data, state-level granularity only) plus 40+ state bills define the safe harbor — own-data-only pricing tools are what the market now wants, and rent-flex as landlord-controlled scheduling (not lending) cleanly avoids both the money-transmitter and consumer-lending perimeters that force Flex’s line-of-credit structure.

10. Sequence ruthlessly and validate AAMG-first: replica dashboards → shadow ledger diffed to $0.00 → parallel-run closes → RUBS/maintenance/comms takeover → resident payments → leasing, each with a hard exit test — because the field evidence shows challengers die on accounting depth (deposit segregation, NACHA, 1099s), users stay for consolidation not features, and practitioner forums are hostile to unproven products; productization is a separate later decision whose wedge would be migration fidelity + audited accounting + price-lock.

Appendix B — Build vs Buy Map

Appendix C — Adversarial Review

Verdict: Directionally sound and unusually well-sourced for a synthesis doc — 7 of 9 spot-checked load-bearing claims verified against primary sources (AppFolio Q3’25 $192.09M VAS vs $53.75M core per the 10-Q; Entrata S-1 filed 5/28/26 at ~$575M ARR, 117% NRR, 97% GRR; Rentvine MCP at Be Herd May 2026; EliseAI $250M @ $2.2B Aug 2025; DOJ-RealPage settlement terms incl. own-data-only rule; RealPage-Livble acquisition July 2025; AppFolio $2.49 eCheck fee from 7/31/2023). However, it is NOT yet decision-grade in three places: (1) the flagship “strongest pure-build” recommendation (RUBS) cites the WRONG Texas regulator — submetering/allocation rules moved from TCEQ to the PUCT in 2014 (16 TAC ch. 24 IS a PUC chapter), so the roadmap’s “TCEQ-rule unit tests” would encode the wrong agency’s rulebook; (2) the $0-fee ACH pillar is silent on Nacha origination compliance (WEB debit account validation, return-rate thresholds, processor underwriting) — “rails at cost” is not just a pricing decision; and (3) the field table omits MRI Software, a top-4 enterprise incumbent, while presenting itself as “the field in one table.” Several pricing/market-share figures trace to vendor marketing or middleware-vendor blogs and should be downgraded to “unverified vendor claim” before anyone quotes them. Compliance honesty overall: better than typical (trust accounting, FCRA adverse action, TCPA per-message exposure, money-transmission perimeter, and DOJ pricing decree are all named with mitigations), but counsel gates arrive at Phase 3/4 while some obligations (TX security-deposit statute, FCRA user obligations at first TU pull, Nacha rules at first origination) attach earlier in the roadmap.

Gaps found:

• MRI Software is entirely absent — a top-4 enterprise PMS (Yardi’s main enterprise rival, large affordable/commercial footprint, owns multiple SMB brands). A field table without MRI is incomplete; Yardi Breeze/Breeze Premier (Yardi’s direct AppFolio competitor at exactly 640 units) is also never evaluated as an option.
• Nacha/ACH-origination compliance is missing from both §6 and §8: building ‘$0-fee ACH at ~$0.25 wholesale’ makes AAMG an ACH originator under a processor/ODFI relationship — WEB debit account-validation rule, unauthorized-return-rate thresholds (0.5%), and processor underwriting/onboarding all apply. The dossier treats rails as purely a price decision.
• Payments category is thin on incumbent comps: Zego (PayLease) and the utility-billing vendors the RUBS build displaces (Conservice, Livable, NES) are never named — so the claimed $38–61K/yr RUBS savings has no visible vendor-price baseline to check against.
• Texas security-deposit law (Tex. Prop. Code ch. 92 — 30-day return, itemization, bad-faith penalties) is never mentioned; the trust-accounting discussion is generic ‘state trust rules.’ For an owner-operator holding its OWN residents’ deposits, ch. 92 is the binding regime, and the dossier never draws the owner-operator vs third-party-PM distinction precisely on deposits.
• Fair-housing/disparate-impact exposure of rent-flex is unaddressed: the dossier covers discrimination risk in screening (SafeRent) but not in deciding WHICH residents are offered payment flexibility — an eligibility algorithm trained on AAMG’s own delinquency history is exactly the pattern that creates disparate-impact claims; ECOA/Reg B also applies if rent-flex is characterized as credit (only a generic ‘verify with fintech counsel’ nod exists).
• PCI-DSS scope never mentioned — resident portals in practice take cards; if Phase 4 is ACH-only that should be stated as a deliberate scope decision.
• FCRA ‘user’ obligations at AAMG’s end (permissible-purpose certification to TU, state screening-fee caps, records retention) attach at the FIRST screening pull in Phase 5, but counsel review is only gated at Phases 3–4.
• BaaS/fintech-rails counterparty risk (the 2024 Synapse collapse and FBO-account reconciliation failures) is unmentioned despite recommending Dwolla/Moov/Stripe-class rails for ~600 households’ rent — the ledger-vs-bank reconciliation lesson from Synapse is directly relevant to the dossier’s own thesis.
• No open-source/self-hosted PMS scan (even to dismiss the category) — for a build-it-yourself dossier, one paragraph establishing that nothing credible exists would strengthen the build case.
• Rent Manager, ResMan, Propertyware rows rest on older/quote-only pricing with no 2026 verification — acceptable as ‘directional’ per the preamble, but the table doesn’t flag which rows are stale.

Claims flagged for re-verification:

• ‘TCEQ RUBS rules’ / ‘TCEQ-rule unit tests green’ (§6, §7 Phase 3, §8.2) — WRONG AGENCY. Texas submetering/allocation jurisdiction transferred from TCEQ (30 TAC ch. 291) to the Public Utility Commission of Texas in July 2014; the dossier’s own citation, 16 TAC §24.283, is a PUC rule (Title 16 = PUC’s title). The compliance-monitoring plan for the strongest pure-build recommendation points at the wrong regulator.
• ‘DoorLoop: $182M raised’ — most primary sources (DoorLoop’s own blog, Calcalist, Bisnow) put total funding at ~$130M after the Oct 2024 $100M Series B; the $182M figure appears only on Tracxn and is uncorroborated. Likely inflated by ~$50M.
• ‘AppFolio’s own $8.75M in FCRA actions’ — the verifiable FTC settlement was $4.25M (Dec 2020); the $8.75M is an unsourced aggregate (presumably adding a private class settlement) presented as a single figure. Should be broken out or cited.
• ‘Rentvine shipped the industry’s FIRST native MCP server’ — Rentvine’s own PR scopes the claim to ‘first in the single-family rentals industry’; the dossier broadens it to the whole PM industry. Vendor claim, overstated in transcription. Relatedly, ‘Yardi’s Virtuoso now uses Claude via MCP’ rests solely on usehaven.ai, an AI-content marketing site — weak sourcing for a market-validation claim.
• ‘AppFolio… 9.5M units’ — the Q3 2025 10-Q reports 9.1M units under management (+7% YoY); 9.5M by Q1’26 is possible but ahead of any figure verified here. Minor, but it’s in the field table.
• Yardi ‘$25K/yr per interface’ and ‘>50% of Fannie-financed MF units’ — sourced respectively to Truto (a middleware vendor selling around exactly this problem) and bitscale.ai (an AI directory). Both are secondary sources with commercial incentive; neither is Yardi-published. Directionally believable, not quotable.
• CAM ‘~40% material error rates and $5–15B/yr leakage’ — sole source is PredictAP, a vendor whose product monetizes that exact claim. Marketing statistic dressed as a market fact.
• EliseAI ‘~10% of US apartments’ — appears in no independent funding coverage checked; company-marketing figure. Similarly the ‘−11pp renewal penalty’ (Propmodo) is a single study doing double duty as evidence in §3 and §8.4 — real, but the dossier leans on it as if replicated.
• ‘DOJ RealPage decree = free design spec’ — accurate in substance (Nov 24, 2025 settlement; own-data-only, no nonpublic competitor data, state-level-only geography), but it is a PROPOSED consent decree requiring court approval with a 7-year term; the dossier states it as final.
• Propexo-class middleware ‘~$18–78K/yr’ (§7) — no source given anywhere in the dossier; every other price figure is linked, this one is bare.