Back to StackSmart for Vendors & Suppliers
StackSmart
Market Signal Report
VMIP Sample
Confidential
What this is. A Market Signal Report is the per-evaluation intelligence a VMIP subscriber receives every time their product appears in a live PMC StackSmart evaluation, including evaluations the vendor never knew were running. This sample is the report a vendor almost never gets to see: a displacement win, in which the operator moved off an embedded incumbent and the reason had nothing to do with the feature comparison. This is an anonymized sample - the operator and the vendor are both de-identified.
Evaluation · Q2 2026
Revenue Management and Pricing Intelligence Recommended
Outcome type: Displacement; embedded incumbent replaced Decision character: Decisive
Operator Anonymized 20,000-40,000 units Institutional owner-operator Multi-region Conventional PMS, middleware-tolerant Reliability-led replacement

Why you won the evaluation

The incumbent's recommendations were not being followed. A pricing system that gets overridden is not a pricing system, and that is what decided this.

The incumbent here was fully deployed, fully paid for, and largely ignored below the regional level. Site teams overrode a substantial share of daily recommendations because the system could not explain them, and the revenue team had no way to separate a good override from a bad one. So this was never a feature comparison. It was a question about whether the operator could obtain a pricing system its own people would actually operate. Explainability was the axis, and it is the axis you won on - decisively, and against a considerably deeper product.

Evaluation scorecard

Recommendation explainability at the decision pointAhead
Site-team adoption in comparable deploymentsAhead
Data architecture and regulatory postureAhead
Portfolio-level forecast accuracyAt parity
Migration and change-management recordCompetitive
Depth of asset-management reportingBehind

Read scale, per dimension: Ahead · Competitive · At parity · Proving · Behind · Not yet. A dashed Not yet marks an absence of evidence in MFC's record, not a judgment about your product. No dimension carries a score, a rank or a percentile.

Capabilities that drove the decision

How you compared

The alternative was the retained incumbent: a long-tenured, market-standard revenue management system, deeply embedded, contractually committed, and materially deeper than you on reporting. It lost anyway.

AxisHow it read
ExplainabilityYouWin decisively. This axis carried the evaluation.
Team adoption in practiceYouWin. Override rate was the operator's own evidence, not a vendor claim.
Asset-management reporting depthIncumbentWins clearly. The operator accepted a real reduction here to get a system that would be used.
Non-public pooled data postureYouWin on an axis that did not exist in this category three years ago.
Switching cost and continuity riskIncumbentWins structurally. Your migration record was the counterweight, not a reversal.
Forecast accuracyParityNeither side could demonstrate a durable advantage at this portfolio scale.

The incumbent's contracted rate at this operator is not a fact MFC may disclose to you, and the operator's cost comparison between the two products is not reported here. Where MFC knows a competing commercial term only in confidence, MFC names the absence rather than the term.

Peer and industry signal

Aggregated operator experience

Across institutional operators who have replaced a legacy revenue management system in recent quarters, the reported failure mode is consistent - and it is not accuracy. It is override. Operators describe recommendations their teams did not trust and could not interrogate, and they describe post-migration satisfaction that tracks explainability rather than model sophistication.

This is what moved the weighting toward explainability in the first place. It exists in MFC's engagement record rather than in any public source, and it is the most commercially useful thing in this report: the deciding criterion in your category has shifted, and the vendors still selling on model quality are answering a question buyers have stopped asking.

What carried it

✓ The condition under which you displace an incumbent

You win a replacement when the incumbent is installed but not operated. Override rate, not satisfaction score, is the leading indicator - and it is visible to the operator before it is visible to you. Where the incumbent's recommendations are being followed, MFC's evaluations in this category do not reach a replacement decision at all, whatever the feature comparison shows. That is your qualification test, and it is a sharper one than portfolio size or contract renewal date.

What would strengthen your representation

★ Future evaluations of this buyer profile
  1. This quarterPublish your parallel-run migration methodology as a documented artifact. It answers the one objection that recurs in every appearance you make in this slot, and it currently has to be surfaced by a buyer asking the right question.
  2. Then, low-effort proofDocument override-rate reduction from an existing deployment. You won on this axis without being able to quantify it; the operator quantified it for you from their own environment, which will not always happen.
  3. Then, the product investmentClose the asset-management reporting gap. It is the one axis where you were read Behind, and it is the axis on which an owner-side stakeholder, rather than an operations stakeholder, will challenge this decision later.

Across recent evaluations

Cross-evaluation pattern

You have appeared in every evaluation MFC has run this year in which a legacy revenue management incumbent came under review. Explainability and team adoption have been the deciding axis in each. Where the incumbent's recommendations were being followed, the evaluation did not reach a replacement decision - so the pattern tells you the qualifying condition for your own pipeline more precisely than a win rate could: the buying signal is override behaviour, not dissatisfaction.

Neutrality, anonymization and evidence basis

Anonymization. Generated from a real PMC StackSmart evaluation, anonymized to protect operator identity. Peer-sentiment signals are aggregated across multiple operators and de-identified; no operator is named or identifiable, and MFC will not confirm or validate any inference about operator identity.

Recommendation independence. StackSmart recommendations are produced by a data-driven engine that carries zero vendor payment input. A VMIP subscription has no influence on PMC-client assessment outcomes. The actionable items in this report describe what would strengthen your standing in future real-world evaluations - product intelligence you pay to see, never a better score you pay to get.

Evidence basis. Tier A evidence is MFC's independent StackSmart evaluation record. Self-reported figures are labeled and require independent verification. Any dollar figure shown is the vendor's own published list price.

NDA designation. Where a finding here rests on information you provided to MFC under NDA - a diligence call, a document you supplied, or your answers to NDA-gated questions in StackSmart - it is marked (gathered under NDA). MFC applies the same protection in reverse: no other vendor's NDA-gathered information appears in this report, and where a competing fact is known to MFC only in confidence, MFC names the absence rather than the fact.

Prepared by. Multifamily Consortium · Vendor Market Intelligence Program. Questions: Johnny Giangregorio, Head of Vendor & Supplier Partnerships.

SAMPLE · MODELLED ON LIVE EVALUATION STRUCTURE · OPERATOR AND VENDOR DE-IDENTIFIED · PEER SENTIMENT AGGREGATED