Use casesPrivate equity

Build shared AI memory for your portfolio.

Carrow Street owns fourteen software companies. At the largest, the token bill had become a board-level line and 380 developers were learning the same lessons separately. The first rollout took eleven days to prove value. The second, seeded from the firm's playbook, took four.

Organisation
Mid-market buyout firm, fourteen portfolio companies, mostly software
First rollout
Albery, property management software, 380 developers
Second rollout
Fenwick, logistics SaaS, 90 developers
Agents in use
Claude Code, Cursor and Copilot in engineering; Claude on month-end close and the board pack
Tools connected
GitHub, Jira, Confluence, Slack
Memory networks
One tenant per company; a firm playbook at Carrow Street that no company can write to directly
Residency
Dedicated tenant per company in its own region; on-prem where a company requires it

01Starting point

Where Carrow Street started

Carrow Street's operating partners bring agents into every acquisition inside the first hundred days. Engineers get Claude Code and Cursor on the repos. Finance gets an agent on the month-end close and the board pack. Every company gets the same kickoff deck, the same prompt files and the same checklist, and every company starts from zero.

Albery was the company that made it urgent. A new CTO had been brought in with a mandate to adopt agents aggressively, and did. Within two quarters agent spend was a seven-figure annual line in the board pack, and 380 developers were each discovering the same things about a twelve-year-old codebase: which tables were tenant-scoped, why the lettings service had two payment paths, which migrations locked. The firm's platform team ran the same six weeks of correction at every company and watched the lessons stay where they were paid for.

The cost landed in the hundred-day plan and in the exit. Every rollout took the same six weeks before an operating partner would accept the agents' work. Prompt files copied between companies went stale within a quarter and carried no record of what had held. When a company exited, everything its agents had learned exited with it, and the next acquisition began the six weeks again. Nothing the firm had learned about deploying agents was anywhere an agent could read.

02Day one

Day one

Albery's platform team connected its agents in an afternoon. The firm's playbook network took a day to draw with the operating partners, and the rule that matters took longer to agree than the software: no company writes to the playbook directly.

  • Claude Code, Cursor and Copilotmemco plugin in Albery's engineering baseline, signed in through Albery's own identity provider. The firm has no accounts at the company.
  • Claude on financeMCP connection for the close and board-pack agent, knowledge-work domain. Reviewers in finance preview each proposed lesson before it is saved.
  • GitHub and JiraPull request outcomes, review comments and tickets attach to insights as evidence inside Albery's tenant.
  • The firm playbookA separate network at Carrow Street, readable by every portfolio company, written to only through a reviewed abstraction gate.
  • SeedAlbery's platform lead turned the firm's kickoff checklist and its own prompt files into fifty insights with scope and source. The hundred-day deck became eight playbook entries.
  • SparkAlbery's tenant administered by Albery. The playbook administered by the firm's two-person portfolio platform team.
  1. Firm playbook, at Carrow StreetApproved, abstracted patterns: how to run a parallel-ledger cutover, pull request standards, incident patterns, what the board pack leads with. Nothing that names a company, a customer or a figure.Every portfolio company's agents. Written to by nobody except through the gate.
  2. Albery, the company networkEngineering standards, security rules and finance policy for Albery.Everyone at Albery.
  3. Albery platform and team networksRepo conventions, tenant-scoping rules, migration patterns, dead ends.Albery engineers with access to those repos.
  4. Albery financeClose procedure, board pack format, the controller's standing corrections.The finance agent and its reviewers.
  5. PersonalEach person's own preferences.That person's agents only.

fig. 01Scope map

Carrow Street and Albery memory networksTwo tenants side by side: the firm playbook at Carrow Street, read by every portfolio company and written only through a reviewed gate, and Albery's own tenant with its platform, team and finance networks; the dashed route is the abstraction gate from Albery to the playbook.CARROW STREET · FIRM PLAYBOOKAPPROVED PATTERNS, NO COMPANY NAMEDParallel-ledger cutoverPull request standardsBoard pack orderIncident patternsALBERY · COMPANY TENANTadministered by AlberyALBERY NETWORKSPlatformLettingsBillingFinancePersonal · one per personABSTRACTION GATEEvery company reads the playbook · No company reads another
Carrow Street and Albery memory networksTwo tenants side by side: the firm playbook at Carrow Street, read by every portfolio company and written only through a reviewed gate, and Albery's own tenant with its platform, team and finance networks; the dashed route is the abstraction gate from Albery to the playbook.CARROW STREET · FIRM PLAYBOOKAPPROVED PATTERNS, NO COMPANY NAMEDParallel-ledgercutoverPull requeststandardsBoard pack orderIncident patternsALBERY · COMPANY TENANTadministered by AlberyALBERY NETWORKSPlatformLettingsBillingFinancePersonal · one per personABSTRACTION GATEEvery company reads the playbook · No company reads another
Two tenants, no shared pool. Every company reads the playbook; no company reads another. The dashed route is the abstraction gate: a lesson promotes, its evidence does not.

