Skip to content
Bad AlienField file 01 Active engagement
01 /CAMCO

Training
the team,
building the tools

A commercial real estate investment group came to me for a new website. Today, its partners can answer investor and client inquiries from 27,000 pages of deal history in under 45 minutes, without access to the sensitive financial information inside, all from their Claude accounts.

Average response to an investor or client inquiry
Before
3+ hrs
Waiting on one of two managing partners to open the files
Now
Under45 min
Answered by the partners themselves, from approved files
Fig. 1 — 475 offering memoranda27,000 pp.
On the recordCAMCO Investment Group

He’s become someone we trust for both advice and execution.

Rasheed is great to work with. He quickly understands how different parts of our business operate and identifies opportunities for improvement that we hadn't considered. His work has significantly improved our response times and given us better tools to evaluate potential investments. He's become someone we trust for both advice and execution, and I wouldn't hesitate to recommend him to any business looking to improve its operations.

Kyle CampbellPresident, CAMCO Investment Group
§ 02The briefConfidential file
02 / The brief
Where it started

27,000 pages of deal history, and every answer waited on two people.

01

CAMCO buys and manages commercial property. Every deal it has looked at arrives as an offering memorandum: a long PDF of rent rolls, financials, tenant names and terms. Over the years the firm had collected 475 of them, about 27,000 pages, in SharePoint, and because they hold highly sensitive information, only the two managing partners could open them.

02

The firm wanted its partners to answer investor and client questions themselves, without anyone seeing what only the managing partners should, and without anything sensitive leaving the firm's own systems.

Pl. 2An offering memorandum, redactedIllustration. Not a CAMCO document.
Fig. 2a — How an answer travelledBefore
  1. 1
    Investor or client
    Asks a question
  2. 2
    Investor and client relations
    Can't open the files
  3. 3
    Managing partner
    Finds the answer in the originals
  4. 4
    Investor and client relations
    Gets it back, writes the reply
  5. 5
    Investor or client
    Gets the answer
Time
3+ hrs
Conditions of the work

Three rules every part of the system had to keep.

Confidential

Originals open to the two managing partners only.

No new stack

Run on the Microsoft 365 and AI subscriptions the firm already had.

A person decides

Nothing reaches the partners until a managing partner approves it.

Fig. 2b — How an answer travels nowAfter
  1. 1
    Investor or client
    Asks a question
  2. 2
    Partner
    Asks Claude, from their own account
  3. 3
    Claude
    Reads only the approved, sanitized files
  4. 4
    Investor or client
    Gets the answer from the partner
Time
Under 45 min
Chapter 1
3 days
2 principals, 4 collaborators

First onsite visit

A new website, a map of where AI fits in the firm's work, and a first prototype of the site-selection tool.

  1. 1.1Rebuilt the website: Next.js with an Auth0 investor login, structured for AI search (GEO), handed off to the firm
  2. 1.2Discovery: where AI would actually save the partners and their team time
  3. 1.3A rapid prototype of the site-selection tool, its interface and scoring worked out with the team
Pl. 01
Commercial property at duskIllustration
Chapter 2
Between visits

Two months of building

The document system and the site-selection tool built, tested, refined and validated before anyone relied on them.

  1. 2.1Two SharePoint sites: the confidential originals, and an approved, sanitized copy
  2. 2.2The Azure redaction and deal-summary pipeline, with a managing partner's approval before anything is published
  3. 2.3The site-selection tool, built out from the prototype on the website's backend
Between the visitsPl. 02
BuildTestRefineValidate
3 daysTwo months2 days
Nothing reached the team until it had been tested and validated.
Eight weeks between the visitsDiagram
Chapter 3
2 days, two months later

Second onsite visit

Teaching the firm to use what was built, and making sure everyone asks it the right way.

  1. 3.1The leads: how the document system and the site-selection tool work
  2. 3.2The partners: which investor and client inquiries they can now answer themselves
  3. 3.3Everyone: querying Claude correctly, on their own deals
Pl. 03
A working session at the whiteboardIllustration
Ongoing

Since then, CAMCO's ongoing AI advisor: maintaining both tools, and adding new ones as the firm finds new questions.

04 /The system, in detail

Redacted, summarized,
then approved
by a person.

An event-driven pipeline inside the firm’s own Microsoft 365 and Azure. Every memorandum is read, redacted and summarized automatically, and a managing partner approves it before any partner’s AI can see it.

No custom server / no vector database / no always-on AI infrastructure

