Before You Hire That CRO, Read This

If you’re a technical founder and your board is telling you it’s time to hire a professional CRO, read this before you make that call.

I’m not going to argue that you should never hire one. But I am going to tell you what happened when a company I was involved with hired two of them, what I learned when I took the job myself despite having no business running a sales org, and why the conventional playbook fails so often at technical companies.

Chapter 1: The Founder CRO

When Lukas Biewald founded Weights & Biases, he wasn’t a sales guy, but he wasn’t new to building companies. He’d previously founded and led Figure Eight (formerly CrowdFlower), and before that had been at Yahoo and Powerset. What set Lukas apart was something harder to put on a resume: he seemed put on earth to improve the life of AI engineers. That deep curiosity about their problems and how to solve them shaped everything about how he built W&B’s early team.

The first sales hires reflected that. It was a small group, and several of them had followed Lukas from Figure Eight into the next adventure. They spent most of their time in consultative relationships with customers. They weren’t running traditional sales cycles. They were doing customer development, sitting with AI researchers, understanding workflows, figuring out where experiment tracking fit into real AI pipelines. They’d built their careers at companies like Domino, Figure Eight, and Scale, where you couldn’t survive without technical depth. They could talk to an AI engineer about hyperparameter sweeps and mean it.

Revenue was growing well, with the kind of customer relationships that compound. Users trusted the team, expanded their usage, and referred colleagues. The foundation was solid.

Then W&B raised a round, and the board did what boards do: suggested it was time to bring in a professional sales leader to “scale the GTM motion.” The founder’s scrappy team had gotten the company this far, the thinking went, but now it was time to professionalize.

SaaStr puts the failure rate for first VP Sales hires at SaaS startups at 70%. Average tenure: about 7 months. For technical and AI-focused products, I think it’s higher. But every board thinks their hire will be in the other 30%.

Chapter 2: The Copy-Paste CRO

The first professional CRO came from a well-known DevOps company, where he’d been a regional VP of Sales. He’d never run an entire company’s go-to-market, and had no prior experience selling to AI practitioners, but the DevOps background looked close enough on paper.

I should own my part here: I was on the W&B board at the time, having led their Series A for Coatue in 2019. I agreed we should make the hire. His resume was impressive. At least I owned fixing the problem I helped create in a way most investors never consider, but more on that below.

His approach was to apply his previous company’s playbook at W&B. Not adapt it, apply it: the same org structure, the same hiring profile, the same sales methodology. To wit, he put in place geography-based rep territories, the same way you’d carve up a DevOps platform sale. We ended up with a rep trying to sell AI experiment tracking tooling in Alabama and Georgia, wondering why she couldn’t make quota. He scaled the team fast (from about 5 to ~20 in seven months) but optimized for speed over fit. The hires skewed toward traditional enterprise sellers rather than the technically fluent reps the market required.

Here’s what made this hard to catch: the top-line GTM metrics looked decent. ARR was growing. If you only looked at the dashboard, you’d think the hire was working. But when we dug in, virtually all of the growth was being driven by those early salespeople Lukas had brought on. The new hires were producing almost nothing. The professional sales machine was a mirage. The founder’s technical sellers were carrying the entire number.

Nine months later, he was gone.

Chapter 3: The Unlikely CRO

When I joined W&B as COO in June 2021, I made Lukas a promise: I’d work on whatever kept him up at night. A few months later, he told me that thing was now sales. I thought he was joking.

Nothing in my background says “you should run a sales org.” I’m a product guy. I wrote code at Google and Microsoft. I founded four venture-backed companies. I was a GP at Coatue Ventures leading AI investments. I’d spent years around data science and AI teams but had never carried a quota, never managed a pipeline, never run a QBR.

But a promise is a promise. Lukas saw some assets I missed: I’d been on the W&B board since the Series A. I knew the product & the customers. I’d spent years hanging out with AI engineers, caring about their problems. I understood why someone would choose W&B over MLflow or a homegrown solution, not because I’d read a battlecard but because I’d lived in the ecosystem.

When I took over as CRO, I didn’t try to invent a new sales methodology. I went back to what had been working before. I let go of most of the team the first CRO had brought on and scaled back down to Lukas’ original hires: the technical, consultative sellers who’d been carrying the number all along. Then I used their profile as the template to build the team back up: people who’d built their careers at AI and data companies, who could hold a real conversation with a practitioner, who were curious about the problems rather than just the quota.

