By Aidan Scudder · Updated , first published
Real Estate Sponsor
How Accomplish Collective put four AI employees across its deal cycle
Four AI employees covering deal sourcing and underwriting, monthly asset-management reviews, and quarterly investor reporting, running inside the firm's own Microsoft 365 tenant and Claude workspace.
Illustrative propertyIllustrative property, not a client asset. Photo: Jay Blacks, CC0.
01Before / After
Less assembly. More judgment.
Before
Done by hand
- Four workstreams competing for the same hours
- Sourcing went quiet in reporting weeks
- The nearest deadline set the pace
After
With PSV
- One AI employee per workstream
- Each workstream worked continuously
- A live deal no longer stalls the reporting calendar
02Built around the work
How the work moves now.
01
Source
Opportunities screened and underwritten on the firm's criteria
02
Review
Portfolio performance reviewed every month
03
Report
Investor reporting drafted each quarter from the same numbers
04
Contain
All of it inside the firm's Microsoft 365 tenant and Claude workspace
Nothing moved to a PSV system. The work lands where the team already works, under the access it already has.
03What the team receives
Outputs the team works with.
01
Deal sourcing and underwriting
Inbound and sourced opportunities are screened and underwritten on the firm's own criteria, so the pipeline keeps moving while the team is heads-down elsewhere.
02
Monthly asset-management reviews
Portfolio performance is reviewed on a monthly cadence rather than whenever a gap opens up in the deal calendar.
03
Quarterly investor reporting
Investor reporting is drafted on the firm's own quarterly cycle, out of the same underlying numbers the asset-management reviews use.
04
Runs in the firm's Microsoft 365 tenant
The AI employees work inside the client's existing tenant and Claude workspace. No data was moved to a PSV system to make the build work.
04The record behind the story
One engagement, in numbers.
Headline result
4
AI employees across the deal cycle
Kicked off July 2026
4
AI employees deployed
Three were scoped and a fourth was added before kickoff, each owning a named workstream rather than a general assistant covering all of them.
4
Workstreams covered
Deal sourcing, underwriting, monthly asset-management reviews, and quarterly investor reporting.
0
Existing client systems replaced
Everything runs inside the firm's own Microsoft 365 tenant and Claude workspace. No migration, no new system of record.
These counts describe what was deployed, not what it has returned. No time-saved figure is published yet.
Engagement notes
What was in the way
Accomplish Collective runs the full sponsor cycle: finding deals, underwriting them, reviewing the portfolio month to month, and reporting to investors every quarter. All four drew on the same team and the same hours.
That makes the calendar the priority system. Whichever workstream was closest to a deadline set the pace for the rest, so sourcing went quiet in reporting weeks and asset-management reviews slipped whenever a deal was live.
What PSV built
Rather than one assistant spread across everything, PSV deployed four AI employees, one per workstream: deal sourcing, underwriting, monthly asset-management reviews, and quarterly investor reporting. Each has its own scope, its own inputs, and its own output the team already recognises.
All four run inside the firm's existing Microsoft 365 tenant and Claude workspace. Nothing was migrated to a PSV platform and no existing system of record was replaced, so the work lands where the team already works.
The engagement was scoped at three AI employees and bought as four before kickoff, which set the pattern for the build: cover the whole cycle at once so no workstream is left as the one that gets dropped under load.
What changed
Four workstreams that used to compete for the same hours now each have something working them continuously, so a live deal no longer stalls the reporting calendar and reporting no longer stalls sourcing.
Deployment inside the firm's own tenant meant no change to where documents live or who has access to them.
This engagement kicked off in July 2026 and is deliberately published without a time-saved figure. We would rather show what was deployed than print a number the engagement has not earned yet.
Questions
What did PSV build for Accomplish Collective?
Four AI employees covering deal sourcing and underwriting, monthly asset-management reviews, and quarterly investor reporting, running inside the firm's own Microsoft 365 tenant and Claude workspace.
What changed for Accomplish Collective?
Four workstreams that used to compete for the same hours now each have something working them continuously, so a live deal no longer stalls the reporting calendar and reporting no longer stalls sourcing.
Who stays in control of the work?
Nothing moved to a PSV system. The work lands where the team already works, under the access it already has.
Where do these numbers come from?
Kicked off July 2026. These counts describe what was deployed, not what it has returned. No time-saved figure is published yet.
See what this looks like on your workflow.
See how we build firm systemsMore case studies