Enterprise Sales Without a BD Team — How We Won the First Three Customers
Eighteen months of building our first three enterprise customers with one engineer and one solutions architect, no BD hire. The five tactics that worked and three that didn't.
CollabOps's first three enterprise customers came in without a BD hire. One engineer, one solutions architect (me), and the founder. Eighteen months. This post is the five tactics that worked and the three that didn't.
The conventional wisdom is that enterprise sales requires BD. Partly true. But for the first 3–5 customers, BD is expensive with weak returns. Our data on why.
Five tactics that worked
1. Technical conference talks + meetings in the hallway
Enterprise CIOs and CISOs show up in person at certain technical conferences (typically 1–2 per quarter). Two of our first three meetings started in the hallway after a talk.
Talk topic was not a product demo — it was one technical problem we'd solved. If a listener has that technical problem at their own company, they come over and hand you a card. Turning the talk into product marketing kills it.
2. A single blog post opening the meeting door
When a post like Why On-Prem AI Agents Are Hard publishes, an email arrives within 1–2 weeks: "I read your post." They reach out first; we don't prospect.
This pattern is silent — hard to attribute which post produced which meeting. We added a first-meeting question: "How did you find us?" Two of three came from a specific post.
3. Technical PoC as the CTA
Where most SaaS uses demo request as the CTA, ours is a 2-week PoC. Higher entry barrier — but whoever enters is serious.
18 PoCs → 3 paid contracts — 17% conversion. Five times the typical demo-request SaaS conversion (~3%).
4. Direct meetings with the security team
In enterprise, the real decision maker is often not the CIO but the security team. We explicitly request a security meeting at PoC kickoff. We show our audit log format / authority model / data boundary in that room.
Without this meeting, the security review six months later blocks. With it, the PoC becomes the raw material for that review.
5. The weight of referrals
Two of three came via referral. The referral source was a previous PoC customer who didn't sign — they spoke well of us anyway. Companies that didn't run a PoC don't refer companies that did.
PoCs that don't sign are sales assets. The time spent isn't wasted.
Three tactics that didn't
1. Cold email campaigns
Sent 300. 4 replies, 1 meeting, 0 contracts. ROI deeply negative. Enterprise rejects cold entry almost categorically.
2. Outsourced BD agency
Three months. 17 MQLs (marketing-qualified leads). Of those, zero matched our ICP. An outside agency without technical depth sees every company as a prospect.
3. Conference booth (exhibition)
One booth — cost $12,000. 47 cards collected. 4 worth following up on. 1 meeting. 0 contracts. Talks work; booths don't.
Time allocation across 18 months
Activity | Hours/week | Outcome
──────────────────────────────────┼────────────┼─────────────────
Conference talk preparation | 4 | 8 first meetings
Blog writing | 8 | 6 first meetings
Existing / unsigned PoC support | 6 | 4 referrals
PoC delivery / technical meetings | 12 | 3 contracts
Security team meetings | 2 | smoothed contract review
──────────────────────────────────┼────────────┼─────────────────
Activities that didn't work:
Cold outreach | 8 (stopped after 3 mo) | 0
Booth | 1 / quarter | 0Total 32 hours/week on sales/marketing — i.e., 50–60% of two people's time. Doing this through the technical team directly worked better than dedicated BD would have.
When to hire a BD
Hiring becomes worthwhile when the five tactics saturate. Our thresholds:
- Conference talks reach 4+ per quarter — talk prep saturates one person
- 6+ concurrent PoCs — solutions-architect time hits its ceiling
- 5+ leads per week — first meetings themselves become a job
When all three saturate at once, BD's value exceeds its cost. Before that, hiring BD is inefficient.
For an early-stage enterprise startup, the BD hire is a decision founders should make after personally running the five tactics and the three non-tactics above. Numbers like 300 cold emails for 0 contracts, or a $12,000 booth for 0 contracts, only show up when you run the experiment yourself. Hire BD before you have that data, and there's no baseline for judging what's saturated.
Related posts
After Leaving Google, My Definition of Good Work Changed
I was a software engineer at Salesforce and Google before founding a company in July 2024. The standard for good code stayed the same. What changed is that the questions in front of the code became mine: which customer problem, and why now. Notes on how the definition of good work shifted from engineer to founder.
John Baek
Will Hiring More Senior Engineers Actually Make the Team Faster?
Expecting a team to speed up after hiring experienced engineers is natural. But there is something to check before opening the role: can you describe why work is slow as a concrete scene? Notes on separating work time from elapsed time, writing down the expected outcome, and how to judge a senior hire.
John Baek
Korea Had PC Bangs. What Kind of Environment Do Developers Need?
A question that started in a StarCraft lobby, where saying I was Korean was enough to make opponents leave. Where does skill actually come from? Move the practice-and-feedback loop of a PC bang into a developer day and you get an environment where you can see what happens after every change.
John Baek