Every fund with a platform function claims to help portfolio companies land enterprise customers. Almost none of them can tell you, with a straight face, whether their business development motion actually produces outcomes — or just goodwill.
That's not a knock on platform teams. It's a knock on the fact that "BD" at most funds, accelerators, and university venture programs isn't really one thing. It's two very different models wearing the same job title, and most teams don't realize which one they're running until it stops working.
The two models
Relationship-Based BD. This is the default. A partner mentions a founder to a contact they know — at a conference, over email, in a text. It works when the person doing the introducing has decades of relationships and enough brand gravity that the other side takes the call. It's how a16z, Bessemer, and First Round do it — and it's genuinely effective for them.
Demand-Based BD. Instead of routing through who the platform lead happens to know, the introduction is routed to a specific, live, budgeted need at the enterprise side — a real initiative an innovation or procurement team has already committed to solving. The platform lead's judgment still decides which portfolio company gets recommended and how; what changes is that the recommendation is aimed at a need that already exists, not a contact who might be receptive.
Neither model is "wrong." But they scale, fail, and report completely differently — and most platform teams are running Relationship-Based BD by default, without ever deciding to.
Side-by-side
| Relationship-Based BD | Demand-Based BD | |
|---|---|---|
| What triggers an intro | A partner remembers a contact | A live, budgeted enterprise need |
| What it requires | Years of personal relationships | Visibility into enterprise demand |
| Who it favors | Funds with deep networks and brand gravity | Any fund, accelerator, or program willing to track demand |
| Scales with | Headcount and tenure | Data and process |
| Typical failure mode | Intro goes nowhere — there was never a real need on the other side | Need is real but poorly matched to the wrong-stage startup |
| What you can report to LPs | "We made introductions" | "X companies entered pilots with Y enterprises" |
| Cost to build | Nearly free, but slow — takes years | Requires a system, but works on day one |
The honest reading of this table: most funds outside the top 10 platform brands are trying to compete on the middle column against firms that have a 20-year head start, when the right column is available to everyone right now.
Score your own BD motion
Pull your last 10 enterprise introductions — the ones platform actually facilitated, not deals partners closed themselves. Score one point for each "yes":
Did the introduction target a need the enterprise had already committed budget to, not just a contact who seemed relevant?
Could you name the specific enterprise initiative or program the startup was being introduced into?
Did you track what happened after the intro (pilot, meeting, no response) rather than losing visibility once it was made?
Was the recommendation based on something more current than a conference conversation or a stale contact list?
Could a partner other than the one who made the intro have made it too, using the same information?
Did the founder get context on the buyer's timing and readiness before the call, not just a name and email?
Would the introduction still have happened if the relevant partner was out sick that week?
Can you produce a number — not an anecdote — for how many of these converted to a paid pilot or contract?
Did the enterprise side already know they wanted a solution in this category before you reached out?
Is your BD process something a new platform hire could run in month one, without inheriting anyone's Rolodex?
You're running Demand-Based BD, whether you called it that or not. Keep tightening the feedback loop between what enterprises need and who you recommend.
You're a hybrid — probably a few strong relationships doing most of the work, with no system behind the rest. That's fragile; it depends on specific people staying at the fund.
You're running pure Relationship-Based BD. That's fine if you're a16z. For everyone else, it means your BD output is capped by how many contacts one or two people happen to have — and it's invisible to you when that runs dry.
Why this matters more for accelerators and universities than for funds
A venture fund that scores low still has capital as the primary offer. An accelerator or university program often doesn't — "we'll get you enterprise customers" is the pitch to founders, and a low score there isn't a platform gap, it's a value proposition problem. The same is true for university tech transfer and venture offices: spinouts need commercial validation to survive, and a program with a handful of alumni contacts is running Relationship-Based BD with almost none of the brand leverage that makes it work at a top fund.
For both, moving even partway down the Demand-Based column doesn't require hiring a BD team. It requires a live view of what enterprises are actually trying to solve for — something ecosystem partners are increasingly building into how they support their communities — so recommendations are aimed at real, budgeted need instead of whoever a partner happened to run into.
The takeaway
"Platform" has become table stakes at venture funds, and business development is the part of it hardest to fake. The firms getting real credit for it aren't the ones with the best relationships — they're the ones who can point to a specific need, a specific match, and a specific outcome. Score your last 10 intros. If you land in the 0–3 range, the fix isn't more networking. It's more visibility into demand that already exists.
Give your platform team a demand-based BD motion.
SwitchPitch's Ecosystem Accounts give VC platform teams, accelerators, and university programs a live feed of vetted, budgeted enterprise needs — so recommendations are based on real demand, not memory.
See how it works →