Conversation
Highlights

Newsela: The CRO Hiring Mistake That Keeps Costing Early-Stage Founders Two Years

Bryan Caplin has sat in the wrong seat before.

A founder brought him in as CRO at a Series A company doing under $10 million in revenue. He was willing. He was capable. It still didn’t work. “I’ve worked for early stage series A companies with, you know, under 10 million in revenue who thought they needed a CRO and I was quite willing to be that person. And it was, it didn’t work.”

The problem wasn’t Bryan. The problem was the job description. At that stage, what the company actually needed was someone who would pound the pavement, build pipeline personally, and grow a team around them. That’s not a CRO role. That’s a head of sales role. The difference sounds semantic. The cost of confusing them is not.

Now CRO at Newsela — overseeing a 160-person org across SDRs, sales, customer success, rev ops, and enablement, serving 7,000 schools and districts — Bryan has become one of the clearer voices on how founders get this decision wrong, and what to do instead.

In a recent episode of Unicorn Builders, Bryan laid out the framework he wishes more founders understood before their first sales leadership hire.

Why the CRO Title Is Misleading Early-Stage

The CRO role is still relatively new as a C-level function. Bryan started his sales career in 2001 at CEB — now part of Gartner — when SVP of Sales was the ceiling. The CRO title didn’t register as a meaningful North Star until the mid-2010s, when he started seeing former colleagues and bosses move into the role and understanding what it actually encompassed.

Even today, the scope varies widely by company. At Newsela, Bryan owns everything that touches acquiring, growing, or retaining a customer — sales, customer success, rev ops, solution architects, enablement, and customer support. Marketing sits separately. That breadth is the point: a true CRO role is an orchestration job, not a selling job.

Early-stage founders conflate the two. They raise a Series A, hear from advisors that they need a CRO, and hire someone genuinely qualified for a large org — but who has no interest in grinding out the first 50 customers themselves. “What they’re really looking for is a enterprising scrappy director or VP of sales who’s going to get out there, pound the pavement, make the calls, get in the trenches, you know, generate pipeline themselves, build a team around them.”

His advice is direct: wait. And if a founder is past the point of waiting, hire explicitly for the stage they’re in — not the stage they’re projecting.

The Two-Year Clock Every Founder Should Know

There’s a structural reality behind this advice that most founders don’t factor in. “I think the average tenure for a CRO now at a venture backed software company is two years, might even be less.”

That number has implications. If average tenure is two years, hiring a CRO built for a $50 million ARR business when you’re at $8 million doesn’t extend your runway — it creates a mismatch that burns time and trust on both sides. The better mental model: hire the person who is right for the next two years of your specific growth stage, accept that the profile will likely need to change after that, and build accordingly.

Bryan is clear that this isn’t pessimism — it’s precision. Some CROs grow with a company from Series A onward. They exist. Most don’t. Building your hiring strategy around the exception is how founders end up replacing senior sales leaders and losing the momentum that came with them.

Building an AI GTM Function Without Losing Control of It

The second major thread in Bryan’s playbook is how Newsela has approached AI adoption inside its GTM org — methodically, and with deliberate sequencing.

The starting point was a go-to-market engineer role, created after Bryan, his CEO, and his head of rev ops each found themselves independently experimenting with LLMs and realized nobody was moving the ball forward. The decision to hire internally was not a compromise — it was a requirement. “We really wanted that person to be an internal hire because we knew we needed someone that kind of understood our data in a really intimate way, someone that understood our market, understood kind of the limits of our current team.”

They promoted from within their own data team: someone who had already been building tools independently and had existing cross-functional relationships. That last point matters more than most teams anticipate. Every third-party AI tool Newsela has evaluated has required an intensive legal and data privacy review. A GTM engineer who can navigate that process across engineering, legal, and data privacy teams is a different profile than a strong technical builder who works in isolation. “This isn’t just some like smart, talented engineer that you’re plugging in. Like they have to have pretty good cross functional collaboration skills as well.”

Why Newsela Sequences AI Wins Deliberately

The first project Bryan’s GTM engineer tackled wasn’t the most ambitious one on the list. It was the one most likely to convert skeptics.

Newsela’s SDRs had been rotating through inbound chat duty, manually triaging a queue that Bryan describes as roughly 90% noise — students exploring the site, spam, irrelevant inquiries. An AI qualification agent eliminated that triage entirely, routing only real teacher and district inquiries to the right rep. The impact was immediate and visible to the exact people who would otherwise be most resistant to an AI program expanding into their workflow.

That sequencing was intentional. Bryan wanted early wins to build credibility and confidence across an org where not everyone knew the GTM engineer and some were understandably uncertain about what an AI program meant for their roles. Early wins create the organizational trust needed to pursue more complex applications — like the call intelligence tools Newsela recently deployed to surface trends across “hundreds and hundreds of calls in any given day,” or the AI-assisted forecasting Bryan is building toward.

On vendor evaluation, Bryan’s rule is firm: pilot everything for one to two months before purchasing. Several AI outbound tools that looked promising in demos failed on email tone and actual meeting generation during POCs. The lesson: “If you want to really get this thing to work, it’s going to require a lot of work upfront.” That upfront training investment is the cost most teams don’t price in before signing.

What Hasn’t Changed

Bryan has led revenue teams through 9/11, the 2008 financial crisis, and Covid. His read on the current AI moment is that CROs who get distracted by the tooling at the expense of the fundamentals are making a mistake. Connecting with reps, listening to calls, joining deals, holding people to the leading metrics — none of that has been automated away. “Don’t forget about what got you here, like the fundamentals of what makes you a great sales leader. That hasn’t changed.”

The principle underneath both threads is the same: match the decision to the stage. Hire the sales leader the current business needs. Build AI capability in the sequence that earns trust before it demands it. And don’t let hype — around a title or around a technology — pull you away from the work that actually drives revenue.