Renewal management existed at this operator as a calendar reminder, a rent-increase matrix in a spreadsheet, and the judgment of individual site managers. There was no tool to displace and no incumbent to unseat, which changes what wins: with no baseline to beat, the deciding question became implementation risk rather than capability ceiling. Two of the three alternatives assessed required the operator to stand up a reporting warehouse before any model could run. You did not. The recommendation is data-gated rather than decisive, and it carries a proof condition set out below.
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.
Two alternatives reached assessment: the renewals module native to the operator's own platform, and an enterprise retention-analytics product built for larger, warehouse-equipped estates.
| Axis | How it read |
|---|---|
| Time to first output | YouWin against both. The native module has no risk model; the enterprise product needs a warehouse. |
| Rent-increase workflow | Native moduleWins. It is already wired into the lease renewal process the operator uses. |
| Analytical depth | Enterprise productWins on model sophistication, at a prerequisite the operator will not fund this cycle. |
| Explainability to site teams | YouWin. Reason codes rather than a score. |
| Proof at this portfolio band | UnresolvedNone of the three could evidence outcomes at this scale in this segment. |
Commercial terms for both alternatives are not publicly disclosed and are not reported here. Where MFC holds a competing figure only in confidence, MFC names the absence rather than the figure.
Your product line has not yet appeared in enough live StackSmart evaluations for MFC to hold aggregated operator experience on it. That absence is a gap in MFC's evidence base, not a negative signal about your product, and it closes as engagements accrue. MFC will not manufacture a peer read it does not have.
What MFC can report at category level: renewal intelligence is increasingly assessed inside the annual budget cycle rather than as a standalone software purchase. That compresses the window in which a vendor can be evaluated at all, and it rewards products that can be trialled without a preceding data project - which is the structural reason you are in this report.
You win the empty slot at mid-size operators when the alternative to you is not another vendor but doing nothing for another year. Against that alternative, speed to first output beats model quality, and transparent pricing beats a better discount. Your risk in this profile is the reverse case: where the operator already has a warehouse and an analytics team, your sequencing advantage disappears and you are compared on depth, where you do not currently lead.
This is your product line's first appearance in a live StackSmart evaluation in this category, so there is no cross-evaluation pattern to report yet. This section populates from your second appearance onward and becomes the most durable intelligence in the report - the recurring axis across buyers, which no single evaluation can show you.
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.