Your product reached the final set in a competitive slot and was not selected. The capability read was close - close enough that every deciding factor sat outside the product's function. This operator manages on behalf of multiple owners across more than one property management system, which raises the evidentiary bar in two specific ways: they require demonstrated performance in an environment resembling their own, and a security posture they can pass through to owners without qualification. Neither was available at the time of assessment. Two of the three gaps are closable on a known timeline. The third is a product decision, and it is the one that would change the outcome rather than narrow the margin.
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.
The selected alternative was another purpose-built conversational leasing platform, with published deployments across multiple property management systems and a completed attestation. It did not win on conversational quality, where the read was at parity. It won on evidence.
| Axis | How it read |
|---|---|
| Conversational quality | ParityNeither side established an advantage. This is no longer a differentiating axis in this category. |
| Action on the outcome | AlternativeWins. Write-back into the leasing system of record carried the labor case. |
| Multi-system evidence | AlternativeWins on published deployments in mixed estates. |
| Security attestation | AlternativeWins on a completed attestation against your in-progress one. |
| Pricing transparency | YouWin. Your published pricing was the clearest in the set and shortened your path to the final round. |
The selected alternative's commercial terms 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.
Across operators, the requirement in this category has moved. The question is no longer whether an agent can hold a conversation - operators broadly accept that it can - but whether it can complete the transaction without returning work to the site team. Operators who deployed answer-only agents consistently report that the labor saving did not materialize, and that finding is now shaping how the capability is specified before any vendor is shortlisted.
Read against your own result, this is the more important half of the report: the axis you were read Behind on is the axis the category is standardizing around. It is not a preference of this one buyer.
Two of the three gaps are proof and disclosure. One is product. The security attestation and the performance documentation are both evidentiary; neither requires a roadmap change, and neither reflects a limitation of what you have built. Write-back scope is architectural, and it is the item that would change the outcome rather than close the margin.
The single upgrade trigger: a completed Type II attestation plus two referenceable deployments in a mixed-system estate at comparable scale. On that evidence alone this evaluation reaches a different final set, because the capability read was already close enough that nothing else had to move.
This outcome is recoverable. It reflects the state of your evidence in Q2 2026, not a settled judgment about product fit for this buyer profile.
None of this is a route to a better score. It is the set of conditions under which a buyer with this profile reaches a different conclusion on its own evidence.
Your product line has reached the final set in each of its recent appearances in this category. The deciding axis has been evidentiary every time - a different gap on each occasion, but always documentation rather than function. That consistency is the finding, and it is a better one than a win rate: your product is competitive on capability in this category and is being decided against on proof. That is a fixable class of problem, and it is not the class of problem most vendors receiving this outcome assume they have.
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.