Why “We Just Need a Business Development Person” Is Rarely the Answer — and What Actually Moves the Needle
I’ve seen this multiple times from multiple founders. Every founder has felt it. You’re pre-product-market fit (or stuck in that frustrating “almost there” zone), adoption is sluggish, yet you have some amount of inbound requests, revenue is lumpy, and you or your co-founder starts asking the inevitable question: “Should we hire a BD person?”
The logic seems sound on the surface. Partnerships will open doors. A seasoned closer will land the lighthouse customers. Business development will “figure out the GTM” while the product team keeps building. It’s a comforting narrative — one that lets the founding team stay in their comfort zone (the code, the roadmap, the vision) while outsourcing the messy, humbling work of market validation.
It’s also usually wrong.
The Real Problem Isn’t Lack of BD Talent — It’s a Broken (or Missing) Feedback Loop
Pre-PMF, your biggest constraint isn’t distribution. It’s speed of learning. The main thing most companies get wrong at this stage is iteration speed. Everything else is secondary.
Traditional BD hires are optimized for a different game. They excel when the playbook is already established:
- The value proposition is already validated
- The sales process is repeatable
- Objections are known and can be handled with case studies
- The product team can ship fixes on a predictable cadence
None of those conditions exist pre-PMF. So you end up with an expensive, frustrated hire who either:
- Pushes a half-baked product and damages early reputation, or
- Sits in discovery meetings gathering “feedback” that never makes it back to the product team in a usable form
The result? Slower iteration, not faster. More noise, less signal.
The Intersection That Actually Matters: BD + GTM + Product in a Tight Feedback Flywheel
The highest-leverage early-stage companies don’t treat BD, Go-to-Market, and product as separate functions. They treat market-facing work as the primary input to product iteration.
Every demo, pilot, partnership discussion, or pricing conversation becomes raw material for the next sprint. The person (or people) doing the market work must be:
- Close enough to the customer to hear the unfiltered truth
- Close enough to the product to translate that truth into actionable changes
- Fast enough to close the loop in days or weeks, not quarters
This is why either founder-led sales or hiring someone who deeply understands the intersection of BD/GTM/Product is non-negotiable pre-PMF. You must work with this person daily and treat their feedback as top priority. The founder (or this hybrid) is the only one who can feel the pain when a prospect says “this is cool but…” and immediately re-prioritize the roadmap. Delegating without this tight integration severs the feedback artery.
What “Good” Looks Like in Practice
1. Founder (or founding GTM hybrid) owns the loop initially
The CEO or a co-founder spends 50-70% of their time in customer conversations. Not polished sales calls — raw discovery. If they see a repeating feature request or valuable feedback from prospects, they bring it directly to the product team for discussion. The team reviews these insights weekly in a 30-minute “feedback sync.” No slides. No process theater. Just signal.
2. When you do hire early GTM help, hire for listener-learners, not closers
Look for the rare profile that can do both:
- Run a discovery call and a pilot
- Document objections in a shared Notion/Airtable that the product team actually reads and acts on (not just ignores)
- Run lightweight experiments (e.g., “We’ll build this integration for three customers if you commit to a 90-day pilot”)
- Ruthlessly prioritize which feedback gets built vs. which gets parked
In modern startups this person is often titled “Founding GTM,” “Head of Early Revenue,” or even “Product + Partnerships” — deliberately blurry. They are not a traditional BD rep.
3. Build the mechanical feedback system early
- One source of truth for all market input (customer calls, support tickets, pilot notes, win/loss analysis)
- Weekly or bi-weekly “insight-to-roadmap” meeting where product commits to what they will (and won’t) ship based on the latest data
- A simple scorecard: % of roadmap items that originated from real customer conversations (aim for >60% pre-PMF)
When a Dedicated BD Hire Actually Makes Sense Pre-PMF
There are narrow exceptions:
- Your product is a protocol where partnerships or composability are literally part of the core offering (e.g., you need ecosystem integrations to make the product valuable)
- You are in a heavily regulated or enterprise-heavy vertical where the buying process is inherently relationship-driven from day one
- You already have clear product-market signals from founder-led efforts and now need to scale the discovery engine
Even then, the hire must be explicitly measured on feedback quality and iteration speed, not just signed contracts.
Stop Outsourcing Your Most Important Job
The narrative “we’re pre-PMF and we need a BD person” is seductive because it feels like progress. Hiring is visible. It signals seriousness. It gives the team someone to point to when things aren’t moving.
But real progress pre-PMF is invisible to outsiders: tighter customer conversations, faster roadmap pivots, higher % of features that actually get used by early users, rising “very disappointed” scores in your own small cohort.
That progress only happens when the people closest to the customer are also closest to the product decisions.
If the founders can’t lead go-to-market themselves, the pre-PMF BD hire must be more than just BD. Hire someone whose feedback is treated as top priority, who lives at the intersection of BD/GTM/Product, works daily with the team, and whose insights drive immediate roadmap changes.
Hire (or assign) the right hybrid role at the right time, build the mechanical feedback system, and you turn every market interaction into rocket fuel for iteration.
The companies that win aren’t the ones that outsourced their learning to a traditional BD. They’re the ones that turned learning into their unfair advantage — one conversation, one insight, one sprint at a time.
Your next BD hire might be exactly what you need.
Just make sure it’s to accelerate the feedback flywheel, not to replace it.