03The first weeks

The first weeks

Albery's first weeks looked like any engineering rollout: corrections becoming insights, a wrong scope caught, a stale rule retired. What was new for the firm came at week seven, when the second company started ahead.

fig. 02Deployment timeline

Carrow Street: first rollout to secondTimeline across two segments: Albery's first weeks from the baseline fortnight to its first reuse on day eleven and the gate holding a named customer on day fourteen, then week seven when Fenwick connects and reuses a playbook lesson on its fourth day.BASELINE FORTNIGHTALBERY ROLLOUTFENWICK ROLLOUTDAY 21DAY 56DAY 11First reuse at AlberyDAY 53First reuse atFenwick, day fourDAY -14Baseline at AlberyDAY 0Albery connected;fifty insights seededDAY 3Lettings querycorrectionDAY 8Board pack correctedDAY 14Gate holds a namedcustomerDAY 19Migration patternscopedDAY 49Fenwick connects,reads the playbook
Carrow Street: first rollout to secondTimeline across two segments: Albery's first weeks from the baseline fortnight to its first reuse on day eleven and the gate holding a named customer on day fourteen, then week seven when Fenwick connects and reuses a playbook lesson on its fourth day.Baseline fortnightAlbery rolloutFenwick rolloutDAY -14Baseline at AlberyDAY 0Albery connected; fifty insights seededDAY 3Lettings query correctionDAY 8Board pack correctedDAY 11First reuse at AlberyDAY 14Gate holds a named customerDAY 19Migration pattern scopedDAY 49Fenwick connects, reads the playbookDAY 53First reuse at Fenwick, day four
Two segments with a break between them. The filled marks are the first reuse at each company: eleven days at Albery, four at Fenwick.
  • Day 3. A reviewer rejects an agent's query on the lettings service for the third time that week.Every query in the lettings service is scoped by agency_id. A query without the scope is a data leak between customers, not a bug.Day eleven: an agent in a different team, on the reporting service, applies the rule unprompted. First reuse at Albery. The reviewer stops writing the comment.
  • Day 8. The finance agent nets one-off costs into the operating line on the board pack and the controller rewrites the page.The board pack shows gross margin before and after one-off costs, with one-offs on their own line. Never net them.Previewed and saved by the controller. The correction does not recur at the next close. The abstract version, with no figures, becomes the first playbook entry promoted through the gate.
  • Day 14. An Albery insight about running old and new ledgers in parallel for two closes is proposed for the playbook with a customer's name in it.Run old and new ledgers in parallel for two closes before cutover. Reconcile at account level, not at the total.The gate holds it. The operating partner and Albery's CTO approve a rewritten version with the customer, the system names and the figures removed. The rule for the playbook becomes explicit: a lesson promotes, its evidence does not.
  • Day 19. An agent applies a migration pattern from the lettings service to the billing service, where the table is small and the pattern wastes a day.The nullable-column-plus-backfill pattern applies to tables over ten million rows. Smaller tables migrate in place.Scope narrowed to the large-table services. Albery's platform lead adds a rule: an insight that names a pattern must name where it applies.
  • Week 7. Fenwick, the second company, connects. Its agents read the playbook on day one.Pull requests open with the ticket, a one-line risk statement and the rollback step. Parallel-ledger cutovers reconcile at account level.Fenwick's first reuse comes on day four, from a lesson Albery paid for. Its own six weeks of correction becomes two. Nothing from Albery's tenant was readable at Fenwick; only the abstracted rule travelled.
  • Month 9. Carrow Street sells one of the fourteen companies.A company's tenant leaves with the company. The playbook keeps only what the gate approved.The company exports its memory in a portable format and takes it. The firm's playbook is unchanged, because nothing in it ever identified the company.

04Governance

