Docs

Using theCREmodel

theCREmodel is one AI-native commercial real estate operating system that adapts to tenant-side and landlord-side brokerage work through a shared representation mode profile layer.

Shared platform architecture
Mode-aware workflows
Live on thecremodel.com

Shared Architecture

Both modes operate on one shared codebase, one shared entity graph, one shared document system, one shared AI orchestration layer, one shared export system, and one shared CRM architecture.

Shared Graph

Companies, contacts, buildings, floors, suites, leases, obligations, deals, proposals, analyses, surveys, tasks, and activities stay connected.

Shared AI

The same AI orchestration layer powers prompt interpretation, suggested actions, automation, and audit visibility in both modes.

Shared Exports

PDFs, spreadsheets, reports, and share links all use the same export pipeline with mode-aware framing.

Representation Modes

Tenant Rep

Relationship-centric advisory CRM for tenant-side brokerage.

Default Module

CRM

Default CRM View

Records

Workflow Emphasis

  • Expiring Clients: Clients with upcoming lease decisions.
  • Expiring Prospects: Prospects entering actionable lease windows.
  • Stale Relationships: Companies with aging touchpoints.
  • Active Deals: Open pursuits and requirement motion.

AI Suggestions

  • Show me prospects expiring in the next 12 months.
  • Draft renewal outreach for these clients.
  • Compare these survey options by monthly occupancy cost.

Landlord Rep

Building-first leasing operations console for landlord-side brokerage.

Default Module

Leasing Console

Default CRM View

Stacking Plan

Workflow Emphasis

  • Portfolio Vacancies: Vacant suites across tracked buildings.
  • Expiring Tenants: Occupancies approaching action windows.
  • Tour Activity: Buildings and suites with active tours.
  • Proposal Pipeline: Suites with proposals or counters underway.

AI Suggestions

  • Show suites expiring in this building.
  • Summarize tour activity for this building.
  • Which availabilities have active proposals?

Mode-Aware Surfaces

Onboarding + Navigation

Onboarding steps, module order, module labels, and workspace defaults are seeded by the active representation mode profile.

Dashboards + CRM

Tenant dashboards center companies and relationships. Landlord dashboards center buildings, suites, vacancies, tours, proposals, and downtime risk.

CRM now opens with a shorter start-here flow, a smaller priority snapshot, and a focused record view first, while deeper pipeline, intake, and inventory tools stay available inside an advanced workspace when you need them.

The Deals workspace now includes a dedicated deal-room shell inspired by enterprise leasing systems: each transaction can be run through explicit Overview, Company, Updates, Listings, Tours, Negotiation, User Management, and Client View tabs instead of one long generic form.

Those deal rooms keep projected close timing, move reason, current-location constraints, access controls, curated client-view summaries, and negotiation trackers attached to the same underlying transaction record used by CRM boards and building workflows.

A dedicated Buildings module now exposes the full building and suite inventory on one shared map with filters, result lists, detail panels, and building-first workflow actions into Surveys, CRM, and Analyses.

The Buildings workspace now supports suite-level filtering, photo-forward result cards, and selected-suite handoff into Surveys so users can move from map browsing to actual option building without rekeying data.

Map selection mode can now drag-select nearby buildings, keep that building set highlighted in the results panel, and feed selected suites directly into Financial Analyses through the same scenario workflow used elsewhere in the platform.

CRM intake now supports typed building search with existing-record autofill and an add-building path when no current match exists.

Account CRM settings now include a shared CoStar Excel import path. Published `.xlsx` office inventory rows update the common building dataset used across CRM for all users, while client-scoped records and overrides remain isolated inside each workspace.

Landlord building views now include an editable stacking-plan workspace for floors and suites, with optional economics such as rate, OpEx, abatement, TI allowance, concessions, and size saved directly to the active building record.

Current lease, amendment, abstract, and sublease uploads can seed or refresh stack occupancy. Proposal, LOI, and counter uploads do not overwrite stack occupancy.

Buildings now also support deal-linked shortlist and tour workflow actions, so selected suites can move directly into shortlist, scheduled tour, and proposal-requested states without leaving the building workspace.

CRM now exposes dedicated shortlist and tour boards inside the deal workspace so teams can manage option progression and tour outcomes visually after the building-side handoff.

Those CRM boards now support inline editing for tour attendees, notes, and follow-up tasks, plus AI actions for generating a tour brief or preparing proposal-request guidance directly from the active card.

Board-level building, broker, and date filters make the shortlist and tour workspace usable for larger teams without forcing users to leave the deal record.

Shortlist and tour cards can now be dragged directly between board columns, which updates the same underlying CRM workflow records that drive the rest of the deal workspace.

Shortlist cards now support inline owner assignment and tour cards support inline assignee fields, so board responsibility can be set directly where the work is happening.

Board cards can now be selected in bulk for reassignment, which lets a lead broker rebalance shortlist ownership or tour coordination across multiple cards at once without opening every record individually.

