Sam Taylor on Building Sales Around Customer Learning

Sam Taylor's route into sales was not direct: after studying environmental science and working in several industries, he joined Salesforce in 2010 and became one of Dropbox's first five salespeople in 2011. He later worked at Quip and Salesforce before joining Loom.

At Dropbox, Taylor learned that security alone was not enough to sell an enterprise consolidation plan. Selling only to IT on the basis of controlling existing usage could position a product as a liability; he wanted to articulate the positive value of employees' actual workflows.

Asked whether startups can run product-led growth and enterprise sales together, Taylor says it depends on the product and buyer. An individual or small team able to buy without a salesperson can take an efficient self-service path; as a product serves larger teams and more decision-makers, sales can complement it.

At Loom, he says, the challenge is connecting enthusiastic individual users with the people who approve larger purchases. Sellers must learn from users' stories and explain the broader business impact without assuming the buyer and the user have the same perspective.

Taylor calls early sellers 'workflow therapists': they ask why a person adopted the product, listen for common patterns and translate the findings into language relevant to a team or department. The goal is to understand the work before presenting a solution.

He favors open-ended questions such as what prompted someone to sign up and what prevents them from sharing the product with colleagues. Engaged users can explain cultural and workflow obstacles that inform which groups to involve and how to define a pilot's success.

Taylor dislikes the term 'playbook' when it implies a rigid script. He prefers adaptable frameworks: listening and changing the next step in response to the customer matter more than repeating a prescribed sequence.

Horizontal products such as Loom, Dropbox and Quip can serve many functions, making the starting point difficult to choose. Taylor wants teams to collect relevant customer stories and distinguish bottom-up adoption from top-down strategic initiatives.

Founders who raise money, recruit people and win early customers are already selling, Taylor argues. The question is how to distill their knowledge into a message someone else can deliver credibly, including lessons from both wins and losses.

He recommends letting early customer-facing hires observe founders pitching or listen to recordings. The seemingly obvious questions, objection handling and positioning a founder has practiced can be valuable material for a new seller.

Documentation need not become a lengthy script. Taylor suggests examining customers who understood the product quickly: their roles, company stage and onboarding experience can reveal patterns that help a team identify and support similar buyers.

In his experience, recordings can be especially useful because founders rarely make their conversations available to employees. He acknowledges that recording and sharing them may feel personal, but says small moments in a call can demonstrate skills that are otherwise hard to transfer.

For the first sales hire, Taylor rejects a universal choice between junior representatives and a senior leader. A narrow product with a clear buyer and a backlog of inbound interest may need people to handle more conversations; a less-defined business may need a different profile.

Early customer interactions may involve support or customer success as much as conventional sales. Taylor says early hires should be accountable for revenue and insights, with learning especially important before the company has settled its go-to-market approach.

He values inquisitive people who can structure what they learn and communicate it to the CEO, product and marketing teams. The right first customer-facing person is not necessarily a quota-carrying representative if customer insight is the most urgent need.

Stebbings asks about tension between product-led growth features and enterprise requests such as access controls or single sign-on. Taylor, whose career has been in product-led companies, says widespread engagement can build a strong enterprise case, but product, marketing and sales must agree on trade-offs.

In a resource-constrained company, the team must decide when repeated enterprise needs justify allocating roadmap capacity. Taylor says Loom also needs a clear ideal customer profile and should recognize when a regulated or very large prospect is beyond what it can realistically serve.

Inbound and outbound sales are different motions. Inbound leads may already know and use a product, while outbound outreach requires a more explicit argument about why the initiative matters and what impact it could have for the prospective organization.

Loom had begun experimenting with outbound before depending on it, Taylor says. From his experience, learning and building the motion can take 12 to 18 months; that is his estimate, not a guaranteed ramp time.

He compares early outbound work to starting at the gym: effort can precede visible results. Leaders should track incremental signs such as conversations, pipeline and repeatable messages, not only closed revenue, while the organization learns what resonates.

Before interviewing early sales hires, Taylor says a founder should identify the actual need: deal structure, a repeatable process, more capacity to handle demand, or another gap. The profile should complement the founder rather than duplicate existing strengths.

He personally looks for product enthusiasm, curiosity and the ability to structure learning. Open questions about interests, group projects and persuading others can reveal how someone thinks, even when the example is not directly from a sales job.

A hiring-manager interview is also a two-way conversation. The founder must assess the candidate while explaining why the person should take a risk on the company, its mission and the opportunity.

