Origination systems
A deal platform inside a family office’s CRM
The same family office, after the roll-up market was built
- Systems of record1Everything lives in the client’s Salesforce and AWS account
- Team operating it3No developer on staff; ours maintain it
- Modules on the same infrastructure2Deal sourcing and recruiting
Mandate
The brief, in one table
- Client
- The same family office, after the roll-up market was built
- Sectors
- Accounting practices, business services
- Engagement
- Origination systems
- Figures as of
- September 2026
The mandate
With the market mapped, the family office wanted the engine to live where the team already worked: their CRM, their cloud, their accounts. Nothing in a vendor’s system, nothing that stops when a contract does.
What we built
The sourcing tool was kept inside Salesforce with an API layer beside it, so the fit score, the research memo and one-click outreach sit on the account record. When the platform needed to hire, the same infrastructure took a recruiting module in two months instead of a second system.
The result
One system of record, one login, and a pipeline the family office owns outright. Sourcing is throttled or paused by the client as deals move through diligence, which is the point: the volume is theirs to set.
Next case study
Add-on origination for a private equity firm
Nine add-on categories worked at once. At full capacity the engine contacts 3,000 owners a month; at this mandate’s rate that is about 55 owner conversations a month for the deal team, every one at or above the size floor. Three letters of intent in the first two months.
Next step
Bring the thesis. We bring the owners.
Thirty minutes with the managing partner on your criteria, the markets we would work, and what the first conversations look like.
