Ben Fiechtner on Deal Design, Forecasting and Building Sales Teams

Ben Fiechtner organizes sales execution around four activities: create pipeline, convert opportunities, close deals and manage churn. The Clari chief revenue officer says sellers tend to seek the quickest path to an outcome, so a forecasting process must be simple enough to use consistently.

Harry Stebbings talks with Fiechtner about deal construction, forecasting, enterprise sales and hiring. Fiechtner leads revenue at Clari, which sells forecasting software; his discussion of its tools is informed by that commercial role.

Fiechtner and a college friend each invested $300 in a Wisconsin-themed T-shirt business. The first shirts sold out in about two days, and they built online and wholesale channels. His friend still runs the business; Fiechtner later sold his stake to him.

A first large sale to the University of Wisconsin bookstore helped Fiechtner discover that he loved selling. He enjoyed helping a customer see an overlooked market, sharing a point of view and the competitive energy of winning a deal.

He says many technology companies begin by selling features and talking about themselves. A better starting point is to research the customer's business and arrive with an informed view of its problems, a proposed direction and a specific way the seller can help. Questions matter, but preparation comes first.

Deal construction starts with understanding both sides' constraints. The buyer's budget, operating or capital expenditure treatment and cash flow may be controlled by finance or procurement as well as the business champion. A seller should learn those needs and know the flexibility available internally before proposing terms.

He asks how the buyer wants to deploy and work backwards from when users need to be live, the value expected and implementation complexity. He then shares the available levers, including service start date, contract length and commercial terms, and looks for a structure that serves both sides.

For a named-user product, he says a larger user commitment can improve the price; the same logic may apply to a consumption commitment. Start date matters to the seller's timing, followed by contract length and payment conditions. These are his negotiating priorities, not a universal accounting rule for every SaaS contract.

Discounts need governance and reasonable guardrails, but Fiechtner tells sellers to own pricing and explain how a proposal supports customer success. He describes gradual ramps for customers with constraints when the parties have enough information and a credible long-term arrangement.

To create urgency, he recommends identifying a genuine business event and working backward from it. He also wants to understand the personal win for a champion or economic buyer: a stakeholder who feels connected to the project and its success may be more motivated to move it forward.

He favors involving multiple stakeholders, including finance, and asking directly for introductions rather than inventing a pretext. A seller can explain that understanding the buying process prevents wasted effort on both sides. He says that honest approach often worked for him, though his experience is not a measured conversion rate.

Fiechtner warns against excessively delayed payment for customers with cash constraints. He has made such accommodations, but says they can end poorly and require careful judgment; higher interest rates also make cash timing more important.

The CFOs he speaks with often say they are spending differently rather than simply spending less. He observes platform consolidation and more spending on generative AI, with buyers looking for measurable business outcomes. This is an account of his conversations, not a market-wide spending survey.

For forecasting in volatile markets, he emphasizes a simple process and consistent questions. A call that only asks whether a deal is still good is insufficient. At UiPath and Clari, he says, he used a 13-week quarterly revenue cadence; the episode title says 12 weeks, but the spoken framework is 13.

The first week starts by reviewing deals that slipped from the previous quarter. An attempt to pull a deal forward that could not complete its necessary steps is less troubling to him than an unexplained slip. The review is meant to locate risks and opportunities, not punish the seller.

Next, the leader submits a forecast and builds it back up from identified committed deals. If the commitment is $1 million, the deals behind it should add up to that amount. Leaders can challenge the team to find more, but he warns against accepting optimistic stories without supporting evidence.

He also reviews renewals at least a quarter ahead because meaningful changes to retention or expansion can require three to six months. Usage and adoption signals alongside contract size help identify large at-risk renewals that warrant early attention.

The fourth first-week check is pipeline coverage, assessed against historical conversion rates at each stage. Fiechtner says forecasting tools can provide a prediction, but process and judgment determine what leaders investigate and do with that signal.

His team groups the quarter into four themes: create, convert, close and churn. Early weeks focus on pipeline generation and coverage; around week six attention turns to stalled opportunities; the last three weeks concentrate on closing; renewal risks are monitored farther ahead throughout.

For conversion, he looks for deals stuck at a stage and missing elements in the sales qualification process. His leaders record forecasting calls and he reviews summaries, allowing him to focus on specific risks such as legal review, security or weak stakeholder support rather than asking for a generic status update.

Fiechtner describes using Clari to surface at-risk deals and inspect calls, engagement and qualification information. He says the goal is to direct limited leadership time toward the largest gaps. Clari sells this kind of software, so his description also reflects his employer's commercial interest.

Closing important deals requires cross-functional trust before the urgent request arrives. A sales leader should have working relationships with product, marketing and the CEO so that the right help—a product discussion, a marketing effort or something else—can be mobilized without bringing an unnecessarily large team to every meeting.

When a salesperson says a customer loves the product but a deal slipped, Fiechtner asks who decides, what criteria apply, whether funding exists and what event creates urgency. A friendly champion is not enough if the seller has not helped that person navigate the buyer's internal process.

His most painful missed commitments often reflect a failure to understand how the customer actually purchases. Even being named the preferred vendor does not guarantee a deal will close if legal, approvals or other steps have not been mapped.

