Jordan Van Horn on Sales Playbooks, Hiring and Learning from Deals

Harry Stebbings welcomes Jordan Van Horn, then a revenue leader at Monte Carlo. Van Horn began in the wine industry before moving to San Francisco and technology sales. Selling to very different audiences taught him to understand what matters to each person and adapt how he communicates.

At Dropbox, he learned the value of clarity about whether a company is serving consumers, enterprises or both. At Segment, he says, he learned to evaluate talent carefully and maintain a high hiring bar. He sees an organization as the combination of its people and how they work together.

At the time his remit at Monte Carlo included sales development, sales, customer success and partnerships. He says the company had grown rapidly without settling formal titles, so “revenue leader” described his broad responsibilities. The organizational details and valuation he mentioned are historical, and he has a professional interest in the company.

He defines a sales playbook as steps that help a customer understand the product, assess a business outcome, build consensus, formalize a relationship and succeed after purchase. It should evolve from an open-ended early version into more specific guidance as a company hires and onboards many representatives.

The founder is accountable for the first version: what problem is being solved and for whom, which wins and losses reveal patterns, and why a customer should address the issue now. Van Horn says it need not be polished. A sales leader can later make the process more detailed, but the founder should remain close to those fundamentals.

For a horizontal product, “who” need not mean every potential user. It can mean the person who can make a purchasing decision and the companies ready to adopt at the current stage. He argues that a small team must focus its limited selling time even if the product could ultimately serve many audiences.

Recorded calls and opportunities to shadow the founder are useful material for early hires. He suggests asking prospects why they took a meeting, documenting recurring reasons and grouping them into a few practical customer patterns. The aim is to equip representatives to ask better questions rather than hand them an exhaustive list.

When deals slip, Van Horn asks whether the seller understands the decision-maker’s problem, the consequences of inaction and why timing matters. An expiring discount may force urgency but can damage the experience. A relationship can help, yet he believes a durable case should be connected to value such as saving money, reducing risk or moving faster.

In a company’s earliest days he prioritizes learning from well-matched customers over maximizing the price of every deal, while making clear that pricing can change. At a later stage, he says, price discipline matters because customers compare notes and want a fair exchange. His view is stage-specific, not a claim that revenue never matters.

If a customer champion leaves, the deal and later adoption can be at risk. He suggests that large enterprise deals involve a champion, a practitioner and an economic buyer, with relationships across them. For a small transaction, he says an elaborate multi-threaded process may cost more than it is worth; a faster cycle may be more appropriate.

The first question before hiring sales is what problem the founder wants to solve. Van Horn warns that hiring a salesperson will not by itself create product-market fit. A hire might help convert a reliable flow of qualified prospects, amplify learning in a competitive market, or handle transactions, but the founder should be explicit about the intended job.

Hiring does not instantly remove the founder’s customer responsibilities. In an enterprise motion he expects the founder to stay involved for months; for a simpler transactional motion a team may scale differently. He suggests looking for some paying, successful customers, repeatable leads and evidence that prospects move through early stages, while presenting the numbers he mentions as estimates.

Choosing a junior representative or a sales leader depends on sale complexity, confidence in the go-to-market motion and the founder’s desired involvement. He gives a low-value transactional example where one representative may be enough, whereas enough volume for several representatives may justify a leader. He cautions that a senior leader may no longer be the best individual seller.

He identifies two common mistakes: trying to solve missing product-market fit with a hire, and assuming a prestigious company or impressive revenue number proves an individual’s skill. A representative may have benefited from customers that grew rapidly or from others’ work. Founders should ask what the person actually contributed.

Van Horn groups hiring failures into mismatch with the organization, insufficient motivation for the work and a skills mismatch. He recommends defining the work and culture before interviewing, while explaining the difficult reality as well as the ambition. Candidates should be able to decide whether that environment is right for them.

To assess skills, he asks detailed questions about past performance: the deals behind a result, the person’s contribution, collaborators, obstacles and what they would change. His favorite follow-up is “what was hard about it?” because the answer can reveal whether the candidate solved a problem relevant to the new role.

