Frank Fillmann on Enterprise Sales, Hiring and Customer-Centered Playbooks

The Salesforce sales leader explains how he coaches teams, maps opportunities and builds a case around the buyer’s priorities.

FFFrank Fillmannゲスト · Salesforce
チャンネル
20VC with Harry Stebbings
公開日
2023年3月22日
動画
1:01:46
読了時間
8 分
原文
英語
YouTube で開く
スクロールすると動画は右下に小さくなって再生を続けます。字幕は閲覧言語に合わせて切り替わります。
閲覧言語2 言語で読めます
この記事はまだ日本語に翻訳されていないため、英語の原文を表示しています。
要約

30 秒でわかる

In this March 2023 interview, Salesforce sales leader Frank Fillmann talks with Harry Stebbings about enterprise sales, recruitment and coaching. He describes a repeatable industry playbook, negotiation grounded in customer needs, and weekly reviews that combine deal discipline with team support. The examples are Fillmann’s personal experiences and professional judgments; results depend on the customer, team and market. His views reflect his role at Salesforce.

  1. 1A relevant playbookFillmann starts with customer problems and maps opportunities by size, timing and whether demand is known.
  2. 2Negotiate around valueHe asks about the buyer’s measures and financial priorities before presenting price.
  3. 3Coach long sales cyclesHe recommends realistic expectations and direct support before judging a new rep only by closed revenue.
  4. 4Work back from the customer deadlineA shared success plan can expose when contracting and implementation must begin.
  5. 5A weekly deal reviewHe combines urgent issues with structured reviews of customer goals, deal mechanics and next steps.
  6. 6Align the wider teamHe advocates involving customer success early and understanding each function’s measures.

ポイント

  1. A sales playbook should be repeatable and relevant to the customer’s work.
  2. Map near-term and longer-term opportunities, including needs the customer has not yet clearly defined.
  3. Pair potential with experienced support and set realistic expectations for long sales cycles.
  4. Build negotiation and urgency around the buyer’s priorities and timeline.
  5. Combine financial analysis, customer conversations and deal-level judgment in forecasting.
  6. Bring customer-success and other teams into the process early and align incentives.
全文

チャプターごとに整えた全文を読む

文字起こしのみ
01

Early sales and leadership

Fillmann recounts his early sales work and personal experiences.

Harry Stebbings interviews Frank Fillmann, then a Salesforce sales leader in Australia, about enterprise selling, hiring and coaching. The conversation was published in March 2023. Fillmann's examples and recommendations reflect his experience and Salesforce role rather than guaranteed results for every team.

Fillmann began selling knives in people's homes while in college and says he managed an office of 75 people at age 20. He later joined IBM, where his first role involved approaching accounts that did not want to talk to him. He describes those early experiences as training in recruiting, persistence and resilience.

He considers recruiting strong people and treating them well the foundation of sales leadership: if the team can meet its goals, the leader and company benefit too. His interest in recruiting began before his later enterprise-sales roles.

Fillmann recalls losing his father as a child and his brother when he was 30. He says those losses contributed to gratitude, persistence and a willingness to take risks in his career. This is his personal interpretation of grief, not a prescription for how others should respond.

02

Building a relevant sales playbook

He explains opportunity mapping, industry context and team development.

He defines a useful sales playbook as repeatable and relevant. Customers care about their own problems and metrics, not a seller's product alone; new representatives also need a way to become effective in an unfamiliar company, customer or industry.

He starts by mapping the money and opportunities, using three dimensions: near or far, big or small, and known or unknown. A team can pursue smaller near-term deals while also working on larger transformations that take longer. He says unknown demand may require helping a customer understand a problem and imagine a solution.

For an industry playbook, Fillmann recommends beginning with an account hypothesis and opportunity map. He uses an insurance claims adjuster as an example: instead of leading with a technology demo, explain how the work could help with speed, fraud or payment. The specific benefits must still be validated with the customer.

To develop specialized teams, he pairs an experienced leader who owns the process with high-potential colleagues who can learn alongside them. He wants experienced representatives to teach and share what has worked. This is a team-development approach, not evidence that a particular staffing ratio will work everywhere.

Asked whether to hire two sales reps at once so they can be compared, Fillmann prefers backing one person and investing in their development. He worries direct competition for one role can undermine safety. He believes intrinsically competitive people do not require fear of failure from management to perform.

He asks strong representatives for referrals to people they respect, reasoning that good performers often know other talented people. Stebbings notes that a mutual contact introduced him to Fillmann. The network can widen a search, though it is Fillmann's preferred method rather than a complete hiring system.

03

Hiring and negotiating