Teams can save both deal-specific and team-wide board views for recurring broker or building slices, and team-wide views are now role-aware so shared filters can be reused without giving every user edit rights to the shared view layer.

Completed tour cards now support AI-generated post-tour recap email drafts with subject and body output, plus one-click send-to-client through the backend mail flow and one-click log-to-deal actions so the recap becomes part of real workflow follow-through.

AI + Next Best Actions

Side panels, prompt interpretation, suggested commands, and next best actions shift by mode without splitting the AI tool layer.

Reminders + Templates + Exports

Reminder timing, outreach templates, and export descriptors all reuse shared infrastructure while changing framing to match the active brokerage workflow.

Production Access

Production is served from thecremodel.com. Long-running workflows can use the platform's existing direct-processing paths, while support and proof routes continue to use the same-origin application domain.

Core Modules

  • CRM: The mode-aware operating hub for companies or buildings, linked records, tasks, reminders, activities, AI actions, and execution workflows. The landing view is now simplified for first-time users with a guided start-here flow, a short priority queue, and one current-focus panel before the deeper operating workspace expands.
  • Deal Rooms: A transaction-first operating layer for overview summaries, listing progression, tours, negotiation tracking, access management, updates, and curated client-facing previews.
  • Buildings: A shared building browser with comprehensive map filters, suite visibility, stacking plans, and handoff actions into surveys and other workflows. Client-scoped building removals now persist across refresh and cloud sync, so deleted buildings do not repopulate from saved workspace state.
  • Surveys: Market options, shortlist management, and location intelligence using the shared record graph.
  • Financial Analyses: Lease comparison, economics, and sublease recovery on top of parsed proposal and lease data. The extractor now uses a guided intake panel with a visible file picker, core-field validation, automatic snapshot repair, and a presentation-ready comparison workspace that keeps source intake, option selection, active editing, and exports in one clean flow. Renewal and counterproposal parsing still preserves explicit carry-forward OpEx cues such as clauses that say the economics should match the existing lease structure, so retained escalations are not flattened to zero. Word proposals and counters that use section layouts like PRIMARY LEASE TERM, RENT ABATEMENT PERIOD, and BASE ANNUAL NET RENTAL RATE now parse option-specific term, abatement, and stepped-rent economics more reliably as well, including landlord-response or tenant-counter files that still contain the original embedded RFP pages above the response terms. Uploads from the Financial Analyses module still carry the saved document id into the scenario pipeline whether they come through the dedicated extract widget, the tab-wide drop zone, or the module document center, and successful parses automatically reopen the comparison summary. Saved workspace snapshots are repaired on reopen so stale confidence scores or outdated review flags do not kick a healthy lease back into a manual gate after refresh. Files that do not yield a dependable canonical lease no longer pretend to be parsed, so the workspace surfaces the extraction issue instead of silently parking a dead document row. Existing workspace documents can also re-parse from their saved file payload when a parsed snapshot is missing. The extraction pipeline now includes additional resilience so that errors in optional enrichment steps are isolated and do not block the core lease extraction result.
  • Document Center: Uploaded PDFs, images, and supported Word proposal files now keep a browser-local openable payload alongside cloud-synced metadata, so the same browser can reopen those files after refresh without losing document intelligence state. Intentional document removals now also persist, preventing deleted files from reappearing from stale synced workspace payloads.
  • Lease Abstracts: Shared lease parsing and abstracting workflows that feed both tenant and landlord operations.
  • Obligations / Reporting: Lease deadlines, notices, expiration risk, and reporting outputs, framed by representation mode.

FAQ

Is this one platform or two separate products?

One platform. Tenant Rep and Landlord Rep run on the same shared entity graph, document intelligence layer, AI orchestration layer, export system, and CRM architecture.

What changes when I switch representation mode?

The platform adapts onboarding, navigation emphasis, dashboard composition, default CRM views, AI suggestions, reminders, templates, next best actions, and export framing without changing the underlying records.

What is the default CRM view in each mode?

Tenant Rep opens the CRM in a client-grouped company hub view. Landlord Rep opens the CRM in a building-first stacking-plan workspace built from shared building, suite, lease, sublease, deal, and obligation records.

What does the landlord stacking plan show?

Editable floor and suite blocks, occupied suites, vacant suites, current lease and sublease occupancy, upcoming expirations, shortlist motion, active proposal motion, and toured suites, organized by building, floor, and suite from the same shared data model used everywhere else in the platform.

How does AI adapt by mode?

Tenant Rep AI biases toward companies, prospects, requirements, surveys, analyses, and obligations. Landlord Rep AI biases toward buildings, suites, availabilities, tours, proposals, expirations, and ownership reporting.

Do exports use different systems in each mode?

No. Exports use one shared pipeline, but the framing shifts by mode: tenant outputs are advisory and client-facing, while landlord outputs are operational and ownership-facing.