The Trust Layer: Built to Reason

Building sequence, what gets built first

The competitive landscape splits into structural cohorts that travel across regions. Operator ERPs (Cohort 1) and operator AI surfaces (Cohort 2) compete at the application layer. Institutional reporting platforms (Cohort 3) and analytics platforms (Cohort 4) compete at the data layer. Horizontal AI infrastructure (Cohort 5) competes through both vertical acquisition (data platforms) and hyperscaler-LLM partnerships arming new vertical AI plays. Cherre's foundation position is at the layer that does not yet have an incumbent. Institutional in-house builds (sovereign wealth funds, large LPs) are addressed in Section 05 as buyer archetypes, not as competitors.

What the meta-layer codifies: the drift taxonomy

Standards do not sit still. They evolve under their own governance, in their own cadence, against their own audiences. The drift across them is not noise; it is the structural problem the meta-layer exists to solve. CORA names three drift types.

CORA operationalizes the drift taxonomy as a drift register: a neutral, public, version-pinned, machine-readable record of where and when drift occurs across the full standards landscape. Each entry captures what changed, why it matters downstream, and traces back to source documents. The register is the citable artifact. Cherre's canonical layer is the operational implementation. The platform applies the n-way correspondence and the drift annotations in production so that an agent reasoning on top of it does not silently break when an underlying standard moves.

The bodies the meta-layer spans

Below the meta-layer sit the standards bodies the drift register tracks. Cherre is seated in the four most relevant to the combined entity's product portfolio.

The standards landscape maps cleanly onto Cherre's product cores. RP Core (multifamily, operator-side) sits where RETTC/MITS owns the rental-housing data exchange. CONNECT and AIM Core (LP, institutional) sit where REDI and NCREIF anchor the institutional reporting and benchmarking work. OSCRE spans both as the broadest cross-segment model. Cherre's seats are secured on the segment-specific bodies that mirror its product cores (RETTC on the operator side, REDI on the institutional side) and in discussion on the institutional benchmark (NCREIF) and the cross-segment model (OSCRE). Both halves of the product portfolio are already represented in the rooms where standards are being formed.

REDI's stated approach is to operationalize INREV and NCREIF rather than replace them. This is the same logic CORA codifies one layer up. The standards bodies that matter are already converging on the "connect existing standards, do not invent a new one" model. The structural risk a sophisticated diligence team will look for is whether a vendor-neutral standard could emerge that commoditizes the semantic layer. The answer reverses the question. Cherre is not a participant in the standards being commoditized. Cherre operates the layer above them: the n-way correspondence, the drift register, the operational implementation of the meta-layer. The firm that implements the meta-layer is not displaced by the standards converging beneath it. The firm that implements the meta-layer is the firm the convergence runs through.

The largest sovereigns and reserve funds are the leading edge of the LP archetype. They have internal data sophistication, cross-asset mandates by construction, and procurement capacity to commit to foundation-grade infrastructure. Mid-tier LPs follow the leading edge by 18 to 24 months. The Phase 01 anchor account sits in this segment; the 900 operating partners that report into its governed data foundation become a directly addressable Phase 02 pipeline at the GP, Asset Manager, and Operator levels. The dual cadence inside the LP archetype is structural, not a sequencing choice.

Entry model by market

Buyer map, who is in the room by product

GTM sequencing, what opens the door

• Lead with the AI readiness assessment in every first meeting. It is low-commitment for the client, positions FDE expertise immediately, and surfaces the data gap that CONNECT solves
• Use existing AIM and IMS relationships as the primary pipeline engine. These clients already trust the brand and have documented data pain points the combined entity can solve today
• Leverage RealPage's institutional client base, large investors with multifamily portfolios and large multifamily operators, as a parallel pipeline engine. These accounts already consume the operational data backbone; CORE and ALPHA are the natural expansion paths
• Client Success teams must be trained to identify ALPHA expansion signals and route them to the Platform Value Office AE team within 24 hours
• Establish fund admin partnerships with clear commercial structure, referral economics or co-sell model, before the first EMEA hire lands
• In EMEA, use the UK as the beachhead and Luxembourg / Netherlands fund admin relationships as the continental European wedge into LP accounts

