For operating partners and value creation teams

Turn how your portfolio companies work into AI they own.

RideAlong watches how work actually gets done inside a portfolio company, builds the agents and software to do it, and measures every build against the work it replaced.

  1. 01ObserveRide along with one function in one portfolio company.
  2. 02LearnModel how the work really runs, exceptions included.
  3. 03BuildAgents, skills and small software for that function.
  4. 04DeployInto the company’s own workflows, reviewed by its team.
  5. 05EvaluateMeasured against the work it replaced. Evidence for the board pack.
  6. 06ImproveThe team’s corrections feed the next version.
wk 01 · company a · claims intake · observe wk 02 · company a · learn · 1 workflow · 3 exceptions wk 03 · company a · build · agent intake-triage v1 wk 03 · company a · deploy · claims team reviews wk 04 · company a · evaluate · 2 corrections wk 05 · company a · improve · intake-triage v2 wk 05 · company b · revenue cycle · observe wk 08 · portfolio · 6 live builds · 2 companies wk 09 · company c · monthly close · observe illustrative · not customer data

Why private equity

The plan says what should change. The work is where it changes.

Most portfolio AI programs end with a deck and a list of opportunities. Then management has to build it, inside a hold period. RideAlong builds it.

  1. 01

    One operating team, every company

    Finance close, claims, collections, onboarding, reporting up to you. The same shapes repeat across the portfolio, so each deployment is faster than the last.

  2. 02

    Evidence is the deliverable

    Every build is measured against the work it replaced, on the metrics in your value creation plan. Not projected hours saved. What each agent did, who reviewed it, what changed.

  3. 03

    It belongs to the asset

    The code and the model of how the company works belong to the portfolio company. Part of the asset at exit, not a subscription that ends with the hold.

Inside a hold period

Weeks to the first build. Not a quarter to the first slide.

One illustrative path through one portfolio company. The pace varies. The shape doesn’t.

  1. Weeks 1–201

    Observe one function.

    Your value creation plan names the function. RideAlong rides along with the people doing the work and comes back with how it actually runs, exceptions included.

  2. Weeks 2–602

    First builds, reviewed by the team.

    Agents for the repeatable parts, software where a spreadsheet was holding on. The people who did the work by hand review them first.

  3. Quarter 103

    Evidence for the board pack.

    Each live build measured against the work it replaced. What kept running, what was corrected, what was retired.

  4. Then04

    The next function. The next company.

    The loop expands when the first team asks for it. The operating partner sees every live build across the portfolio in one place.

Illustrative sequence, not customer data. Timings vary by function.

The portfolio view

Every live build, every portfolio company, on one page.

Illustrative portfolio. Not customer data.

portfolio · live builds · this week
CompanyFunctionLive buildsStateLast evidence
Company Aspecialty insuranceclaims intake3runningreviewed by claims lead · 1 correction
Company Bhealthcare servicesrevenue cycle2runningno corrections this week
Company Cbusiness servicesmonthly close1evaluatingfirst cycle · finance reviewing
Company Dlogisticsdispatch reporting—observingweek 1 of 2
Company Econsumer——nextobservation agreed with management
what each build did · who reviewed it · what changed · nothing shared between companies

Governance

Portfolio-wide by design. Settled company by company.

The fund opens the door. The portfolio company decides what happens inside it.

  1. 01

    Management says yes first.

    Sponsored by the fund, run with the portfolio company. Its CEO and function lead agree the scope before observation starts, and their team reviews every build.

  2. 02

    Nothing crosses between companies.

    Each portfolio company’s observations and builds stay inside that company. The fund sees status and evidence, not the work itself.

  3. 03

    Observation is agreed, not assumed.

    Who is observed, which tools, who sees what. Settled in writing before anything is captured. How we handle data.

  4. 04

    It leaves with the asset.

    At exit, the builds go with the company. No vendor lock, nothing to renegotiate in the data room.

Every company in the portfolio already knows how to do its work. It should own what that knowledge can build.

Operating partners spend the hold period turning a thesis into operating change, one management team at a time. RideAlong puts that change into the work itself.

Intelligence each portfolio company owns, compounding until exit.

Bring one portfolio company
and one function that costs too much.

We’re working with a few operating teams as design partners. Tell us the company and the function, and we’ll tell you what the loop would do with it.

Talk to a founder hello@joinridealong.com