Fig. 5 — one memorandum through the pipeline / Stage 01 of 07
SharePoint / ConfidentialSharePoint / ApprovedOffering memorandum
New file → workflow started
Offering
memorandum
Confidential
Property
Industrial flex, 6 buildings
Market
Inland Empire, CA
Seller
Contact
Rent rollNOI · Cap rate · IRR
Lease terms
Deal summaryIllustrative
NOI (yr 1)
$2.41M
Cap rate
6.2%
IRR (5-yr hold)
14.8%
Financing
65% LTV, 5.9% fixed
Key risk
Two tenants hold 48% of rent
Partner asksApproved files only
What occupancy rate did we underwrite for the property by year two?
  1. SharePoint Online

    The original memoranda, in their own site with role-based permissions.

    In
    Original offering memoranda (PDF)
    Out
    A new or updated file event
    Sees it
    The two managing partners only
  2. Power Automate

    An event-driven workflow starts on every new or changed memorandum; nobody runs it by hand.

    In
    File event from the confidential site
    Out
    One logged run per memorandum
    Sees it
    Runs inside the firm's Microsoft 365
  3. Azure AI Document Intelligence

    Reads every page: running text, tables and the financial figures in them.

    In
    The original PDF
    Out
    Structured text, tables and figures
    Sees it
    Processed within the firm's Azure
  4. Azure AI Language + Azure OpenAI

    Azure AI Language and Azure OpenAI find and remove sensitive details, then write a standard deal summary: NOI, IRR, cap rates, financing terms and risks.

    In
    Extracted text and figures
    Out
    A sanitized document and a deal summary
    Sees it
    Processed within the firm's Azure
  5. Managing partner

    A managing partner reviews every sanitized document and summary. Only approved files move on.

    In
    Sanitized document and summary
    Out
    An approval record
    Sees it
    The two managing partners
  6. SharePoint Online

    Sanitized copies and summaries, in a separate site the other partners can open.

    In
    Approved files only
    Out
    A searchable, sanitized archive
    Sees it
    Partners, by role
  7. Claude Team + Microsoft 365 connector

    Partners sign in with Entra ID and MFA; the AI inherits their SharePoint permissions, so it can only reach the approved site.

    In
    A partner's question
    Out
    An answer drawn from approved files
    Sees it
    Whatever that partner may open
Fig. 6 — Architecture and trust boundaryOriginals never leave the firm’s tenant
The firm’s Microsoft 365 and Azure
Confidential · managing partners only
01
Confidential site
SharePoint Online
02
Workflow
Power Automate
03
Extract
Document Intelligence
04
Redact, summarize
AI Language + OpenAI
05
Approve
Managing partner
Approved
06
Approved site
SharePoint Online
Approved
files only
AI workspace
07
Partner asks
Claude Team + Microsoft 365 connector

Four guardrails

  1. 1
    Sign-in

    Partners sign in with their existing Microsoft 365 accounts through Entra ID with MFA.

  2. 2
    Permissions

    The AI reaches only the documents that partner may already open.

  3. 3
    Approval

    A managing partner approves every sanitized file before it is published.

  4. 4
    Audit

    Microsoft Purview logs access, sharing and security events, alongside approval records.

What it costs

$300

One-time, to process all 475 memoranda

~$25 / yr

For about 12 new memoranda a year

0

Custom servers, vector databases or always-on AI infrastructure

Everything runs on the Microsoft 365 and AI team subscriptions the firm already had.

05 /Site-selection tool

Finding land near the power

Data centers and other heavy-power tenants need sites near transmission capacity. Prototyped with the team on the first visit and built out between visits, the site-selection tool runs on the website's backend: it overlays public grid data on a prospective acquisition and asks an AI model for a weighted score of its fit.

1.4 mi · 230 kVParcel 0417 · 38 ac · illustrative
Plate 5 — prospective acquisition, public grid data overlaidLayers HIFLD / EIA / OpenStreetMap
  1. 1HIFLD
    Transmission lines and substations
  2. 2EIA
    Power plants and generation capacity
  3. 3OpenStreetMap
    Roads, parcels and land use
Built with
  • Mapbox GL JS
  • Turf.js
  • Supabase
  • PostGIS
  • Anthropic API

Used by the team in the field.

Pl. 6 — Commercial property at duskIllustration
06 /Since 2025

Still CAMCO's AI advisor.

New tools as the firm finds new questions.

Colophon

Claude Team/Microsoft 365/SharePoint/Microsoft Entra ID/Power Automate/Azure AI Document Intelligence/Azure AI Language/Azure OpenAI/Microsoft Purview/Next.js/Auth0/Mapbox GL JS/Supabase PostGIS