Private deal data by default
Sensitive borrower, owner, asset, and model context should stay scoped to the right workspace, team, and approval path.
Security, methodology & trust
CRE analysis should be fast, but never unreviewable.
Cactus is designed as the CRE workflow layer around powerful AI: documents, sources, assumptions, approvals, outputs, and reusable firm intelligence stay connected so your team can inspect the work before it moves.
01
Ingest the deal package
OMs, rent rolls, T-12s, leases, spreadsheets, models, and market context come into one workspace instead of living across inboxes, folders, and one-off AI chats.
02
Extract structured facts
Cactus turns messy CRE materials into structured deal facts your team can inspect, edit, approve, reject, or send back for more evidence.
03
Tie facts back to sources
Important values stay connected to source notes, timestamps, and confidence/review states so the workflow remains reviewable instead of becoming a black-box answer.
04
Review assumptions before outputs
Teams keep control over assumptions, caveats, comps, market support, and model logic before analysis moves into Excel, memos, BOVs, debt packages, or presentations.
05
Reuse approved context
Reviewed facts, assumptions, source notes, comp decisions, model rules, and output preferences become reusable firm intelligence for future work.
What Cactus is not
Cactus is not a generic AI chat that gives a plausible answer and leaves your team to reverse-engineer the numbers. It is a governed CRE workflow for documents, assumptions, source trails, review, Excel-ready analysis, and firm intelligence.
Compare workflow optionsWorkflow controls
- Source trails for key extracted facts, assumptions, comps, and reviewer notes
- Confidence and review states before outputs go final
- Approval gates before any sensitive side effect or external handoff
- Audit history for decisions, edits, assumptions, and output changes
- Reusable firm intelligence so prior work compounds without hiding the source trail
- Human review for assumptions that affect valuation, credit, IC, or client-facing materials
Least-privilege access
Users, tools, and future connectors should only get the minimum access required for the specific workflow they are helping with.
Credentialed workflows require controls
Email, app, scraper, and data connectors must use OAuth or secure credential storage, encrypted secrets, scoped permissions, and revocation paths before production use.
Prompt-injection defense
External documents and web content are treated as untrusted input. Cactus workflows should separate user intent from document text and require approval before tool-driven side effects.
Buyer checklist
Questions every CRE team should ask before trusting AI with deal work.
- Can every material number be traced back to a file, page, source note, or reviewed assumption?
- Can a principal, lender, broker, or IC reviewer see what changed and who approved it?
- Are connectors, credentials, and sensitive actions gated by least-privilege access and explicit approval?
- Can the team reuse prior facts and assumptions without losing provenance?