The venture studio shared team model is simple to state. One central team of builders, recruiters, lawyers, finance people and engineers works across several companies at once, instead of every startup hiring all of those functions alone. The studio pays for that team, the ventures plug into it, and the studio takes equity for the work.
That is the brochure version. The useful version answers three harder questions: what should actually be shared, where the model breaks, and what changes when the company is built on science rather than software. That last one is the part almost nobody writes about, and it is the part we live in every day.
If you want the full studio lifecycle first, read how venture studios work. This piece zooms in on the team.
What the shared team model actually is
Most mature studios run on two linked entities. The operating company employs the shared team, engineers, designers, recruiters and finance, while a separate studio fund raised from LPs supplies the pre-seed and seed capital. The studio earns equity for sweat. The fund earns equity for cash.
The alternative it replaces is what Tim Keller at UC Davis calls the solo-company ratchet: every idea gets its own company, and that company develops through rounds where it gives up around 20 percent of ownership every time it raises. Each new company hires its own lawyer, its own bookkeeper, its own first engineers, and learns the same lessons from zero. Keller's fix, built on watching more than 40 companies come through his incubator, is the studio logic in one line: instead of building one company at a time, build a system for building many.
The shared team is that system.
What gets shared, and what never should be
The usual shared layer
The list is fairly consistent across studios. A centralised layer covering product, legal, finance, HR, IT and marketing infrastructure that every portfolio company draws on, plus playbooks for hiring, fundraising and go-to-market. Studios also tend to keep engineers and designers who rotate across portfolio companies during the zero-to-one phase, which is exactly when a solo founder cannot afford senior talent.
In practice that means:
- Entity formation, cap table and standard contracts done once, reused many times
- A recruiting pipeline that is already warm when a venture needs its first hire
- Finance ops, payroll and reporting on one stack
- Design and engineering capacity for prototypes and first builds
- Playbooks that encode what the last venture learned
What stays inside the venture
The shared team handles the plumbing. It cannot own the company. Vision, customer relationships, the sales motion and culture belong to the founding team from day one, and a studio that tries to run those centrally ends up with portfolio companies that look identical and fail identically.
A good test: if the founder disappeared tomorrow, would the venture still know who its first ten customers are? If only the studio knows, the shared team has reached too far.
Why it is faster: the economics of reuse
Speed in this model comes from reuse, not from working harder.
Fractional senior talent. A single venture cannot justify a full-time finance lead. Five ventures sharing one can, and the quality goes up because that person has done the job before. The same logic applies to a patent attorney, a grants specialist or a head of manufacturing.
Compounding playbooks. The same source puts it well: the first company learns how to hire a sales rep the hard way, the fifth inherits a tested process. Every venture makes the shared team better at the next one.
Day-one infrastructure. Legal formation, recruiting and finance ops come from the shared services team instead of consuming the founder's first six months. One engineering studio compares tech setup at days in a factory model against weeks or months for a traditional startup.
Smaller, smarter bets. This is the deep-tech argument. When every milestone needs a priced round, founders are pushed toward fewer, bigger raises and lose the ability to fund small experiments that move the needle, which is Keller's critique of the ratchet. A shared team with its own capital can fund a two-week test without a cap table event.
Where the model breaks
The pages selling studios rarely cover this, so here it is.
Contention for the same people
Shared means scarce. When two ventures need the same lead engineer in the same month, one of them waits. Mature studios know this and cap their throughput: most successful factories limit output to 3 to 4 high-quality ventures per year. A studio claiming twenty launches a year with a fifteen-person team is either very good at saying no internally or not doing much for each one.
Ask how priority gets decided when two ventures collide. "The partners decide" is an honest answer. "That never happens" is not.
The graduation cliff
At some point the venture has to stand alone, and every function the shared team provided must be rebuilt inside the company. Studios describe a graduation phase where the studio's role shifts from operations to ownership. Done well, it is a planned hand-off with documentation and a hiring plan. Done badly, a company that looked fully staffed discovers it has no finance function the week after its Series A.
The cost hides in the cap table
The shared team is not free. Founders usually do not pay for it in cash, they pay in the studio's equity stake. That is a fair trade when the team is real and senior. It is a bad one when "shared services" means a template folder and a monthly check-in. Compare what you get against how much equity venture studios take, and see the venture studio business model for how the studio funds the bench before any venture pays back.
Watch the mix, too. A studio staffed entirely with investors or consultants will struggle to build real companies. You want operators who have shipped.
The shared team in a deep-tech build
Almost every description of the shared team assumes a software company: design system, growth marketing, a cloud account. Science-based ventures need a different shared layer, because they fail for different reasons.
Keller's experience with those 40 deep-tech companies is blunt: most failures were not because the technology did not work. They came from human and strategic mistakes, often rookie errors by academic founders, or from being crushed slowly by the capital needs of commercialisation. Both are things a shared team can fix. Neither is fixed by a better landing page.
So in a deep-tech studio the shared team looks like this:
- IP. Patents filed before a conference talk kills novelty, and a portfolio strategy across ventures, not one filing at a time.
- Capital sequencing. Grants and public funding lined up against equity so dilution stays sane across a long development cycle.
- Manufacturing and deployment. People who can get hardware built, shipped, installed and serviced in the country where it runs.
- Operators. Trained crews who can commission and run a plant, not only people who can run a sprint.
This is how EX EPIC is built. One shared team carries the patents, the funding, the manufacturing and the field work across the portfolio, which is why the numbers are deployment numbers: a track record above 160 million euros financing, patenting and deploying deep tech, 200 or more waste-to-energy units across 11 countries, 24 patent families filed with roughly 100 more validated in the pipeline, and 250 or more operators trained and placed into the portfolio. No single startup could hire that bench. Shared across ventures, it pays for itself. More on that model in deep-tech venture builder.
The bench is shrinking
One real shift is worth naming. The classic studio scaled by hiring: an in-house team of 30 operators lent out to each portfolio company. Some studios now argue for a senior team of around ten on shared agent infrastructure, where software handles the volume work and people handle judgment. Another claims a three-person AI-native studio now does what a fifteen-person studio did five years ago.
For software ventures, believe a version of that. For deep tech, be careful. Agents can draft a patent landscape, a grant application or a financial model. They cannot commission a gasifier or train a crew on site. The shared team in a science studio gets leaner on paperwork and stays heavy on hands. That is the bench worth paying equity for.
Questions to ask a studio about its shared team
Before you sign, get straight answers to these:
- Who exactly is on the shared team, and what have they shipped? Names and track records, not functions on a slide.
- How many ventures is the team supporting right now? Compare with the 3 to 4 per year that careful factories stick to.
- What happens when two ventures need the same person? You want a rule, not a shrug.
- What is the services contribution worth at cost? Separate cash invested from services valued, so you know what the equity buys.
- What is the graduation plan? When does each function move in-house, and who helps hire it?
- For deep tech: who files the patents, who sequences the grants, and who has deployed hardware before?
A studio that answers all six clearly has a real shared team. One that gets vague on the first two is selling a brand.
FAQ
Is the shared team the same as a startup accelerator's mentor network? No. An accelerator gives advice on a fixed term to companies that already exist. A studio's shared team does the work itself, inside the venture, often before there is a founder. Mentors suggest. The shared team ships.
Can a founder bring their own team into a studio? Often yes. Some studios recruit founders to run ideas they originated, others take existing founders and plug them into the shared backbone. Either way, check which functions you keep and which you hand to the studio, because that split drives the equity.
Does the shared team model work outside software? It works better in hard tech than people assume, because the scarce skills there, patent strategy, grant funding, manufacturing and field operations, are exactly the ones a single early company cannot afford to hire full time.