Hot take: The advice you're getting about SPVs is wrong. It feels productive, but it's a trap that's actively destroying your portfolio's potential. Let's talk about the uncomfortable truth.
I get it. You read the blogs, you listen to the podcasts. Everyone from your favorite VC influencer to that partner at a16z is talking about Special Purpose Vehicles. They seem like the ultimate cheat code. A way to bundle small checks, clean up your cap table, and show you’re a sophisticated operator. It sounds like a power move. It’s not.
I’ve seen this movie play out more than 200 times as an angel investor, and I saw it from the other side of the table during my two exits. The pattern is painfully clear: a premature obsession with financial engineering is a direct predictor of failure. Founders who spend their nights designing the perfect SPV structure are the same ones who can’t tell me their customer acquisition cost.
The Allure of Playing Banker
Why is this trap so effective? Because it feels like you’re making progress. Building a product is hard and uncertain. Talking to customers is draining. But structuring a legal entity? That feels concrete. You can hire lawyers, draw diagrams, and create a data room that looks just like the ones the big funds have. It’s a powerful form of procrastination that masquerades as strategic finance.
I once advised a founder—let’s call him Mike—who had a brilliant idea for a developer tool. In our first meeting, he didn’t open a product demo. He opened a flowchart of his proposed SPV structure. He had spent weeks, and probably close to $20,000 in legal fees, figuring out how to bring in 50 small-check angels. He was so proud.
My first question was, “How many developers are using your beta?”
He froze. The answer was seven. And three of them were his old college roommates.
Mike’s company died six months later. Not because the SPV was flawed, but because he was so focused on the funding vehicle that he forgot to build the car. He was playing banker when he should have been a builder.
Three Ways SPVs Destroy Early-Stage Startups
This isn’t a one-off story. It’s a disease. Here’s how it kills your company and your returns.
1. It’s a Massive Distraction from What Matters
The only thing that matters in the first 12-24 months of a startup’s life is finding product-market fit. That’s it. Nothing else. Every single ounce of your energy—every brain cycle, every minute—should be dedicated to building something people want, talking to those people, and iterating.
Structuring an SPV is a deep, complex task. It involves lawyers, administrative costs, and a ton of coordination. It pulls you out of the trenches and puts you into a conference room. You’re not thinking about user feedback; you’re thinking about management fees and carry. This is a fatal misallocation of your most precious resource: your attention.
2. It Sends a Terrible Signal to Real VCs
Imagine you’re a serious institutional VC. You’re looking for founders with an irrational conviction to build something massive over a 10-year horizon. You meet a founder who, before they’ve even hit $10k in monthly recurring revenue, is already optimizing for secondary liquidity and managing a complex web of small investors.
What does that signal? It signals a short-term mindset. It signals that you’re more interested in the idea of being a founder than the grueling work of it. It can suggest that you’re looking for a quick flip, not a world-changing outcome. It makes you look like a tourist, not a native. A messy, SPV-laden cap table at the seed stage is a red flag. It tells me I’m going to have a headache dealing with 50 different opinions every time a tough decision comes up.
When I was raising for RemoteTeam, we had a clean cap table with a handful of committed angels who understood the vision. When Gusto came knocking, the diligence process was clean and fast. There weren’t 30 different parties to consult. The focus was on the deal, not on stakeholder management.
3. It Creates Legal and Administrative Drag
SPVs are not “set it and forget it” instruments. They require ongoing administration. There are state filings, K-1s for investors, and potential compliance issues. This costs money and, more importantly, time. It’s a tax on your future operations.
I’ve seen startups get bogged down in this. A simple pivot becomes a complex legal maneuver. A bridge round turns into a nightmare of collecting signatures. You’ve traded the agility of a startup for the bureaucracy of a mini-conglomerate, and you haven’t even found your market yet.
What to Do Instead: The 1% Founder’s Playbook
So if you shouldn’t be obsessing over SPVs, what should you be doing?
Focus Maniacally on Product: Build, ship, learn, repeat. Be obsessed with your users and their problems. Your product is the only leverage you truly have.
Find a Few Great Angels: Instead of 50 investors giving you $5,000 each, find 5-10 who can write $25k-$50k checks. You want partners, not just passengers. You want people you can call at 10 PM when everything is on fire. You can’t do that with an SPV of strangers.
Keep Your Cap Table Simple: A simple cap table is a sign of a focused founder. It makes you more attractive to future investors and potential acquirers. Don’t create problems for your future self just to feel clever today.
Understand Dilution is a Feature, Not a Bug: Yes, taking on fewer, larger checks means more dilution from those specific investors. But it also dramatically increases your odds of getting to the next stage, where the valuation will be multiples higher. You’re better off owning 15% of a $100 million company than 50% of a dead one.
There is a time and a place for SPVs. They can be a useful tool for later-stage companies to consolidate smaller investors in a growth round or for a specific strategic purpose. But at the seed stage, it’s like a toddler trying to enter the Formula 1. You need to learn to walk first.
Stop trying to be a financial wizard. Be a founder. The best way to generate incredible returns isn’t to engineer the perfect cap table—it’s to build a company so successful that the cap table barely matters. Go build.
Frequently Asked Questions
What experience informs this perspective?
This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 200+ startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.
What's the most common pushback you get on this?
People often push back by citing exceptions or edge cases. And they're usually right that exceptions exist. But building a strategy around exceptions rather than patterns is a losing game for most founders.
How can I apply this thinking to my own situation?
Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.
How has this view evolved over time?
My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.