07.1 — Event Strategy

Cherre doesn’t attend the event. Cherre is the event.

A decade building the technical brand. Three years building the institutional commercial position. The result is a company senior buyers want to spend thirty minutes with, three years running.

Where Cherre showed up

Every event of consequence in institutional real assets and partner ecosystem across the past three years. Sponsorship, speaking placements, private meeting rooms, and hosted events. The pattern below shows a company that has stopped attending events and started being them.

Who’s in the Cherre Room

Three years of Cherre-hosted rooms. The people inside them.

How Cherre operates between the rooms

Cherre’s GTM is not a calendar of conferences. It is a year-long serialized program where each event compounds the last. The three activations below were executed by Cherre’s commercial team and demonstrate the operating discipline behind the convening capability: a year-long collectible campaign, an immersive product universe, a launch tied to a flagship product release. This is what scaled coordination across product, brand, and field looks like.

The Full House

Serialized Brand Universe · Year-Long Campaign · 4 National Events · 2025

Most B2B companies treat trade shows as isolated moments: a booth, a happy hour, a follow-up email. Cherre built a year-long narrative arc across four national events, turning a conference calendar into a serialized collector experience. Each event dropped a limited-edition playing card. The first, the Ace of Spades at RETCON, launched through pure guerrilla scarcity: no booth, no signage, just a card you could only get by meeting the team face-to-face. That single mechanic created the demand that made every subsequent drop more desirable. By the fourth card at CREtech New York, attendees were seeking out the Cherre booth specifically to complete their set and earn the #StayCurious blind box mailer. The innovation: a loyalty and community mechanic borrowed from consumer brands, applied to enterprise real estate for the first time.

The Data Mart

A Data Ontology Universe · Immersive Experiential · OPTECH 2025 & RETCON 2026

Data ontology is Cherre’s core technical differentiator, and the hardest concept in its entire product suite to explain. Rather than default to slides and demos, Cherre made the problem physical. At OPTECH in Las Vegas, the booth became a grocery store where ontology breaks down: mislabeled products, misplaced aisles, SQL & Vinegar Chips shelved next to the produce. Attendees hunted ingredients for Curious Cupcakes and experienced firsthand what real estate data management feels like without a governing schema. At RETCON 2026, the universe extended with the OntoloTea speakeasy: a walk-in beverage cooler hidden inside the Cherre Mart, with koozies reading “Talk Data to Me,” “Prompt Responsibly,” and “Is This AI Generated.” The innovation: turning an abstract infrastructure concept into a tactile, shareable experience that generated more booth traffic and conversation than any product demo could.

The Studio

Street Vendor Speakeasy Kiosk Activation · October 2025

The final Full House card dropped alongside an activation designed for the city it was in: a NYC street vendor kiosk on the conference floor, with checkered hotdog bags, a commissioned artist, and 3D-printed merch. The activation ran simultaneously with the official launch of Agent STUDIO and the Cherre Agent Marketplace, converting booth energy directly into product awareness. Nearly twenty Cherre team members worked the floor, the largest single-company presence at CREtech that year. The innovation: using a collectible campaign’s final chapter to drive urgency to the booth at the exact moment Cherre had an important product story to tell.

Lineage, Legacy, Consistency

Every activation was designed around a three-part philosophy: Lineage — executive visibility that earns the stage; Legacy — experiences that outlast the event; and Consistency — showing up with presence year after year. Click into each event to see the story in frame.

LineageCherre Chief Client Officer, Margaret Guelzow, on stage at RETCON

Legacy#StayCurious playing card unveil — the guerrilla drop that launched the Full House collector series at RETCON

ConsistencySpill the OntoloTea — a walk-in speakeasy hidden inside the Cherre Data Mart at RETCON 2026

‹

›

LineageCherre CEO and Co-Founder, L.D. Salmanson, speaking at Realcomm 2025

LineageCherre Chief Strategy Officer, Tama Huang, presenting at Realcomm 2025

LineageCherre Chief Growth Officer, Tyler Christensen, on the Realcomm 2025 stage

