# PRISM competitive strategy brief

> *AI-generated recommendations for discussion. These are not Nick’s recommendations or approved JLL/PRISM guidance.

**Recommendation: explore financial follow-through for operators with substantial chargeback pain. The case depends on customer demand and a demonstrated improvement over their current process.**

## Market position

Cove and Visitt both span building operations, tenant experience and AI. Cove emphasizes consolidation, a configurable building experience and implementation support. Visitt emphasizes service outcomes, frontline AI assistance and connected operations. These are differences in commercial emphasis, with substantial feature overlap. [Cove and Visitt GTM comparison](https://crefieldnotes.com/gtm-and-ui-brief.html)

The competitive question is how PRISM delivers a better outcome for a particular buyer. Public screenshots and selected reviews do not establish a universal winner. Visitt's enterprise rollout reference, detailed billing controls and modern tenant app are material counterevidence to an overly narrow competitor description. [BGO announcement](https://bgo.com/press-release/bgo-properties-and-visitt-announce-national-strategic-partnership-to-power-ai-driven-operations?hs_amp=true) · [Visitt billing guide](https://help.visitt.io/en/articles/9357580-billing-management) · [Visitt tenant guide](https://help.visitt.io/en/articles/16891940-getting-started-with-visitt-a-guide-for-tenants)

## Recommended PRISM priorities

| Priority | Recommendation | Evidence needed to proceed |
|---|---|---|
| Broad market message | Test “Make every building run to your standard,” supported by real examples of coordination, field execution and portfolio oversight. | Buyers understand and value the promise; the offered PRISM configuration demonstrates it. |
| First commercial experiment | For operators with material chargeback pain, test completed-service omissions and accounting exceptions. | Controller-confirmed unmet need; reliable source records; incremental benefit over the incumbent and current manual process. |
| Delivery foundation | Validate field capture, data readiness, migration and exception ownership. | Engineers complete the work; records survive retries and reconnection; finance can trace the result. |
| Later opportunities | Evaluate maintenance follow-through and compliance handoffs when a narrower customer problem is established. | A distinct outcome and buying sponsor; evidence of incremental value in an already competitive category. |

The broad research report ranks operational readiness first for a general entrant. The PRISM playbook ranks financial follow-through first as a PRISM-specific commercial test, with readiness as its foundation. These recommendations have different scopes. **This brief is the starting point for the PRISM discussion.** [Market messaging](https://crefieldnotes.com/prism-market-messaging.html) · [PRISM deal playbook](https://crefieldnotes.com/prism-market-wedge-playbook.html)

## Head-to-head implications

**Against Cove:** tenant experience and implementation support may matter as much as the finance workflow. Its customer references describe consolidation and close deployment support. A finance demonstration is useful only when finance influences the buying decision. [Longfellow customer story](https://cove.is/customer-story-longfellow-real-estate-partners)

**Against Visitt:** the strongest comparison would follow completed field work through to its accounting outcome. Visitt already describes charge review, approvals, accounting queues and error handling. A queue or AI label is insufficient differentiation. Its billing guide separates verification from queuing for synchronization; A useful PRISM distinction would be detecting omissions or resolving exceptions with less effort. [Visitt billing product page](https://visitt.io/billing) · [Billing instructions](https://help.visitt.io/en/articles/9357580-billing-management)

**For PRISM:** the proposed revenue-assurance agent remains a hypothesis. PRISM's Yardi guide distinguishes an unposted/open accounting batch from downstream posting. Readback and reconciliation remain evidence gaps for the proposed financial-outcome claim. [PRISM and Yardi setup guide](https://buildingengines-prism.zendesk.com/hc/en-us/articles/34455212272155-Prism-and-Yardi-Technical-Setup-Guide)

## Questions that could change the recommendation

- Is chargeback reconciliation a significant buying problem for the target customer? Multi-property office operators on Yardi are a proposed starting segment, not a validated target.
- Which parts can the offered PRISM configuration demonstrate today, and which rely on setup, manual work or a prototype?
- Would comparable customer cases show an improvement over the incumbent, including corrections, non-billable work and pending accounting states?

The principal missing evidence is internal: current capability proof, comparable pricing and implementation scope, buyer-specific win/loss reasons, and controller-labeled customer cases. Public research cannot establish these for PRISM. [Open questions and evidence gates](https://crefieldnotes.com/report-readiness.html)

## Reading routes

| Audience | Next destination | Purpose |
|---|---|---|
| Leadership and strategy | [PRISM deal playbook](https://crefieldnotes.com/prism-market-wedge-playbook.html) | Segment, proposed wedge, pilot and stopping conditions |
| Sales and marketing | [GTM comparison](https://crefieldnotes.com/gtm-and-ui-brief.html) and [market messaging](https://crefieldnotes.com/prism-market-messaging.html) | Competitor motions, discovery and proposed copy |
| Product and design | [Cove reservation](https://crefieldnotes.com/ui-task-journeys.html#cove-amenity-reservation) and [Visitt reservation](https://crefieldnotes.com/ui-task-journeys.html#visitt-amenity-reservation) → [58-task reference](https://crefieldnotes.com/ui-user-flow-team-reference.html) → original images | Answer product questions, compare documented workflows and inspect original evidence |
| Research and data teams | [Claim register](https://crefieldnotes.com/knowledge-base.html) and [knowledge-base guide](https://crefieldnotes.com/knowledge-base-guide.html) | Retrieve evidence with dates, boundaries and linked sources |

The UI library contains 1,334 assets, 58 documented flow maps and 16 component families. Assets include crops, composites and historical video frames. These are public evidence sequences, not a count of unique screens or authenticated usability tests. The original PDF is an earlier snapshot; use this brief and the linked HTML reports for the current package.


[Suggested demo questions](https://crefieldnotes.com/team-action-guide.html) connect the booking and billing evidence to useful comparisons.