Governance

  • One tenant per company, administered by the companyEach portfolio company has its own tenant, its own identity provider and its own validation rules. The firm has no accounts in them and reads nothing from them.
  • The playbook is written only through the gateA lesson reaches the firm playbook when an operating partner and the originating company's CTO approve an abstracted version. The evidence stays in the company's tenant. The playbook carries the rule, never the figures, the customer or the system.
  • Downward reads, never sidewaysEvery company reads the playbook. No company reads another. There is no firm-wide pool and no blended commons.
  • Provenance at both levelsInside a company, every insight links to the pull request, ticket or correction it came from. In the playbook, every entry records which company proposed it, who approved it and when, without exposing the source.
  • Exit, audit and residencyA company that exits takes its tenant and its memory with it in a portable format, under the enterprise terms. Every read, write, promotion and retirement is logged in both places. Each tenant sits in the region its company requires.

fig. 03The write path

From a controller's correction to another company's agentSwimlane showing Albery's controller correcting the board pack, the finance agent proposing the lesson, Albery's tenant serving it, the operating partner and Albery's CTO approving an abstracted version for the firm playbook, and Fenwick's agent reusing it on its fourth day.ALBERY CONTROLLERALBERY FINANCEAGENTALBERY TENANTFIRM PLAYBOOK GATEFENWICK AGENTRewrites theboard pack pageday 8Proposes: one-offcosts on theirown lineServed insideAlberyTWO APPROVERSAbstracted;partner and CTOapproveReads theplaybook; appliesitday 4 at Fenwick
From a controller's correction to another company's agentSwimlane showing Albery's controller correcting the board pack, the finance agent proposing the lesson, Albery's tenant serving it, the operating partner and Albery's CTO approving an abstracted version for the firm playbook, and Fenwick's agent reusing it on its fourth day.ALBERY CONTROLLERRewrites the board pack pageday 8ALBERY FINANCE AGENTProposes: one-off costs on their own lineALBERY TENANTServed inside AlberyFIRM PLAYBOOK GATE · TWO APPROVERSAbstracted; partner and CTO approveFENWICK AGENTReads the playbook; applies itday 4 at Fenwick
The dashed node is the abstraction gate: an operating partner and the originating company's CTO approve a version with no customer, figure or system in it.

05What compounded

What compounded

Albery's readout was an engineering readout. The firm's readout was the difference between the first rollout and the second. By the end of the year nine companies were connected and the playbook held forty entries.

MetricMovementWhy
Time to first proven valueDay 11, then day 4Day eleven at Albery, day four at Fenwick. Fenwick started from forty playbook entries instead of a kickoff deck. The third company, in month five, took three days.
Cross-person or agent learning gainEvery entry, two companies or moreThe parallel-ledger rule was reused at four companies in the year. Albery's engineers never knew it had travelled.
First-pass acceptance61% to 79%At Albery by month three, measured on agent-opened pull requests. The finance agent's board-pack pages went from two rewrites a close to none.
Repeat-error rateSix weeks to twoThe six-week correction period became two, measured at Fenwick as the time until an operating partner accepted agent work without a standing list of corrections.
All-in cost per accepted resultTokens per PR down 41%Albery's tokens per merged pull request, counted after reads. At seven figures of agent spend a year, the reduction paid for the agreement across the portfolio several times over.
Improvement with experienceEach rollout shorterThe playbook is the firm's asset, not any company's, and it survives exits, model changes and the next acquisition.

fig. 04Rollout after rollout

Days to first proven value, by rolloutBar chart: eleven days at Albery, four at Fenwick, three at the third company.3691211Albery, first4Fenwick, second3Third companyDays to first proven value
Days from connection to the first reused lesson that improved a later task, for each company connected in the year.

fig. 05Costs before it pays

Tokens per merged pull request at AlberyLine chart indexed to Albery's baseline: 105 in week one, crossover in week two, 80 by week four and 59 by month three.607590100BASELINECROSSOVER10559WK 1WK 2WK 4MO 2MO 3Tokens per merged pull request, Albery
Index, Albery's baseline fortnight = 100, counted after reads. At seven figures of agent spend a year, the gap is the agreement several times over.

06What it cost

What it cost

  • Setup timeOne afternoon per company for the plugin and MCP connections, plus a day to seed from its own prompt files. The firm playbook took a day to draw and three weeks to agree the gate.
  • Who ran itThe firm's two-person portfolio platform team and each company's platform lead. One operating partner spends about an hour a fortnight approving playbook promotions. No new hires at the firm or the companies.
  • Licence and tokensAn enterprise agreement at the firm level covering named portfolio companies, each on its own tenant with unlimited users and agents inside it. At Albery, reads added five percent to token use and the net bill per merged pull request fell by two-fifths.
  • What it replacedHand-copied prompt packs, the hundred-day deck, and the six-week correction period at every new acquisition.

Make the second rollout faster than the first.

Join the waitlist

More deployments.

All use cases