Fillmann describes complementary sales profiles and customer-centered deal structure.

For enterprise accounts, he looks for complementary profiles: a closer who can carry a deal, a visionary who can frame a customer's future, and a hunter who pursues opportunities. He asks candidates what work excites them and about times they created demand that had not previously been explicit.

Creating demand, in his view, means understanding a customer's problem and showing how a solution could help meet its goals. He wants salespeople to start with the customer's plans and work back to technology, rather than begin by presenting product features.

On negotiation, Fillmann cautions against sending a price before understanding the buyer's measures of success and financial priorities. He asks about cash flow, total cost, timing and other levers, then explains the seller's own constraints. His goal is a predictable structure that can work for both sides.

He recommends first asking how to serve the customer, including what internal objections they expect. Once both sides' priorities are visible, the team can identify points of friction and try to solve them. Not every buyer will share information, he acknowledges, and no negotiation is guaranteed to go smoothly.

For coaching, Fillmann prefers preparation, role-play, attending meetings together and an immediate debrief over waiting until a quarterly review. He asks for feedback on his own performance first so the conversation is about improving the craft rather than a leader judging a subordinate.

04

Coaching and onboarding

He discusses hiring mistakes, supporting potential and preparing new representatives.

A mistake he has made is pairing two highly dominant people whose egos conflict. He prefers pairing an experienced leader with a high-potential colleague who can learn quickly, while paying attention to team chemistry. The labels are his shorthand, not a formal personality test.

He generally prioritizes potential over experience, with an exception for very high-profile accounts where an inexperienced person could be set up to fail. A newer representative should receive preparation, role-play and support from a senior colleague before taking full responsibility.

For long enterprise sales cycles, he reserves time to work directly with reps on accounts. He says managers should set realistic expectations: a deal with a one- or two-year cycle may not close in a new hire's first year. Joint preparation, meetings and debriefs give a leader information before revenue arrives.

His onboarding sequence begins with an account hypothesis, an estimate of opportunity and a sales plan that balances smaller transactions with larger bets. An industry playbook supplies a concise starting point for discovery rather than replacing it.

He describes a small set of slides covering likely industry problems, relevant solutions, customer examples and a success plan. The team should adapt the template and validate assumptions. In his view, shared materials let a new rep spend more time in customer conversations and less time recreating work.

Fillmann says teams build playbooks together from recent customer experience, including mistakes. Salespeople, industry specialists and engineers can identify what worked, revise the materials and keep them current as circumstances change. His claimed speed improvements are his experience, not a controlled measurement.

05

Urgency, value and forecasting

The speakers examine buyer timelines, financial justification and uncertain forecasts.

To create urgency, he works backward from the buyer's own deadline. If a system must launch in July, testing, setup and contracting may have to start months earlier. A success plan can make that sequence visible; pressure based only on the seller's quarter end is less persuasive in his view.

When deals slip, he asks whether the proposal can make financial sense to a CFO who may never meet the sales team. He suggests quantifying relevant cost savings, avoided costs, time to value or other benefits, with the customer's team validating assumptions. Qualitative benefits can complement that case but may not resolve a financial objection.

He says economic conditions had shifted many buyers toward efficiency and doing more with less in 2023. Sales messaging should follow the customer's current priorities rather than repeat an old pitch. This is his observation of that period, and buyers' priorities differ by company.

For forecasting, he combines historical conversion mathematics, technology-assisted pattern analysis at scale and a bottom-up review of individual deals. He then compares the views and asks whether they make sense in light of customer conversations. The process can reduce uncertainty but cannot eliminate it.

06

Deal reviews and cross-functional work

Fillmann describes weekly reviews, account relationships, customer success and incentives.

Fillmann distinguishes useful hands-on leadership from a controlling manager who takes over every deal. He wants leaders close enough to customers and representatives to identify problems and help, while making the rep's own goals and development central to the conversation.

His weekly review is typically about 90 minutes: an initial flexible period for urgent issues, followed by structured deal reviews. For each major opportunity he asks why it matters to the customer, what could prevent the customer's goals, who is involved and what the next step is.

The wider team—including industry, value, solution and sales colleagues—joins to improve the work as peers. He wants participants to bring incomplete ideas without fear of being judged. The aim is to strengthen the proposal and help the representative succeed, not merely inspect a forecast.

To reduce dependence on a single champion, he recommends understanding the account across functions and building relationships before a deal is imminent. He gives examples such as using the customer's product, talking to frontline staff and connecting relevant executives. Those activities should serve the customer's needs, not become contact collecting for its own sake.

