Tech due diligence advisory
A global tech due-diligence advisor
We started by building two new tools the firm didn't have, and once those proved out, the client trusted us enough to let us touch their main product. From there the work kept compounding.
What we did, by area
Before
The client is a global advisory firm whose consultants do the technology due-diligence work behind hundreds of private-equity deals each year. Over more than a decade they had built an enormous archive of past assessments that, on paper, was the firm's competitive moat. The data was there. It just wasn't doing much for them in real time.
The first bet
Two tools they didn't have yet
We started with two new builds because they were the safest places to prove ourselves. The first was a staffing tool that ingested a candidate's resume, scraped their LinkedIn, tagged their experience, and matched them to the right kind of project, producing a defensible answer to the question every services firm asks every week. The second was a workforce classifier that took a client's organizational data and classified every employee by role and seniority, with the reasoning shown for each one. Slow, manual analysis turned into fast analysis with the work visible.
What we noticed
Both tools worked, so the client let us into their main product. We started shipping fully-vetted features into their core codebases at roughly a third of the time their internal teams took, by collapsing what is normally a four-role handoff (analyst, product manager, designer, engineer) into a single operator-engineer who could move from sketch to merged PR without losing a week to coordination.
How we work in their codebase
We work on the what. The agent works on the how.
What we focus on
- 01Which features are actually worth building
- 02What good looks like for the business
- 03Talking to the people who'll use it
- 04Reviewing what the agent ships before it lands
- 05Picking what to do next
What the agent does
- 01Reads the ticket
- 02Walks the codebase
- 03Writes the code
- 04Opens the PR
- 05Runs the tests
- 06Waits for review
Most of our PRs come back overnight. We come in the next morning, review, merge what's good, and pick the next batch.
What we built next
A shared starting point for everything
We built a production-ready scaffold every new product could start from, which meant each new build got cheaper than the last and the firm stopped re-solving the same plumbing problems on every project.
The archive, made useful in real time
We built a tool that puts thousands of past assessments in front of a partner during a live call with a private-equity firm, turning the archive from something the firm referenced after the call into a tool they use during it.
A new system to replace the old one
The legacy system the firm runs on was built years ago and was getting in their way. We're replacing it with a new platform built around how they actually work today, and we could only do this because the earlier work made it possible.
How they use it now
Working sessions twice a week. Both teams are getting faster, and patterns we use are starting to show up inside their organization.
What's now possible
The firm's archive answers questions during a deal call, not after one. Each new product they want to build is cheaper than the last, because the platform underneath does more of the work. And inside their own engineering organization, the way Runpoint people ship has become a reference point.
“I don't think I've ever heard the term operator engineer, but I think it fits really well for what you guys do… I've found with you guys, I can just let you go to these meetings by yourselves. I don't even need to be there.”
Client lead
These are real quotes from real clients. We anonymize on the site until each one says yes to being named. Most are in the queue. References available now.