Oliver Jay on Sales Playbooks, Hiring and Customer Learning

Oliver Jay began in equity research and venture capital before deciding to work in operating roles. Advice from investors he admired led him toward selling products; he later worked at Dropbox and Asana.

His Dropbox lesson was that employees increasingly choose the technology they use, changing business software adoption. At Asana he worked on combining product-led growth and traditional enterprise sales, which he says is difficult but possible.

Stebbings asks whether product-led companies need sales at all. Jay says it depends on the product and buyer: some categories can go far with self-service, but sales may help other companies engage larger customers and more strategic decision-makers.

Jay distinguishes an early sales playbook from a mature, repeatable process. At the beginning, the hard questions are which customer personas receive genuine value, how to reach them and how to explain that value; he says founders must participate because the answers also inform the product.

He does not consider a process truly scalable merely because a handful of representatives can repeat it. His personal benchmark is around 20 fully ramped account executives before claiming a mature playbook; the number is his experience-based heuristic, not a universal threshold.

Early teams should prioritize learning and agility. Jay suggests testing one question at a time, such as which persona responds or which outreach method works, and having the first customer-facing hires return with insights as well as revenue.

Stebbings worries that junior reps without a finished process will miss targets and leave. Jay agrees founders need a starting point from their early traction, but says that first version should improve continuously as representatives test messaging and share what they learn.

Asked whether to hire a head of sales or representatives first, Jay says the category matters. A clearly defined market with an established buyer may justify a sales leader earlier; a company creating a new category may first need curious customer-facing people to discover the buyer and motion.

He agrees there can be benefits to hiring in batches, including shared onboarding and comparison. But he resists manufacturing competition between early hires: he wants intrinsically motivated people who collaborate and share what they learn as they build the process.

The first customer-facing hire need not have a sales title. Depending on the product, customer success, sales engineering or developer relations skills may be more useful for collecting feedback and serving customers.

His 2022 advice to hire that person early assumes the startup has sufficient capital, an assumption he explicitly states. The near-term objective is learning about customers, not necessarily maximizing immediate revenue.

Jay recommends a structured hiring process: write down the competencies and behaviors required, assign questions to assess them and define what strong or weaker answers look like. He sees this as one way to reduce unconscious bias and improve early-team diversity.

One quality he seeks is genuine appreciation for the product. He asks candidates to describe their current product and listens to how they explain its value, looking for engagement with customer outcomes rather than a generic pitch alone.

He also wants people who make colleagues better. For leaders, he asks about someone whose career they helped and someone whose potential they failed to develop; he listens for ownership and care rather than reflexively blaming the other person.

Jay maps about four or five competencies to interviewers, with each conversation testing a distinct area. He favors a diverse panel and one or two cross-functional partners, such as product, marketing or recruiting, to broaden the assessment.

A prepared demo or pitch can reveal potential that an on-the-spot interview misses. Jay gives candidates time to prepare because less-polished early-career talent may perform much better with context and practice.

For very early sales compensation, he cautions against copying a mature company's commission plan. Without historical data, targets and rates can be wrong, and formal arrangements can be difficult to unwind; his remarks are practical experience, not legal advice.

Variable pay can take different forms, such as bonuses, team incentives, new customer logos or deals of a particular size. The metric should reflect what the company is trying to learn or achieve rather than defaulting to a standard annual recurring revenue commission.

He argues early salespeople should also receive equity. In his experience the first group can become the cultural and operational foundation of the organization, transferring product knowledge and helping establish future offices; a purely transactional relationship risks losing that knowledge.

For onboarding, Jay sequences product knowledge first, market knowledge second and sales practice last. Early customer-facing hires may need much deeper technical understanding than later representatives because there may be no specialized sales engineering team.

He recommends starting with support tickets, then finding engineers who can explain why a problem exists and how the product works. This exposes likely customer objections and helps a new hire learn how to find answers when documentation is incomplete.

Market education might begin with the founder's fundraising deck if no sales deck exists. Jay wants new hires to understand the category, competition, mission and market drivers before being absorbed in day-to-day sales messaging.

For sales practice, new hires can shadow the founder and speak with friendly early customers about the value they receive. Jay likes an end-of-onboarding demo with colleagues role-playing buyers, so the representative must synthesize product, market and communication skills.

He suggests roughly two months to reach a strong demo in an early-stage setting, while noting that a product-led company with inbound users may let new hires speak with customers within a few weeks. Those conversations need not immediately be sales calls; the timing is his example, not a fixed standard.

Jay warns that a plateau in inbound growth does not make outbound a simple substitute. Outbound can involve a different, more senior buyer, a different value proposition, lower conversion and larger deals, and may require different sales talent.

Buying a list and sending cold messages will not repair a process built for another buyer. He says marketing, product and sales need to align around the new audience and offer, while the company should also examine ways to improve its existing inbound funnel.

He sees the head of sales and CEO as partners. The sales leader must generate revenue but also bring structured customer feedback to the CEO, avoid overreacting to the latest lost deal and help the founder make better decisions.

In an early-stage company he would expect frequent, at least weekly, conversations with the CEO. Their purpose includes sharing what is working and what is not, not merely reporting a sales number.

Jay describes weekly deal reviews and a 'five whys' post-mortem. Instead of accepting the first explanation for a lost or delayed deal, the team keeps asking why until it can identify underlying problems that may be addressable.

For example, 'bad timing' may prompt a discussion of why the issue was not urgent for the customer. Losing an internal champion may lead to questions about why the team lacked other relationships and whether account prioritization left too little time.

In the quick-fire round, he says articulating business impact remains fundamental to selling. He is skeptical of mass email and superficial lead-scoring approaches in the 2022 environment; that is his view, not proof every email tactic has stopped working.

He sees a major founder mistake in failing to connect customer-facing teams with product. Companies should plan how the voice of the customer is captured and returned to product, rather than focusing only on the sales process.

His advice to a new sales leader in 2022 is to manage upward: maintain clear dialogue with the founder, CEO and board as well as building a team. He frames this in the context of demanding growth expectations and high valuations at that time.

Jay would like salespeople to be treated as partners in solving customer problems, on an equal footing with product teams. He argues that their direct contact with customers can be a source of valuable feedback; Stebbings thanks him and closes the interview.