Eight systems across the deal cycle.

Deal Sourcing Engine

Which parcels deserve a call this week?

Runs your buy box across county records, permit filings, and distress signals every night. Each parcel gets a score you can audit — the signals that produced it are listed, not hidden — so the morning call list is defensible rather than a black box.

312parcels screened overnight

Output → Ranked call list, scored against your buy box, with the evidence behind every score

County records · Signal scoring · Claude · Cron pipelines

Owner Intelligence Engine

Who actually owns this, and how do I reach them?

Recursive corporate-registry resolution through layered LLC chains, a three-tier contact enrichment waterfall, and results written straight back into the team's admin platform. Every hop in the ownership chain cites the registry record it came from.

5-10 minper property, down to seconds

Output → Verified beneficial owner with a contact path and full provenance

Claude · Headless browsing · Enrichment APIs

Deal Pipeline Engine

Which deals are going stale while we look away?

Deals die from silence, not rejection. This watches every open deal for a missing next action, an unanswered broker thread, or an owner who has gone quiet, then drafts the follow-up and logs the activity so the CRM stays honest without anyone maintaining it.

41stalled deals recovered

Output → A pipeline where every deal has a next action, an owner, and a date

CRM sync · Claude · Thread analysis · Cron pipelines

Underwriting & Pro Forma Engine

What can we pay, and what breaks the deal?

Deal facts arrive from the lease abstract and the comp set. The engine assembles sources and uses, a five-year NOI ramp, and debt sized against LTC, DSCR, and debt-yield constraints, then computes returns deterministically across an 81-cell sensitivity grid. Every assumption cites its basis, so the IC spends its time on the deal itself.

81return scenarios per sensitivity grid

Output → Auditable pro forma with sized debt, a sensitivity grid, and a maximum price you can defend

Deterministic models · Debt sizing · Sensitivity grids · Comp citations

Document Intelligence Engine

What is actually in this lease, and what did we miss?

Drop in a lease, PSA, or offering memorandum and get back structured fields — dates, options, escalations, exclusions — with a page and clause citation on every one. Anything the model is not confident about lands in a review queue instead of silently into your model.

94fields abstracted per lease

Output → Structured abstract with clause-level provenance and a review queue

Claude · OCR · Clause citation · Review queue

Email Operations Suite

What in my inbox actually needs me today?

A morning digest of the day's actionable threads, nightly contact mining that keeps the marketing list growing on its own, and a listings activity report that maintains itself every weekday.

10+ hrsper week of manual work removed

Output → Morning digest of the threads that need a decision, and nothing else

M365 Graph · Claude · Cron pipelines · Google Sheets

LP Reporting Engine

Can we send the quarterly update without a fire drill?

Reads only from figures a human has already approved, drafts each investor's letter against their actual position, and cites the source of every number. It never sends: the last step is a GP signing off, because the point is to remove the typing, not the judgement.

38letters drafted from approved data

Output → Draft investor letters built only from approved figures, held for GP sign-off

Claude · Approved-data only · Provenance · Sign-off gate

Platform Cutover

How do we take the keys and keep moving?

Migrated a core admin platform off an outside vendor and onto infrastructure the client controls. Source and CI moved, vendor access removed, secrets rotated, backups in place — and the runbook handed over with it.

100%client-owned infrastructure

Output → Infrastructure in your accounts, credentials rotated, backups verified

CI/CD · Secrets rotation · DigitalOcean