One of the first things we changed was territory design. Instead of geography, we segmented by vertical, focusing on the industries we knew trained and fine-tuned models: tech, healthcare, automotive, financial services, government. We gathered data on the number of AI engineers at thousands of companies and did our best to give each rep a territory with a similarly-sized pool of practitioners to target (contract sizes were seat-based then, so this mattered).

We executed quarter on quarter. I ran data science concurrently with sales, which sounds odd but was a structural advantage: I could instrument our pipeline like I’d instrument a product, build dashboards that showed where deals were stalling, and test interventions with the same rigor I’d apply to an experiment. I got my hands dirty across the funnel: helped write SDR sequences, sat in on first pitches, negotiated down-to-the-wire renewals. Not because I needed to close every deal, but because participating across the funnel is the only way to understand where it breaks.

I also couldn’t have done any of this alone. One of the most important things I did was assemble a sales leadership team that filled in my skill gaps. What started as a tiger team to right the ship after the first CRO became a permanent group I relied on for advice, pushback on strategy, and the kind of late-night work sessions where we’d be categorizing prospects for territories at 11pm. They were willing to do whatever was necessary for the company to succeed. They know who they are, and I couldn’t have done it without them.

Chapter 4: The Delegator CRO

Despite our results, after about three quarters, the board pressure returned. The feeling was that the company needed a “career CRO” to take it to the next level, someone who’d scaled enterprise sales orgs before and could build the machine for the long term. So we decided to try again.

This time we ran a more thorough search and hired someone with a stronger profile: years of enterprise sales leadership at data and analytics companies, prior CRO experience, a career spanning institutional finance and global software sales. He was professional, organized, and had a track record.

He wanted to run the team the way a CRO at a larger-scale company would: build the org, build the machine, manage from above. He wasn't interested in getting personally involved in specific deals or spending time with specific customers. His career had been selling to business buyers, from institutional equities to enterprise analytics. He'd never sold to AI practitioners, and at a company where technical credibility is table stakes, that mismatch showed up in every customer call and team meeting.

The GTM metrics got worse: growth and net new ARR decelerated, churn went up, and a few of our best salespeople left because they wanted a leader with deeper technical fluency. On the retention side, the lack of executive hands-on involvement with top customers led to surprise churns and contractions.

After about a year, we parted ways. Lukas knew who had fixed the broken engine once before: “if at first you succeed, try, try again”. I took the CRO role back for the second time, mid-2023.

This rebuild was harder than the first one. Morale was low. The numbers had been tough for several quarters and the team felt like they’d underperformed, even though much of that was a leadership problem, not a talent problem. We needed to jazz the org back to life, not just restructure it. Some of the people who’d left were the best sellers we’d had. I made it my mission to bring them back, and succeeded in many cases. We rebuilt both the sales and CS motions to be what they’d been before: more customer-oriented, more technical, more interested in outcomes than activity metrics.

One thing we did to fix the churn problem was assign executive champions across our leadership team to our biggest and most discriminating customers. This wasn’t a CRM field or a quarterly check-in. It meant our leaders were personally accountable for those relationships. It helped us uncover issues customers had been complaining about for a year, allowed us to focus our engineering efforts on addressing them quickly, and got the relationships back on track. The best part: those feature requests ended up being useful for our whole customer base. Just like in the early days of W&B, the early adopters were tastemakers in how to build in AI. Listening to them made the product better for everyone.

We got back to hitting targets within one quarter. The days and nights of that quarter definitely blur together, but we got there. When I stepped away in mid-2024, the person who replaced me was also an operator and former CEO who’d built AI companies himself, not a central-casting sales leader. The pattern held.

W&B was eventually acquired by CoreWeave. The GTM organization we built was a big part of why.

What I’d Tell You

If you’re the technical founder sitting across from your board right now, here’s what I’d tell you.

Trust your instincts on hiring. Lukas built a better sales team on instinct than two professional CROs built on purpose. He hired people who were curious, technical, and consultative. He didn’t know all the sales jargon for what he was doing, but he knew what kind of person could have a real conversation with an AI researcher. He also trusted that I’d be good at running sales, even when I thought that was nuts. If you find yourself thinking “this salesperson seems impressive but I wouldn’t want them talking to my users unsupervised,” trust that feeling. And if you see someone unconventional who deeply understands your customers, trust that too.