A good handoff to customer success starts during the sale. Fiechtner wants the team to map the customer's desired outcomes, deployment timetable and implementation needs before signing, so the success team inherits a practical plan rather than a promise disconnected from delivery.

Moving from commercial accounts to enterprise does not change the need to understand and solve customer problems, he says, but it introduces more stakeholders and complexity. At Salesforce, he was advised to treat a large global account as many smaller accounts with distinct problems that could eventually support an enterprise agreement.

Stebbings points out that a $5,000 annual contract and a $500,000 contract cannot receive the same resources. Fiechtner agrees: the solution-selling motion can be similar, but larger accounts require more capacity, while long-tail customers may need self-service. Allocation should be revisited as opportunities change.

For sales enablement, he favors frequent, specific coaching by frontline managers over relying only on long mandatory presentations. Formal training has a place, but a small startup may benefit more from leaders who make feedback and accountability part of daily work.

He cautions against moving into enterprise solely because larger contracts exist. Clari chose to shift capacity toward enterprise based on its product and a board-level strategic decision, he says. Some founders may rationally remain focused on smaller customers if that is where the product fits.

A startup can test enterprise demand with a named account before committing the whole company. But large customers may require substantial custom development, forcing tradeoffs against the existing roadmap. The test should reveal whether the opportunity justifies that investment.

Vertical sales requires learning the customer's language and specific problems. Fiechtner says his team had to reframe forecasting for medical-device customers, whose consumable demand differs from a conventional business-to-business opportunity pipeline. Sometimes a seller must also recognize that its product is not a good fit.

Specialization can cost more because account executives, sales engineers, customer success and messaging may all need industry knowledge. He remains a strong supporter of vertical strategies, while Stebbings argues companies can begin testing a few industries early and learn through customer conversations.

Stebbings describes an investment in a restaurant payments company that uses salespeople who speak customers' languages and understand their communities. He discloses that his firm invested in the business. Fiechtner sees dedicated vertical approaches as a way to align the offer with the customer's context.

For hiring, Fiechtner prioritizes three qualities: attitude, aptitude and authenticity. He asks candidates why they have not been more successful, seeking evidence that they can identify their own growth areas rather than attribute every problem to territory, quota or product.

He also looks for curiosity about the company and whether candidates see imperfections as opportunities to improve things. His estimate that 60% to 70% of sellers cite factors outside their control is a personal interview observation, not a representative study.

Aptitude includes intellectual curiosity about the product, market and customer. He encourages candidates to ask questions they genuinely care about rather than rehearsed questions chosen to impress an interviewer.

He has no objection to a salesperson being motivated primarily by money if the person meets the other criteria and is honest about it. Understanding a candidate's motivation helps him assess fit and support that person's performance.

A favorite closing question, in interviews and customer conversations, is whether there is anything he failed to ask. It gives the other person room to identify an important issue that has not yet surfaced.

Fiechtner says fear of failure and a competitive streak helped drive his career. He also dislikes letting people down, which can support customer and team relationships but can become a tendency to seek approval.

Stebbings suggests kindness and authenticity may make difficult decisions harder. Fiechtner accepts the feedback and says direct, clear feedback can be kinder than avoiding an uncomfortable conversation. He has worked on that skill over the preceding three to four years.

He moved away from artificial role-play interviews after finding that interviewers did not always play their assigned roles well. Instead, candidates present an account plan and executive point of view as if briefing their actual managers for a customer meeting.

That exercise reveals how candidates prepare, understand customer problems and propose distinctive value. He considers lack of preparation a frequent interview failure, while Stebbings notes that candidates may be juggling many interviews. Fiechtner still sees preparation as something each person can control.

Authenticity is the third hiring criterion. He says performative attempts to act like a stereotypical salesperson rarely work as well as being open about one's own style, motivations and strengths.

Compensation design should follow the go-to-market strategy, sales alignment and desired behavior, with financial constraints such as margin and growth included. He warns against simply making small adjustments to last year's compensation plan without revisiting the sales motion.

To prevent a lightly resourced account manager from facing a competitor's full hunting effort, he recommends choosing segments and accounts carefully. At Clari, he says, the team narrowed enterprise account focus and staffed priority opportunities more heavily rather than giving every enterprise representative 100 accounts.

In quick-fire questions, he says artificial month-end or quarter-end expiration tactics have lost their power because buyers can see through them. He contrasts that with genuine customer deadlines discussed earlier in the interview.

At UiPath, his key lesson was to align sales capacity with product-market fit. He saw strong potential in banking and healthcare that geographic staffing had not captured, then worked with others to concentrate resources there. He says the bet paid off, without providing an attributable return figure.

Sales leaders can fail by copying the playbook from a previous employer without listening to a new company's circumstances. Fiechtner recommends bringing principles and frameworks, then adapting them to the product, team and maturity of the business.

Early in his career, a Salesforce executive encouraged him to stop imitating a uniform sales persona and be himself. Fiechtner says sellers can succeed through different strengths, whether relationship building or detailed, data-driven analysis.

He applies a similar lesson to marriage and family: be honest about priorities and put real effort into them. He describes learning to show up for his family after travel with the same attention he gives clients.

A senior leader once told him that an executive role came with extensive travel and scheduled time with children. Fiechtner sees more flexibility in modern sales work, but says prioritizing a partner and family still takes deliberate effort.