What your agent reads.
- name
- foundry-vs-solo
- description
- Whether to co-found a cybersecurity company inside a venture foundry or studio, or to found solo and raise a seed. Covers the one structural difference between the two routes (who chose the problem), what a foundry supplies at formation (a first check, an operating partner in the seat beside you, a network of security leaders, a recruited team, a shared back office), what it costs (a share set at formation rather than by a priced round, a board that is also a co-founder, an exit list shaped by the fund's relationships), why an introduced buyer's yes is cheap on either route, the odds-against-ownership trade, and the question that decides it. Use when a founder is recruited by a foundry, is weighing a studio's offer against raising a seed, or is a first-time technical founder without a commercial partner. Not for who leads a seed (who-leads-cyber-seed), whether to raise at all (bootstrap-or-raise), or which founder is chief executive (who-is-ceo).
- title
- Foundry or solo
- question
- Should I co-found inside a foundry or found solo and raise a seed?
- subtitle
- Your ownership gets set at formation by agreement, rather than by a market price.
- summary
- You are choosing between two honest routes, and the difference that drives everything else is who chose the problem. A foundry supplies a network, a team and a first check in the week you start, and prices that at formation rather than at a priced round; going solo is slower and cheaper and keeps the problem yours. Read the trade as odds against ownership, and decide which one you will regret less.
- group
- before
- verified
- 2026-09-08
- order
- 13
960 / 1024 characters
This is the top of the SKILL.md file, exactly as it downloads. Your agent reads the description field to decide when to load this skill. The rest of this page is for you.
You are choosing between two routes that both work, and the difference that drives all the others is who chose the problem. In a foundry the idea generally starts with the fund and the founder is recruited to build it. Solo, the problem is yours and the money follows it. Good security companies have come out of both, and we invest alongside foundries in companies we did not start. What follows is the trade, in the shape a founder has to weigh it.
What a foundry supplies in the first week.
You get, in a week, things a solo founder spends a year assembling. A first check with no pitch. An operating partner in the seat beside you, who has done the commercial work you have not. A network of security leaders who answer the phone. A recruited team, a shared back office, an office, and a brand that opens a door before you have a product.
None of that is decoration. For a first-time technical founder with a deep problem and no commercial partner, it fills the exact gap that kills most companies at that stage, and it fills it in the first quarter rather than the fourth. The routes are not equally risky, and pretending otherwise is not honesty.
What it costs, stated plainly.
You give up a share of the company set at formation rather than by a priced round, and it is larger than a seed round takes. That price is paid before there is a product, which is the point of it from the fund's side and the cost of it from yours.
You get a board that is also your co-founder. That cuts both ways: the person who evaluates you is the person you disagree with, and also the person who has to make it work and cannot walk away from the outcome. And you inherit a list of possible acquirers shaped by the fund's relationships, which is a real asset on the day you need it and a shape you did not choose.
An introduced buyer's yes is cheap on either route.
You will hear that the network is the product, and it is worth having. Know what it buys. An introduction buys a warm meeting, not a budget, and that is as true of ours as of anyone's. A foundry supplies introductions at scale, so its design partners arrive with the same caution any introduced buyer carries: the yes cost them nothing.
The test of fit is therefore the same on both routes, and it is worth writing down before you start either one. A cold close, from a buyer who did not already trust the fund or you. Until there is one, what exists is a thesis with a staff, and a solo founder with a network of their own is in exactly the same position.
The trade is odds against ownership.
You are pricing two different things against each other, and the argument goes wrong when a founder compares them on one axis. A foundry improves the odds that the company survives its first two years and reduces the share you hold if it does. Going solo does the reverse, more slowly.
Neither of those is the better answer in general. What decides it is which outcome you would regret. A founder who would be more troubled by owning a small piece of a good company than by owning a large piece of one that never started should think hard before signing at formation. A founder who would rather have built something real on someone else's terms than owned all of a company that ran out of runway alone should stop apologizing for taking the offer.
When a foundry is the better choice.
You take the foundry when you are a first-time technical founder with a deep problem and no commercial partner, when your category needs a network of security leaders from the first week to get any conversation at all, and when you have been honest with yourself that the odds matter more to you than the ownership. That is a reasonable trade, and good companies have been built on it.
Then negotiate it as what it is. Ownership and decision rights are the two terms that matter, and both are easier to set at formation than to revisit later.
When going solo is the better choice.
You go solo when you saw the problem in your own work, when you already have the buyer's words for it, and when you can get to a first cold conversation without a fund's phone. A seed from a fund that knows your buyer then keeps the problem yours, keeps the board a board, and leaves the acquirer list as wide as the market.
The cost is a year. You assemble the network yourself, you hire without a brand behind you, and you carry the commercial work while you build. Say that cost out loud before you choose, because the honest case for going solo is not that it is easier.
The question that decides it.
You ask who saw the problem first, and then you ask which regret you can live with. If the fund saw it, you are joining a company the fund started, and the terms to negotiate are ownership and decision rights. If you saw it, the problem is the asset, and keeping it is worth a slower year. We back founders who saw the problem first, and we say so on the first call — which is a statement about what we look for, not a verdict on the other route.
Install the skill.
You are reading the skill itself — this page and the download are the same files. Unzip it into ~/.claude/skills/ (or a project’s .claude/skills/) and Claude Code loads it when the question comes up; so does any agent that reads Agent Skills.
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -sLO https://techoperators.com/skills/foundry-vs-solo.zip && unzip -oq foundry-vs-solo.zip && rm foundry-vs-solo.zipfoundry-vs-solo/SKILL.md
No terminal? Download foundry-vs-solo.zip and drop into your assistant’s project files.