He says alignment with peers in other functions is a major part of a sales leader's job. He asks how colleagues are measured, what they need from sales and what sales needs from them. Customer-success teams can face different incentives and too many demands from both customers and sales.

Bringing customer-success colleagues into sales conversations early can help them understand what is being sold and prepare for delivery. Fillmann recommends highlighting their work and agreeing on success measures rather than handing them an unexpected commitment after a deal closes.

On compensation plans, he wants the way a rep is paid to align with how the company is measured. If leadership, sales management and representatives are rewarded for conflicting outcomes, tension can appear in customer relationships and execution. He gives a principle rather than a universal commission formula.

He considers it hard to find people who can envision a customer's future state, work backward through obstacles and communicate that vision to senior executives. His analogy is seeing the potential of a house despite an unattractive paint color. He values retaining and supporting people with that skill.

07

Final advice

He reflects on remote selling, hiring, empathy and a product he admires.

In quick-fire questions, Fillmann says listening, discovery and personal relationships remain important. He missed face-to-face selling during COVID, although his team used remote briefings and virtual events to stay connected. He sees remote tools as useful but believes building a new relationship can be harder without in-person contact.

He thinks withholding information as a sales tactic has become less useful when buyers can research products and companies themselves. Transparency and a conversation about what the customer already knows are more productive in his view.

As companies move upmarket, Fillmann recommends adding experienced enterprise sellers while retaining people who understand the existing business and smaller customers. Asked to choose between industry knowledge and deal-size experience, he favors customer and industry relevance while acknowledging that unusually large deals also require experience.

His advice to a new sales leader is to serve the team and help representatives succeed, rather than focus on personal status. He also wants leaders to retain empathy for the difficulty of a rep's job and stay close to customers as their own work becomes more internal.

Asked about an admired sales strategy, Fillmann names Miro and says its collaborative whiteboard helped his teams work visually while remote and in person. Stebbings notes that a Miro contact introduced him to Fillmann. This is a personal product endorsement with that relationship disclosed, and the interview closes with thanks.

同じチャンネルの記事

23:48EN
20VC with Harry Stebbings· 2026年10月26日ポッドキャスト · 2 人Satya Nadella on Zero Trust for AI and Why Every Company Should Own Its Intelligenceゲスト Satya Nadella · ホスト Harry StebbingsThe Microsoft CEO argues that capable agents need security boundaries even as alignment research remains unsettled, and explains why firms should retain the value created by their own AI use.エンタープライズ AIAI security評価(Evals)+2
1:13:26EN
20VC with Harry Stebbings· 2026年10月24日ポッドキャスト · 2 人Naveen Rao on Energy, AI Hardware, Verification and the Future of Roboticsゲスト Naveen Rao · ホスト Harry StebbingsThe Unconventional AI founder argues that energy efficiency will shape AI hardware, while the growing volume of model output makes verification more valuable.EnergySemiconductorsInference+2
59:41EN
20VC with Harry Stebbings· 2026年10月22日ポッドキャスト · 3 人20VC: Venture Fund Size, AI Valuations and the Changing Software Marketゲスト Jason Lemkin, Rory O’Driscoll · ホスト Harry StebbingsHarry Stebbings, Jason Lemkin and Rory O'Driscoll debate venture concentration, infrastructure risk, code review and the assumptions behind fast-growing AI companies.Venture CapitalInvestingAI cost & performance+2
1:19:50EN
20VC with Harry Stebbings· 2026年10月19日ポッドキャスト · 2 人Sameer Dholakia on AI Investing, Bessemer's Growth Strategy and Company Cultureゲスト Sameer Dholakia · ホスト Harry StebbingsThe Bessemer partner explains his approach to pricing fast-growing AI companies, backing founders and building teams, while discussing the risks behind his optimistic forecasts.Venture CapitalAI StrategyLeadership+2
1:03:05EN
20VC with Harry Stebbings· 2026年10月17日ポッドキャスト · 2 人Harrison Chase on Building Reliable Agents, Model Routing and Memoryゲスト Harrison Chase · ホスト Harry StebbingsThe LangChain co-founder explains why agents remain difficult to control, where domain expertise matters, and how his team manages coding-agent costs.AI agentsAgent orchestration評価(Evals)+2
1:17:09EN
20VC with Harry Stebbings· 2026年10月15日ポッドキャスト · 3 人20VC on Pro Rata Rights, AI Pricing and the Changing Software Marketゲスト Jason Lemkin, Rory O’Driscoll · ホスト Harry StebbingsHarry Stebbings, Jason Lemkin and Rory O’Driscoll debate investor rights, model economics and the choices facing software companies and their employees.Venture CapitalAI cost & performanceRobotics+2