Keep the platform-bundled maintenance module.
The specialist is better at the technician’s daily job. The incumbent still wins because the capability gap is smaller than the structural cost of closing it.
The operating model makes connection burden unusually consequential.
This is a composite prospect artifact, not a client deliverable. The methodology, section structure, scoring framework, confidence rationale, and Capabilities Taxonomy service lines are production; the operator and vendor profiles are composite or anonymized.
| Parameter | Composite operator |
|---|---|
| Markets | Texas ~45% (34 communities) · Midwest ~35% (27) · Mountain West ~20% (15) |
| Asset mix | 50 Class B garden value-add · 17 Class A mid-rise · 9 Class C stabilized |
| Operating model | Hybrid - 47 communities owned, 29 fee-managed for four institutional owners |
| Organization | No CIO or CTO. CFO owns the technology budget by default; VP Operations is de facto systems owner. Two IT staff and one helpdesk contractor handle infrastructure only. Seven regional managers. Five-person centralized leasing pod covers 22 communities. No vendor management function. |
| Incumbent stack | One core property management platform, nine years in place, renewed twice without competitive review. 38 point solutions outside it; five overlapping pairs from a 2023 acquisition; three auto-renewing contracts no current employee has read; one vendor paid monthly for 14 months with zero active users. |
| Technology spend | ~$5.5M · $282/unit/year · $23.50/unit/month |
The incumbent wins on structure, not capability.
MFC recommends keeping the maintenance module bundled with the core property management platform. Confidence: 93%.
Three alternatives plus one disqualification
The strongest category specialist is genuinely better at the technician’s daily workflow. An adjacent facilities suite was removed before scoring because of ecosystem risk.
The structural cost overwhelms the capability gain
The specialist adds roughly $531,400 a year plus about $85,000 once, along with a permanent two-way connection and owner-reporting dependency.
The Midwest gap is not primarily a software signal
The same tool produces 3.1-day performance in Texas and 4.8 days in the Midwest. Staffing and building age are the more likely variables.
Maintenance is fully embedded in the core platform today.
There is no separate maintenance contract or invoice. The module was switched on with the platform nine years ago and is used portfolio-wide.
| Current-state dimension | Read |
|---|---|
| Deployment | All 76 communities and 19,500 units. Every regional manager, every onsite maintenance technician, and two centralized service coordinators use it. |
| Core platform spend | $1.42M/year · $6.07/unit/month. |
| Maintenance incremental spend | $0 - bundled into the platform license. |
| Directional module allocation | ~$0.85/unit/month, or ~$198,900/year, estimated by MFC from unbundled pricing in other markets. This is not a confirmed cost and would not be recovered by removing the module. |
| Contract posture | Three-year platform agreement, renewed twice without competitive review. Notice to avoid automatic renewal is due 90 days before the next renewal. |
This is a validation question, not a broken-system problem.
Two regional managers independently asked whether a dedicated maintenance product would fix completion times. Neither was complaining about the current system; both were asking whether something better exists.
Are we leaving something on the table?
A switch recommendation has to show that a specialist would actually close the Midwest performance gap - not simply demonstrate a better interface.
The regional gap points away from the tool
The Midwest portfolio is older, was acquired in 2023, and has roughly double the technician vacancy rate. The same software performs better elsewhere.
The category has settled into three operating shapes.
Adequate capability, structural advantage
Work order, unit, resident, technician, and ledger data sit together. Nothing has to be synchronized between products.
Best visible innovation
Mobile-first technician workflows, AI request triage, and vendor dispatch networks. The trade is permanent connection ownership back to the core platform.
Broader asset-management depth
Maintenance becomes one module inside a larger facilities/capital planning environment, usually for operators with deeper preventive maintenance needs.
Keep the platform-bundled incumbent.
The recommendation rests on what the incumbent does structurally well for this operator - not on dismissing genuine specialist strengths.
One database, no synchronization
Work orders, residents, units, labor and expenses stay in the same system. For a 76-community operator with two IT staff, that is the reason the data is trustworthy today.
Fee-managed reporting stays native
Twenty-nine communities report to four institutional owners through the core platform. Maintenance activity reaches those reports automatically.
Nine years of linked operating history stays usable
Work-order, vendor, unit-level repair and ledger history remains fully linked. Exporting the history would not preserve those relationships in a meaningful way.
No new standing connection obligation
With only two IT FTEs and one helpdesk contractor, every connection consumes scarce operating capacity. The incumbent creates none.
The specialist wins capability. The incumbent wins the operator-level decision.
Four candidates were evaluated. One was disqualified before scoring on ecosystem grounds.
| Candidate | Capability profile |
|---|---|
| Platform-Bundled Incumbent | Adequate functional coverage. Dated technician mobile experience. No AI triage. No vendor dispatch. Zero connection surface. No incremental license cost. |
| Category Specialist | Strongest technician mobile experience. AI triage. Built-in outside vendor dispatch marketplace. Requires a maintained two-way connection. |
| Integrated Challenger | Strong workflow design and good reporting. Published operating references concentrated below 8,000 units; thin proof at this portfolio’s scale. |
| Adjacent Facilities Suite | Maintenance bundled with capital planning and preventive maintenance. Disqualified before scoring. |
Dimension comparison
| Dimension | Platform-Bundled Incumbent | Category Specialist | Integrated Challenger |
|---|---|---|---|
| Technician experience | Dated; more steps; functional. Confirmed | Best in category; photo capture, offline mode, parts lookup. Verified vs. two references | Good; cleaner than incumbent, behind specialist. Claimed · no scale reference |
| AI triage of requests | None; coordinator routes requests. Confirmed | Present; majority-routing figure vendor-reported. Claimed | Rules-based routing only. Confirmed |
| Outside vendor dispatch | None; phone/email. Confirmed | Built-in marketplace; strong Texas coverage, thinner Mountain West. Confirmed | None. Confirmed |
| Connection burden | None; same database. Confirmed | Two-way connection required; standard connector exists. Confirmed | Two-way connection required; custom build. Confirmed |
| Fee-managed owner reporting | Native; no extra work. Confirmed | Depends on connection availability. Confirmed | Same dependency, on custom connection. Confirmed |
| Nine years of history | Retained, fully linked. Confirmed | Exportable; linkage does not survive. Confirmed | Same. Confirmed |
| Security/compliance | SOC 2 Type II current. Confirmed | SOC 2 Type II current. Confirmed | SOC 2 Type I; Type II in progress. Claimed |
| Proof at this scale | Nine years of operator history. Confirmed | Two references above 15,000 units; both single-market. References contacted | None found above 8,000 units. Absence confirmed |
| Annual cost | $0 incremental. Confirmed | ~$491,400 license + ~$40,000 connection maintenance. Estimated | ~$374,400 + custom connector. Estimated |
| One-time switching cost | None. | ~$85,000 connector + migration. Estimated | Higher custom connector; not quoted. |
A Keep creates no savings against today. It avoids a costly change with no proven operating return.
The confirmed position
| Line | Amount | Basis |
|---|---|---|
| Core platform license | $1,420,380/year · $6.07/unit/month | Confirmed - executed agreement |
| Maintenance module incremental cost | $0 | Confirmed - bundled |
| Recommended annual cost | $0 change | Confirmed |
| Projected annual delta | $0 | Delta Data Confidence: Not Applicable - Keep / No Change |
What keeping avoids
| If the operator switched to the Category Specialist | Amount |
|---|---|
| License · 19,500 units at ~$2.10/unit/month | $491,400/year · Estimated vendor quote |
| Maintain two-way connection | ~$40,000/year · Estimated |
| Ongoing total | ~$531,400/year · $2.27/unit/month |
| Connector build + data migration | ~$85,000 one time · Estimated |
| Five-year total | ~$2,742,000 |
At roughly 106,800 work orders per year, the specialist premium is about $4.98 per work order for a better technician app, AI request routing MFC could not independently verify, and a vendor dispatch network strongest in the region already performing best.
Keeping is actively correct for this operator - not merely cheaper.
The risks of keeping are real - they simply compound more slowly than the risks of switching.
The specialist gap will widen
Technician mobile experience, AI triage, and vendor dispatch are real areas of specialist investment. Today the gap does not justify the trade. In two or three years it may.
Technician recruitment and retention
The Midwest region has roughly double the vacancy rate. MFC found no evidence that the incumbent UI causes turnover, but the operator has never asked technicians directly.
The Midwest diagnosis is inferred
Staffing and building age are the more likely variables, but that conclusion has not been directly proven. If staffing reaches parity and performance does not improve, the analysis must be reopened.
Renewal leverage is weak
A third consecutive platform term without competitive review would leave the operator with less pricing leverage, even if keeping maintenance remains correct.
Keep the platform-bundled maintenance module. Confidence: 93%.
The incumbent did not win by default and did not win on capability. It won because closing the capability gap would create substantial annual cost, one-time cost, connection ownership, and fee-managed reporting risk that do not pay for this operator today.
The core platform stays
This recommendation is architecture-dependent and is void if the core property management platform is replaced.
The Midwest gap responds to staffing
If completion times do not improve after vacancy rates reach parity with the other regions, maintenance technology returns to the table.
The vendor keeps investing
If the roadmap stalls while the specialist tier continues to move, the trade changes.
How to act on this
Brief the regional managers and test the staffing hypothesis with vacancy, time-to-fill and completion-time data.
Get a written 24-month product roadmap and survey technicians directly.
Maintenance is downstream of the core platform decision and should not be evaluated separately.
Agreement renews 31 Oct 2027; notice due 2 Aug 2027. Begin competitive platform review no later than Feb 2027.
The recommendation depends on an architecture decision that has not been made.
The module has no separate contract, no separate price, and no standalone architecture. Every argument for keeping it - one database, native owner reporting, zero connection burden, nine years of linked history - holds only while the core platform holds.
- If the core platform is replaced, this recommendation is void, not merely weakened.
- The maintenance module should never be evaluated alone; its economics cannot be separated cleanly from the platform bundle.
- The service line’s decision window is governed by the platform renewal date: 31 October 2027, with notice due 2 August 2027.
- The platform has been renewed twice without competitive review; a review is recommended separately.
Close the specific evidence gaps that hold confidence at 93%.
Confidence gaps, tracked
| # | Priority | Action | Data needed | From | Owner | Due |
|---|---|---|---|---|---|---|
| 1 | High | Test the staffing hypothesis for the Midwest gap | Vacancy rate, time-to-fill, overtime by region vs. completion times | HR + operations | Regional Manager - Midwest | 2026-09-30 |
| 2 | High | Get the module roadmap in writing | 24-month commitments with dates for mobile, AI triage, vendor dispatch | Core platform vendor | VP Operations | 2026-10-15 |
| 3 | Medium | Ask technicians directly | Anonymous survey across all 76 communities | Internal | VP Operations | 2026-11-30 |
| 4 | Medium | Price the module | Unbundled module pricing for renewal preparation | Core platform vendor | CFO | 2027-02-28 |
| 5 | Medium | Price the alternative properly | Fixed-price connector + migration quote | Implementation partner | Director of IT | 2027-02-28 |
| 6 | Low | Close the reference gap | One specialist reference above 15,000 units in a multi-market portfolio | MFC vendor intelligence | MFC | 2026-12-31 |
Operational next steps
| # | Action | Owner | Due |
|---|---|---|---|
| 7 | Brief the two regional managers who raised the question, with the comparison table | VP Operations | 2026-09-05 |
| 8 | Record the Keep decision and its three conditions where the next reviewer will find them | VP Operations | 2026-09-15 |
| 9 | Open the core platform competitive review | CFO | 2027-02-28 |
| 10 | Calendar the 2 August 2027 renewal-notice deadline with a 120-day advance alert | CFO | 2026-09-15 |
Confidence - full rationale
Strong operator-specific structural proof
Nine years of operating history, contractual zero incremental cost, alternatives priced and compared, specialist references contacted, and a structural argument that does not depend on vendor claims.
Thin standalone evidence
No standalone module price; Midwest causality inferred rather than measured; AI triage unverified; forward roadmap unknown; technicians have never been asked directly.
Close items 1-5
Staffing evidence is the biggest lever. A stalled roadmap could also lower confidence - which is the intended behavior of an honest instrument.