LegacyCherre-hosted VIP dinner in Savannah — an invite-only gathering for senior industry leaders at Realcomm 2026

LegacyRealTalk 2024 — Cherre-produced thought leadership series bringing together C-suite voices at Realcomm

LegacyCherre recognized with the Digie Award for innovation excellence at Realcomm

ConsistencyCherre booth presence at Realcomm 2024 — three consecutive years as a headline sponsor

ConsistencyRealcomm 2026 booth concept sketch — evolving the activation design year over year

‹

›

LineageCherre CEO and Co-Founder, L.D. Salmanson, delivering the keynote at CREtech 2024

LineageL.D. Salmanson returns to the CREtech keynote stage in 2025 — back-to-back years

LegacyThe Agent Studio speakeasy meeting room — a branded VIP experience at CREtech for product demos and executive conversations

ConsistencyCherre-hosted VIP event at CREtech — a curated evening for top-tier prospects and partners

‹

›

LineageCherre Chief Strategy Officer, Tama Huang, speaking on the Invest in Innovation panel at NMHC OPTECH

LegacyCherre co-authoring the MITS data standard — establishing industry-level credibility through standards leadership at NMHC

ConsistencyThe Cherre Data Mart grocery store booth at OPTECH — turning data ontology into a tactile, walk-through experience

‹

›

Most enterprise software companies have a brand. Few have a commercial position. Cherre has both.

The position is not abstract. It is the reason the meeting rooms fill, the receptions sell out, the same senior buyers keep coming back, and successors join the conversation when they are promoted. The evidence in this deck is the receipt. The receipt is also, in another reading, the verdict.

Cherre coming into RealPage is not a customer list. It is a commercial position in institutional real assets, built deliberately over three years on a decade of technical credibility, validated by who keeps showing up, and demonstrated by a pipeline that converts. The motion is built. Scaling it is the work that comes next.

07.2 — Pipeline

What the focus produced.

Three years ago, Cherre committed its product, GTM, and senior leadership to institutional investors and the commercial market. The pipeline below is the output of that focus. Three sellers, against a defined segment of sovereign wealth funds, pension funds, global asset managers, fund administrators, and institutional commercial REITs. The motion is proven. The book is real.

07.3 — Revenue Model

The motion is built. RP adds the team to run it at scale.

Three sellers built $15.5M in committed LARR and a $12.8M active pipeline across institutional real estate. GIC — closing this quarter — is a $2.5M ARR contract that puts Cherre in front of 400 GP operators globally. The LP-led initiative with HOOPP and the REDI standard creates a downstream mandate: every manager reporting into a REDI-adopting LP needs a compliant platform. GIC as a reference closes the conversation before it starts. That pipeline is not confined to North America. Savills Investment Management, DWS, ICG, and Partners Enterprise Capital are active in the book. Cherre brings the relationships, product fit, and institutional credibility to open the international market — a segment RealPage has not historically penetrated. The segment is mapped. The relationships are established. The pipeline converts. RP’s contribution is targeted: additional Sales Directors to absorb existing pipeline and build new pipeline from RP’s customer base, plus a new BDR to accelerate top-of-funnel. The ICP is proven. The book is real. Scaling it is the work that comes next.

The model above reflects Cherre’s standalone commercial position. It does not include the incremental opportunity across the RealPage product suite — AIM, RealPage BI, Market Analytics, and Investment Management. Cherre looks forward to modeling that upside collaboratively with the RealPage team.

This is what the Cherre team built before any RP contribution. The $9.5M Demo pipeline across 82 named institutional deals sits above this as further upside — not counted in either scenario. The international accounts are not modeled separately; they are active in the existing pipeline and represent an expansion surface that RP has not historically had access to.

Conservative model. $394K above the $17M target. Moderate scenario reaches $19.1M.

From the reporting stack to the agentic stack

Systems of record do not change. Storage does not change. The consumption layer does not change in role. Its consumer does. What gets added are the layers that make explicit the cognitive work the human used to perform invisibly. Three classes carry through the stack: Persistent, what survives unchanged from the reporting era; Transformed, mechanical transport shed of the semantic arbitration that used to hide inside ETL; and Codified, what the human used to do invisibly, now made explicit because the agent has no head.

