Meet your CIP agents.
Each task spawns a focused specialist.
When your team makes a request, a fresh agent spawns, loaded with the master context for the CIP portfolio. It executes one task, reports back, and ends. The next request spawns the next agent. Your team directs. The agents execute. You stay in charge of every task.
The Make-Ready Agent.
Works the make-ready phase. Spawned when your team triggers a make-ready task.
Tasks it executes on request:
- Drafts a punch list from a walk-through report
- Compiles a vendor bid comparison from submitted quotes
- Generates a CapEx routing form from approved scope
- Alerts the team when a unit crosses a defined threshold (14 days, vendor unresponsive, scope variance)
- Drafts a sign-off checklist when work completes
How you direct it:
Triggered by name from the Notice and Make-Ready surface, by menu selection, or by structured form input. Never by free-form prompt.
What it does not do:
Does not approve work, dispatch vendors, release payment, or modify lease terms. Every action requires explicit team confirmation.
How it ends:
Reports back to the team with a structured outcome record. The agent ends. The next make-ready task spawns a fresh instance.
And the others.
Same pattern, different specialties. Each one spawns on request, executes one task, reports back. Listed in lifecycle order.
The Notice Agent
Works the notice-of-intent phase.
Example task: Drafts a move-out checklist from an incoming notice and the original lease.
The Market Agent
Works the market read phase.
Example task: Pulls comparable listings and generates a pricing recommendation with confidence score.
The Listing Agent
Works the listing distribution phase.
Example task: Drafts listing copy and assembles a marketing package from unit specs and photography.
The Deal Agent
Works the deal qualification phase.
Example task: Compiles a credit and financial profile on a prospect, benchmarks the LOI against recent comparable deals.
The Onboarding Agent
Works the tenant onboarding phase.
Example task: Tracks TI scope and coordinates contractor access against the move-in timeline.
Why this works.
Each agent fires with full context loaded. That's why the output is reliable. Built once during the engagement, revised as the portfolio evolves.
Master context layer
Loaded into every agent on spawn. Persistent across the operation.
- Portfolio structure, market territories, and lease templates as a structured knowledge base, not free text
- Organizational hierarchy with role-based access boundaries across asset management, leasing, property management, and accounting
- Terminology, unit codes, and naming conventions specific to the CIP portfolio
- Document sources mapped by authority, defining which document is canonical for which question
- Versioned and revisable, with a complete audit trail on every change
Orchestration layer
Defines how every agent reads, reasons, and routes.
- Source-of-truth hierarchy across lease management, accounting, work orders, listing platforms, and field tools, defined per question type
- Conflict resolution rules when two systems disagree, configured during onboarding
- Confidence thresholds that determine when CIP Agent answers directly versus surfaces a question to the team
- Recurring briefing patterns such as weekly portfolio reads, monthly leasing position, and quarterly capital reviews, defined as standing prompts
- Escalation routing for items above defined thresholds, including variance flags, time-on-market slips, and CapEx requests
Execution layer
Defines the scoped tasks each agent can execute.
- Pre-built scripts for recurring scoped actions, including listing generation, marketing package compilation, vendor bid request routing, deal package assembly, and onboarding checklist generation
- Each script has defined inputs, defined outputs, defined permissions, and a defined audit record
- Triggered by name, by menu selection, or by structured form input, never by free-form prompt
- Idempotent and reversible where possible, with destructive actions requiring explicit team confirmation
- Reports back to the team on completion with a structured outcome record
Integration layer
Defines what every agent reads from. Nothing replaced.
- Read-only API connections to lease management, accounting, work order, and listing systems
- Structured intake from email, calendar, document folders, and exports where APIs are not available
- All data stays in your systems of record. CIP Agent holds no canonical data
- Connection health monitored continuously, with source failures surfaced as confidence flags on affected answers
- Onboarding integration scoped per system during the initial engagement
Each request spawns a specialist. Each specialist runs one task. Your team directs. The system reports back. Trust compounds as your team learns where each agent fires reliably, and the agents get sharper as the master context grows. You stay in charge of every task.