CASE STUDY

Venture Studio.

A First Strategy case study.

Company name is held in confidence.

PDF Download the full case study (PDF).

The story

Venture studio

A missed deal makes no sound

A three-principal medtech venture studio acquires university and lab IP and develops it into pre-revenue clinical assets, against a thesis sharp enough to kill most of medtech on sight. Its deal flow ran on the CEO's own reading hours, one opportunity at a time, in a market of hundreds of commercialization sites and a research literature nobody could read by hand. The deals the studio never saw cost it nothing it could measure and everything it was for.

What was at stake

The model has no slack in it. Three principals run three live programs against a target of three to five vetted opportunities a quarter, with about five thousand dollars of specialist time committed every time a candidate reaches deep diligence. The CEO had been spending evenings on a custom GPT that remembered nothing from one session to the next, and a full day on one university negotiation for one deal from one source. The growth ceiling was a single person's reading capacity, and the loss it caused was invisible, because a missed deal makes no sound.

Where the bottleneck actually was

The visible symptom was the CEO's hours. The deeper read was that his hours were the wrong asset to spend. The studio's edge is judgment: a thesis that filters most of medtech out on sight, and specialists who can tell an engineering problem from a science project. The constraint is reading. Hundreds of commercialization sites publish technology continuously, roughly five journals per research category sit upstream of them, and one person reading by hand covers a rounding error against any of it.

We traced one opportunity from the lab that produced it to the decision the studio made about it. Of the five investment gates the studio runs, three are data disciplines wearing judgment's clothes: the patent landscape is searchable, the regulatory pathway is a predicate lookup, and acquisition appetite is M&A history. The other two, whether a device can be manufactured and tested inside the budget and the timeline, stay human, because that judgment is the studio's product. The scarcest asset in the building, specialist time, was being spent partly on a machine's work.

The CEO's instinct had been to chase the upstream research first, because really good technology often never reaches a transfer office at all. The instinct was right and expensive: the studio had the receipt, a funded university research project with multiple possible use cases and no certainty which product it would become. Going upstream meant paying for the future before it was investable.

The strategic shift

Instead of pointing the build at the upstream research, exhaust the downstream commercialization inventory first. The transfer inventory is sitting stock: engineered, often validated, listed by someone whose job is to sell it. The cheap test is to read the downstream commercialization inventory broadly enough to prove whether it is insufficient, then pay to go upstream only when the evidence says to. The CEO talked himself out of his own sequence once the costs went on the whiteboard, which is the better way for that to happen.

The architectural rider mattered more than the sequence. The machine that reads a commercialization site must not care it is reading a commercialization site. Point it at a journal next year and the funnel downstream is identical. The insight was not abandoned. It was sequenced, and the architecture made the sequencing reversible.

How we built it

The build ran in three phases, one month each, fixed fee per phase, each phase independently valuable, stop at any boundary. Phase one stood up the agents and the database. One agent per source, runs watched by hand, every call checked. The commercialization sites share a purpose and almost nothing else; each one failed differently before it ran clean. Everything the agents read went into the database, relevant or not, because relevance is a function of a thesis that moves and re-scoring a stored record is free.

Phase two encoded the judgment. The thesis screen made its calls and a human made the same calls blind, and the gap between them was the number that mattered. Early, the gap was wide. That was the plan. A screen wrong in measured ways improves; a screen wrong in unmeasured ways lies to you. The feedback loop ran from the first gate, the CEO's corrections flowing back into a matrix that carried version numbers like code. Each surfaced candidate arrived as an intelligent brief: what it is, why it fits the thesis, what the gates found, readable in minutes.

Phase three made expansion cheap. The differences between sources turned out to be configuration, not code, and the engine generalized until a new source onboards from its URL. Adding a source stopped being a project and became a decision.

The discipline that kept trust honest was the unglamorous one. The discard pile gets sampled by a human every week, because a wrongly surfaced candidate costs minutes and a wrongly killed one is invisible forever. More than one correction that taught the matrix something came off the pile that was supposed to be noise.

What changed

A three-principal team now runs the deal review of a firm thirty times its size. The specialists' five-thousand-dollar hours are spent only on candidates the funnel has earned. The CEO's job inverted: he started as the funnel, the man whose evenings were the studio's sourcing capacity, and is now the judge of what the funnel surfaces.

Reading capacity moved from one opportunity at a time, by hand, to hundreds a week by machine, with headroom to thousands. New deal sources onboard from a URL, so coverage compounds without builds. The qualification matrix versions like code; when the thesis moves, it re-scores the entire stored database overnight, and last January's near-miss can resurface as this June's candidate without touching a single source.

Underneath the throughput, the database compounds. Every opportunity the engine has ever read is logged with its source, researchers, summary, and categorization. The studio holds a proprietary record of the medtech IP landscape that would be hard for a competitor to justify building by hand, and it grows with every run. The methodology stayed NDA-gated and unpatented; the public record describes the shape, not the recipe.

What stands as proof

The trust moment was not a demo. It was the CEO working through a morning's briefs in the time a single raw listing used to take, and realizing the reading was now happening continuously, while he slept and while he ran his three live programs.

The other test was a quieter one. A source restructured its site, and the agent reading it did not break. It returned thin, run after run, errors zero, volume down. No error log would have caught it. The per-source volume baselines did, the agent was reconfigured and re-watched, and the rule it confirmed went standing: in a system built to make invisible misses harder to repeat, silence is a symptom, and aggregate health is not health.

The downstream inventory has not yet run thin, so the journals, the expensive upstream move, remain unspent. The downstream inventory is still producing candidates.

The operator takeaway

The bottleneck in a small expert team is rarely the experts. It is the work below them: the reading, the cataloging, the listing that has to happen before judgment can be applied. Move that work to a machine that does not skim and does not tire, and the team's ceiling stops being its hours and starts being its judgment. The methodology is the company; protect it, version it, and make sure every decision keeps teaching it.

Where each of these started.

Every one of these engagements started with a day. A fixed-fee day in the business with leadership. Real work, not slides. A playbook within two weeks. Then a decision.

Start with a Day One

How it starts.

A day.

A fixed-fee day in your business with your leadership. Real work, not slides. Two weeks later you have a playbook, yours to run with us or without us. Day One.

A build.

You know what you want built. Tell us what it is. Inquire.

A team.

The systems are there and your people are not using them. We start with the work they actually do. Inquire.