Read top-down: the consumer is layer 09; systems of record are layer 01. Click any row for the gap today and what is still missing at scale. The badge on each row carries two lenses: the architectural class and the product line that owns it. CONNECT owns layer 02 across three flows in: Submissions, Pipelines, Market Data. Layers 01 and 09 are client-owned.

The deployment question (what gets built inside the firm, what gets consumed from the shared canonical layer, and the one layer that sits locally but depends on the canonical layer beneath) is answered in Section 11 Delivery, where the nine layers collapse into three deployment buckets.

Product ladder, the land-and-expand model

Why FDE-shaped delivery, not Center of Excellence

A Center of Excellence holds capability centrally and routes domain requests up for review before outputs return to the field. The model scales for reporting-era outputs, where review cadence is weekly and approval latency is measured in business days. Agentic outputs are continuous. Approval chains become latency. The reviewing center becomes the bottleneck the agent was supposed to eliminate. FDE-shaped delivery keeps domain expertise and AI capability in the same accountable unit. Pods carry the governing principles into the engagement. Authority sits at the unit doing the work. The decision-maker receives governed outputs without the relay.

The model has institutional precedent. Palantir's Forward Deployed Engineer practice scales by pod, not by hierarchy. McKinsey's QuantumBlack operates as embedded teams with platform-side principals, not as a center of excellence routing through a partnership. The argument is not that FDE is new; it is that the existing CoE-shaped CX functions inside both Cherre and RealPage need restructuring before they meet agentic delivery at scale.

Capability model, who owns what

Build, buy, or consume: the architectural layers

The in-house vs. partner question is sharper at the layer level than at the function level. Some layers each enterprise has to run for itself. Some are candidates for shared industry-level infrastructure, because the value of each scales with the number of participants. One layer sits locally but depends on the layers below being stable. This is the framework the combined entity uses to answer the audience's question about which services stay in-house and what in-house actually looks like.

The nine layers, mapped to the three buckets

The architecture defined in Section 08 collapses here into a deployment decision. Each row is one layer of the stack; the bucket column names where the combined entity operates it: built or bought inside the firm, consumed from the shared canonical layer, or sitting locally but depending on the canonical layer beneath.

The audience flagged that existing deployment and CX functions are weak in both legacy organizations. The layer-level frame is the answer: the canonical layer (industry-level) is where the combined entity invests deepest, because that is where scale advantage compounds. Enterprise-side delivery (in-house implementation, Data Services support, FDE pods) is rebuilt as the Platform Value Office, led by the Platform Value Office GM. RealPage's owned Data Services delivery centers in India and the Philippines and Cherre's Data Services partner network are integrated as a managed delivery portfolio for the support function: owned capacity handles predictable, repeatable workloads; partners handle surge, regional reach, and specialty workloads. The portfolio is the strategic asset, actively managed. Partner participation is appropriate at the enterprise edges (regional implementation surge, jurisdiction-specific compliance, specialty Data Services coverage) and explicitly inappropriate at the canonical layer.

Medallion architecture, the shared development methodology

The Medallion architecture defines how data is ingested, validated, and made ready for AI, in three enforced layers. Every client deployment follows this pattern, which ensures data quality gates are met before AI agents operate on the data. It is the shared methodology across Onboarding, Data Services, and FDE.

Beyond Gold: the decision graph

The Medallion layers serve the data agents reason against. The decision graph is what makes their reasoning auditable. Every meaningful action an agent takes, every approval, every override, every interpretation, every model output, is captured as a queryable event indexed by entity, by actor, by time, and by definition version. This is what reproducibility looks like in implementation. Without it, an agent that produces the right answer cannot prove how it produced the right answer, and the answer fails the audit standard the next era will impose.

Delivery model decisions to resolve