He personally prefers detailed examination of relevant past work to a forward-looking case study, although his team still used a final presentation. In his historical process, a hiring manager first assessed motivation and track record, then a panel evaluated specific competencies with a structured score before the presentation.

The presentation should also let a candidate experience working with the company. Van Horn allows people to ask colleagues for information and values curiosity and conversational discovery over a recital of memorized material. His process is one approach to evaluation, not proof that presentations are suitable for every role.

His own hiring mistakes include skipping a structured step because of a strong recommendation, failing to check references and involving too many people before defining the role. He says these shortcuts can let bias or uncertainty drive the decision. A smaller decision group and clear requirements made the process more disciplined in his experience.

A written “user guide” helps colleagues understand how he works, what he values and when he is available. For example, he protects family dinner time and explains how to reach him for something urgent. He says stating expectations before a conflict can help build trust, especially in a remote or growing team.

Developing people starts in hiring by understanding their motivations and whether the role suits them. On the first day he explains strengths and possible derailers identified during interviews, then revisits them in regular conversations. He acknowledges that rapid growth has sometimes made that cadence difficult to maintain.

Stebbings relays feedback that Van Horn can care so much about representatives that objectivity becomes difficult. Van Horn agrees and says he has learned that caring is not the same as simply being nice. People need a clear picture of strong performance and honest information about their progress toward it.

Onboarding should reflect company stage. With a handful of employees he gave new hires information and close feedback without a formal program; with larger cohorts he moved toward structured competencies and checkpoints. He places early responsibility on frontline managers and says they need substantial time with new hires.

A manager must distinguish a genuine skills gap from something a new employee simply has not learned yet. Van Horn suggests examining what successful onboarding looked like and supporting the new person closely. His suggestion that fit can be visible within about thirty days is a personal heuristic, not a rule for every job.

He looks for early impact rather than demanding a large closed deal in the first month. Impact might be a useful customer conversation, an improvement to a process or progress through onboarding. He is wary of activity that looks impressive but has not yet shown whether it contributes to an outcome.

Long enterprise sales cycles make revenue a lagging indicator. Van Horn recommends defining observable steps before revenue, such as whether early calls lead to agreed next steps or useful introductions. A failed presentation or a few unproductive calls are signals to investigate, not automatic grounds for dismissal.

He says Monte Carlo had sometimes put new representatives in front of customers too quickly as the team grew. He favors supervised early exposure for learning, while suggesting that independently running a full deal might take roughly 30 to 60 days. That estimate was his view of the situation at the time, not a universal onboarding requirement.

The team reviewed important active deals weekly and retrospectively examined deals or proofs of concept that consumed meaningful resources without the expected result. He also reviewed some wins that had exposed process weaknesses. He wants representatives to lead those discussions in a safe environment, not be punished for acknowledging mistakes.

Van Horn tries to model that safety by discussing his own failures and describing learning from mistakes as a strength. In the quick-fire round, he says customer discovery and qualification remain fundamental: a seller should understand the problem and whether the customer is actually likely to buy before consuming substantial resources.

He believes purely top-down enterprise selling has weakened because leaders also need to see practitioner adoption and a workable behavior change. The executive buyer remains important, but in his view a polished presentation to that person alone is rarely enough. This is his 2022 experience-based assessment, not a claim that all sales processes are identical.

His advice to a new revenue leader is to choose a founder partnership carefully and discuss complementary strengths early. He describes himself as stronger in systems, people and execution than product storytelling, and values founder Barr Moses’s ability to frame the problem. This assessment reflects his working relationship at Monte Carlo.

He wants customer-oriented selling to win trust between buyers and sellers. At the time he described Monte Carlo’s challenge as maintaining simplicity and communication while revenue and the go-to-market team grew quickly. His reported historical scale is a company leader’s account, not independently verified performance data.

As examples of sales strategies he admires, he names Retool’s combination of product-led and sales-assisted growth and MongoDB’s move toward product-led sales. These are personal observations about other companies. Stebbings thanks him for the conversation and Van Horn returns the thanks.