Taylor involves cross-functional colleagues in hiring so the new sales function does not become isolated from product, engineering and design. He chooses panelists with credibility across the company and asks whether a candidate can build similarly strong relationships.

He recalls advice from an early Dropbox manager: spend lunch with people outside sales. For Taylor, building relationships with the people making the product develops both context and trust, whether the lunch table is physical or virtual.

Taylor does not favor overly rigid case studies, but likes working sessions that show how a candidate thinks. A team might present a customer objection and ask the candidate to structure a discussion about product, marketing and go-to-market responses.

He prefers giving candidates time to prepare when the problem concerns an unfamiliar company. Expecting someone to solve the company's own problems immediately, without context, is unlikely to set the conversation up for success.

Loom uses short take-home prompts between an initial screen and panel interviews. Leadership candidates may discuss culture, management and sales process in a brief Loom recording; panelists can watch ahead of the live conversation and assess communication as well as ideas.

A common founder mistake is failing to define the role. Someone hired to develop the entire go-to-market strategy is not necessarily the same person as someone asked to build outbound, so questions and panel responsibilities should follow the actual job.

On compensation, Taylor says variable pay is useful at the right time, but may be premature for the first few hires when there is little evidence of achievable results. He favors a sustainable base and incentives reflecting early learning or inputs as well as revenue.

At Quip, he recalls early compensation with a substantial base and upside for performance; Loom also used input measures while building customer knowledge. He advises using experience and data to establish targets rather than adopting standard commission structures by habit.

Onboarding starts with understanding the company, its mission and its people before narrowing to the specific job. Taylor sees a seller as an ambassador for the product and brand, making cross-functional relationships and deep product knowledge essential.

Being able to operate Loom is not sufficient: sellers should understand when and why customers might use it in their work. That context helps them connect a product demonstration to a customer's workflow rather than just showing features.

Taylor believes an early demonstration and mock discovery conversation can validate readiness and establish a culture of coaching. At Loom, he says, new hires generally do this by the end of their second week and receive feedback from onboarding partners and a broader group.

Expectations for results depend on the sales segment. Taylor describes Loom's small-business deals as averaging roughly 45 days, with early pipeline expected before closed deals and about two deal cycles as a broad initial window; these are his company's 2022 examples, not universal benchmarks.

Enterprise cycles at Loom may run six to nine months, so he watches leading indicators: relationships across an account, pilot commitments and whether pipeline coverage fits the agreed ramp plan. Significant recurring revenue may arrive later in the cycle.

Strong new hires ask good questions across the company and seek to understand why the product and go-to-market approach work as they do. Taylor sees passive learning or a failure to build relationships as early warning signs, not a definitive test on their own.

Remote work can make those relationships harder for a new hire to initiate. Loom supplies a cross-functional listening-tour list and suggested questions about product roadmaps, customer input and how best to share what sellers learn.

He includes engineering, product marketing, operations and other sales functions in that tour, and highlights support as a rich source of information. Support teams hear both complaints and praise at higher volume than many other customer-facing groups.

As Loom's sales team expanded beyond a small group, deal reviews evolved as well. Taylor says segment leaders organize the cadence, the deal team leads the discussion, and the company was holding reviews roughly every two weeks at the time.

Reviews and post-mortems should examine losses as well as wins. The team asks what resonated, what did not and what might have been done differently; product colleagues can attend to hear the context behind enterprise deals.

When a customer delays a purchase because it is not a priority, Taylor wants sellers to ask why where the relationship allows for candor. Learning which other initiatives took precedence can help the team understand the customer's decision process and work with an internal champion.

Asked why enterprises might not buy Loom that quarter, Taylor points to scrutiny of spending and the company's early work establishing its category with large organizations. This is the Loom sales leader's account of its challenges, not an independently measured explanation.

In the quick-fire round, he says genuine curiosity about customer needs remains fundamental, while automated email has made it harder to cut through inbox fatigue. He argues that early sales teams should be integrated with the company rather than left as an orphaned function.

His advice to a new sales leader is to build cross-functional relationships and translate customer feedback in ways colleagues can use. He describes his own partnership with Loom's product leadership as important for aligning trade-offs and improving speed.

Taylor would like the profession to be recognized for learning and creating customer value rather than being perceived as interested only in commission. As an example of a sales strategy he admires, he cites Notion's community; he discloses that his wife works there.

Stebbings thanks Taylor and closes the conversation.