• Define the handoff protocol between Onboarding and Data Services: documentation requirements, SLA definitions, and client introduction process must be standardized before the first EMEA hire
• Productize the FDE readiness assessment: fixed scope, defined output format, repeatable methodology across all ICP segments; this is the opening move in every sales cycle
• Determine the staffing ratio between Onboarding, Data Services, and FDE by region and phase. These ratios drive the hiring plan and budget model
• Build Bronze → Silver → Gold quality gate definitions into the CONNECT platform so they are enforced by the system, not by manual process dependent on individual team members
• Define "agent-ready" data specifications per ICP segment. The Gold layer configuration differs between a GP, an LP, and a fund administrator; FDEs and Onboarding must align on this before Phase 02

Three delivery functions inside the Office

Three functions sit inside the Platform Value Office, each contributing services revenue. A fourth function, SaaS Support, sits adjacent: operationally co-located so signals flow into Onboarding, Data Services, and FDE, but funded as software COGS to keep software and services revenue distinct on the buyer's side.

The client lifecycle flow

How signals travel

Inside the same operating team, even when Support's costs sit in software COGS, signals travel by standup, by shared ticket queue, by the same manager asking "what are we seeing this week?" The cost-center boundary doesn't break the discipline; the BU is built so it doesn't.

Client experience as a horizontal

CX is not a fifth org. It is a horizontal function inside the Platform Value Office that ensures the client sees one team, one intake, and one escalation path, regardless of which function is doing the work.

Integration map, what gets merged, what gets built, what gets sunset

How revenue is reported

Hiring sequence, what gets staffed first

Organizational decisions to resolve before close

• Confirm the Platform Value Office GM mandate is global from day one and revenue from CORE and ALPHA reports distinctly from software subscription revenue, so buyers can allocate cleanly across opex and capex
• Define the FDE Practice's relationship to product engineering; is FDE a customer of product, a peer to product, or a feedback channel into product roadmap? The choice determines pod composition and hiring profile
• Finalize whether the CX function leads from operator side (RealPage muscle) or institutional side (Cherre depth); the answer drives whether the existing RealPage CX team is restructured or partially replaced
• Resolve the open questions in the integration map, solutions engineering merge path, and channel-partner strategy, before regional hiring for Phase 02 begins
• Establish FDE attribution rules between sales (deal credit) and Practice (deployment outcome) before the first regional FDE is hired; cross-region FDE deployments need an explicit attribution policy at hire
• Decide the FDE compensation model; pod-level deployment target, deal-attach component, NRR contribution, or hybrid; the model has implications for how pods coordinate vs. compete

Capability model

Functional areas define the phases of delivery. Capabilities (pills) will be mapped to each area and color-coded by which function owns them: Onboarding, Data Services Support, or FDE. Project Management spans all four delivery phases as a cross-cutting discipline.

Maturity levels: baseline to excellent

Baseline is the floor: what each function must be able to do before touching a client account. Excellent is the Phase 02 target state. The gap between them is each engine lead's development agenda.

Ramp model: 30 / 60 / 90 day milestones

Every new hire enters a structured ramp regardless of seniority. Milestones are binary: either the deliverable exists or it does not. They are the basis for ramp-period performance review and the gate before a hire receives primary account ownership.

Onboarding

Data Services Support

Forward Deployed Engineering

Capability model decisions to resolve

• Define the formal handoff document template between Onboarding and Data Services Support before the first EMEA hire joins. The handoff protocol cannot be verbal at regional scale
• Productize the FDE AI readiness assessment: fixed scope, defined deliverable format, consistent pricing. This is the opening play in every ALPHA sales cycle and must be repeatable across all pods
• Establish the Gold-layer readiness specification per ICP segment (GP, LP, Institutional Asset Manager, Operator) so Onboarding and FDE share a definition before Phase 02 hiring begins
• Build the 30/60/90 ramp milestones into the offer letter and day-one onboarding for every hire, not as aspirational targets but as the explicit condition for ramp-period completion and transition to full OTE

Integration sequence

Phase model from Section 02 crossed against the delivery, capability, and standards tracks. Each cell names the milestones and gates the track has to clear before the next phase opens.

Decision Ledger

Decisions for the integration committee to ratify. Priority indicates urgency, not sequence; each is argued in the body of the brief.

Risk Register

Integration risks for the integration committee to track. Impact indicates severity, not sequence; each carries a mitigation argued in the body of the brief.