Get your hands dirty before you hire a leader. You need to participate in enough deals, from first outbound email to signed contract, that you understand the real objections (not the polite ones), the buying process (not the org chart version), and the competitive dynamics (not the Gartner quadrant version). Write outbound copy, sit in on pitches, negotiate pricing. That experience is irreplaceable, and it’s the only way to build a sales methodology that reflects your market.

Document the pattern, not the pitch. Most sales playbooks are decks full of talk tracks, and most of them are useless. What you need to write down is the buying pattern: who initiates, who blocks, what triggers urgency, what information they need at each stage. When you hand this to a hire, you’re giving them a map, not a script. Maps scale. Scripts don’t.

Your first sales hire should be a full-cycle AE, not a VP. Hire someone hungry who doesn’t mind doing their own prospecting, demos, and negotiations. Bringing on a VP Sales when you have zero reps is like hiring a general with no army. The VP comes when you have 4-5 AEs producing consistently and the job shifts from selling to managing.

Hire technical sellers, not “enterprise reps.” The best hires at W&B were people who had sales experience but had built their careers selling technical products to technical buyers at companies like Domino, Figure Eight, and Scale. They understood the ecosystem and could hold real conversations with practitioners while knowing how to run a deal process and close. The sweet spot is salespeople with technical depth. They’re not cheap (they know what that combination of skills is worth), but the ROI is better than paying less for enterprise reps who can’t earn trust with your buyers. Be prepared to defend these hires and their compensation to other leaders in the company, including your CFO. Non-traditional sellers often come with non-traditional comp expectations, and you’ll need to make the case that the premium is worth it. But winning often requires innovation in the playbook, and you have to follow that conviction even when others aren’t doing it the same way. Every company succeeds for its own reasons.

Know when to hire above yourself. There’s a revenue threshold (roughly $15-25M ARR in my experience) where the job changes from “how do we win this deal” to “how do we build a machine that works without me in the room.” That’s when a professional sales leader starts to make sense. But not before. And when you do hire, make sure they can go deep with your buyers. The lesson from W&B isn’t “never hire a CRO.” It’s “never hire a CRO who can’t hold their own in a 30-minute technical conversation with your most sophisticated customer.”

Sell like an engineer, not like a salesperson. Technical buyers have finely-tuned BS detectors. They want to see something real, have an honest conversation about where the product is strong and where it’s not, and make their own decision. Some of the best sales conversations I had at W&B were the ones where I said “honestly, we’re not great at that yet, but here’s our roadmap and here’s why we’ll get there.” Counterintuitive, but that kind of candor builds more trust than any pitch deck. When you fly out to a customer to personally apologize for issues and walk through the roadmap for fixing them, that carries more weight than any QBR slide ever will.

Why 2026 Is Different

AI is making the founder-as-CRO path more viable, not less. The parts of sales that technical founders hate (and are bad at) are the parts AI handles well: CRM hygiene, follow-up sequences, call prep, meeting summaries, competitive intel, lead scoring. A technical founder in 2026 with the right AI tooling can run an effective sales operation without the overhead that used to require a full GTM team. You focus on what only you can do: having a real technical conversation about a real problem with a real buyer. AI handles the scaffolding.

This is part of why we invest in what we call “AI coworkers” at B Capital: persistent, learning AI systems that integrate into workflows and get better over time. Sales is one of the clearest early use cases. If you’re building in this space, I’d love to talk.

When This Doesn’t Work

If you’re selling to non-technical buyers (CFOs, CHROs, procurement), the founder advantage is smaller because domain credibility matters less than relationship credibility. If your product is horizontal, the buyer set is too diverse for one person to deeply understand. And if you hate talking to customers, forcing yourself through it will produce worse results than hiring someone energized by it.

This is also about the first sales leader. At scale, you need professional sales management. The question isn’t whether to eventually hire a CRO: it’s when and who.

The Signal I Look For

As an investor, the signal I care about most in early-stage AI companies isn’t the pitch deck or the TAM slide. It’s whether the founder can get on a call with a skeptical VP of Engineering and, within 20 minutes, have that person saying “when can we start?”

That ability isn’t taught in any sales methodology. It comes from building the thing yourself and knowing why it matters. The founders who have it build companies that grow efficiently. The ones who outsource it too early spend their Series A cycling through sales leaders while their competitors close deals.

The conventional wisdom says technical founders need a “professional” to run sales. The data says those professionals fail 70% of the time. I watched it happen twice at the same company before doing it myself, and the company did just fine.

Time the conventional wisdom got an update.