Draven McConville built trust in B2B sales by selling in a market where buyers had already rejected the category. He founded Klipboard, a field service management software company, raised $3 million in patient capital, scaled across the UK, Ireland, Australia, and the US, and sold to Kerridge Commercial Systems in 2024. This episode of the Predictable B2B Success podcast covers the specific mechanisms he used when buyers had decided software was not worth trying again.
Quick Answer: To sell B2B software in a market where buyers distrust the category, address the category failure first. McConville named the field service industry’s history of failed software implementations directly in sales conversations, then used transparent pricing with no setup fees, strict no-discounting, founder presence on early calls, and operationally specific case studies to separate Klipboard from the category’s reputation. Skeptical buyers need evidence, not claims.
About Draven McConville
Draven McConville was founder and CEO of Klipboard at the time of this recording. Klipboard, a name drawn from the paper clipboard that field engineers carried to every job, helped plumbers, HVAC contractors, and electrical businesses manage their mobile teams without the paperwork that was costing them revenue. He raised $3 million from a family office rather than venture capital, scaled the company across the UK, Ireland, Australia, and the US, and sold it to Kerridge Commercial Systems in 2024. McConville is now an active angel investor.
Watch the Episode
Table of Contents
Why B2B Buyers Reject Categories Before Meeting Vendors
The category trust deficit occurs when buyers reject an entire software category before evaluating any specific vendor. A Mercuri International survey of over 1,000 B2B decision-makers found that 99% say trust is crucial when choosing a supplier, but that statistic assumes buyers are open to evaluating vendors. In field service management, buyers had already paid for software that failed to deliver. They arrived at sales conversations not weighing Klipboard against competitors; they were weighing it against their prior experience of the category as a whole. According to McConville, overcoming this required naming the deficit directly: acknowledging the industry’s record of failed implementations before any discussion of products began.
Most founders diagnose pipeline stalls as one of three problems: the product needs work, the pitch needs work, or they need more leads. McConville had a fourth problem, and almost no playbook existed for it.
In field service software, roughly half of potential buyers had already decided software for their kind of business was not worth the bother. Not because they had tried Klipboard and rejected it. Because they had tried other vendors and been burned.
Category-level skepticism operates differently from standard product objections. Buyers who carry it are not open to product comparisons. They have pre-decided that software in this space does not work for businesses like theirs. The sales conversation collapses before it starts.
The signals are plain English. Prospects say things like “we’re not ready” or “our engineers won’t adapt to this.” These are not objections to Klipboard. They are objections to the entire idea of software deployment in their trade. Treating them as product objections, by iterating features or lowering price, misses the actual diagnosis.
Klipboard’s fix was to name the category problem directly. Sales conversations began by acknowledging why previous implementations in field service software had failed, and explaining specifically what Klipboard had built to avoid those failure modes. This gave skeptical buyers a framework for distinguishing Klipboard from the category’s track record.
How to diagnose a category trust problem: Ask three questions. Are buyers saying “we’re not ready” rather than raising specific product objections? Have they tried comparable software and been burned? Does your pitch address the category’s record of failure, or only your product’s strengths? If the answers are yes, yes, and no, you have a category trust problem. Changing the pitch or iterating features will not fix it. The sales narrative needs to change first.
In my work with funded B2B tech founders, this diagnostic step is one of the most valuable conversations a CEO can have before hiring another SDR. The question is whether the sales problem is a product problem, a pitch problem, or a category trust problem. The answer changes everything.
How Klipboard Solved the Problem Its Name Promised
Klipboard’s name wasn’t a branding exercise. It named the exact paper artifact the product was built to eliminate. Field engineers carried physical clipboards to every job, filled in triplicate forms on-site, and handed them back to the office, creating billing delays, errors, and administrative breakdown at the back end of every job. The product’s entire initial promise was to remove that clipboard. McConville found that solving only this one problem first, and delivering on it completely, built more trust than selling the full platform’s capabilities to skeptical buyers.
When field service prospects resisted full software adoption, McConville asked one question: “What’s the most painful thing? And if we could only solve that one thing, would you trust us to do it?”
The customers’ response was consistent: engineers weren’t getting their paper forms back on time. That caused billing delays. Fix that first. The scheduling, the invoicing, the accounting integrations: all real, all needed. But the entry point was the clipboard. Solve the one problem the prospect could feel immediately. Build trust on that delivery. Expand from there.
“Field service simplified” became Klipboard’s tagline, but it wasn’t invented in a marketing meeting. It came directly from feedback sessions with confused prospects. The more McConville stripped technical language, removing phrases like “cloud native SaaS platform with iOS and Android apps,” the more prospects engaged. The tagline emerged because simplification was the actual value being delivered, not just the product.
“We asked them, what’s the most painful thing? And if only we solved that one bit, would you trust us to do that one bit and not all the other bits?” — Draven McConville, former founder of Klipboard
A pattern I notice across early-stage B2B tech companies: founders want to sell the platform. The market is only ready to buy the solution to one problem. The founders who grow fastest are usually the ones who resist the platform pitch longest.
How Pricing Transparency Becomes a Trust Signal
The pricing structure communicates the company’s confidence before any conversation begins. Klipboard published its pricing without setup fees in a market where competitors were charging implementation fees and locking buyers into three to five year contracts. McConville held a strict no-discounting policy: if the price is right, discounting signals the original number was wrong. The 12-month contract was framed as mutual commitment: Klipboard absorbed setup costs; the buyer committed for a year. This made the commercial terms feel like a partnership rather than a vendor transaction.
McConville did not think about pricing primarily as a revenue decision. He thought about it as a trust signal that reached buyers before any conversation started.
The field service software market had conditioned buyers to expect hidden charges. Setup fees, implementation costs, long-term lock-in. Klipboard published its pricing. A single per-user subscription, no setup fees, a 12-month commitment.
The framing was direct. “We’re not going to charge you for the setup fees because we are committed to you. We need you to be committed for 12 months.” Both parties had skin in the game. Klipboard was absorbing real cost. The buyer was committing to a fair trial period. Competitors were signing customers to five-year contracts and charging thousands in implementation fees. Klipboard’s model communicated something different from first contact.
On discounting: holding the price was itself a signal. Buyers who received a discount began to wonder what else was negotiable. The original price stopped feeling fair. Klipboard’s no-discount policy told buyers the number had been set deliberately and would stand.
Buyers who committed for 12 months engaged more deeply with the product, achieved better outcomes, and retained longer than those in shorter-term arrangements.
“You should be selling on the value of what the product is going to bring to you and the return it’s going to bring. Not discounting because your sales team found it easier.” — Draven McConville
The Role of Patient Capital in Letting Trust Develop
Patient capital changes the practical decisions available to a B2B founder. Klipboard’s $3 million family office raise gave McConville a longer investment horizon than the typical venture capital fund cycle of three to seven years. In practice, this meant Klipboard could refuse buyers who were a poor fit, maintain pricing discipline through a strict no-discount policy, and invest in onboarding quality rather than acquisition volume. These decisions compounded slowly. Kerridge Commercial Systems cited Klipboard’s customer relationship quality as part of its rationale for the 2024 acquisition.
Venture capital-backed companies face fund return windows measured in five to seven years. That compression pushes founders toward tactics that erode trust: aggressive discounting to close deals faster, overpromising on the roadmap to win deals, and cutting support investment to scale more cheaply. Each of these decisions costs something that patient capital never needed to spend.
Family office capital does not remove performance pressure. McConville is clear about this. There were targets, growth expectations, investor expectations. The difference was the investment horizon. He could say no to buyers who were a wrong fit without panicking about the quarter. He could hold pricing. He could invest in customer success before acquisition efficiency.
From 500+ interviews on the Predictable B2B Success podcast, patient capital is among the least-discussed structural advantages in B2B trust-building and long-term credibility. McConville’s outcome, an acquisition partly driven by customer relationship quality, is the compounded result of that structural choice.
How Does the Sales Process Build Trust in B2B Sales?
The sales process mirrors the product experience that follows it. McConville designed Klipboard’s sales motion to demonstrate the qualities the product was meant to deliver: simplicity and attentiveness. Slow follow-up during the sales cycle communicated to prospects what post-purchase support would look like. Demos focused on the buyer’s specific workflow rather than feature breadth, signaling domain understanding rather than generic capability. Founder presence on early calls, without announcing his CEO role, served both intelligence and trust functions simultaneously.
McConville became known for joining customer calls without introducing himself as CEO. The reasoning was practical: announcing “I’m the CEO” changes the tone. Customers wonder if the CEO is watching their colleague, whether they’re being charmed for optics. By joining as an observer, McConville watched real sales and onboarding conversations without distorting them.
The CEO’s presence on calls served as a second trust signal, even when McConville did not announce his role. Customers who figured out they were speaking with the founder found it significant: no barrier to leadership, direct access, a company permeable enough that the person running it was still on calls. McConville’s first customers, many of whom he handled personally, remain customers of the business post-acquisition.
The CEO intelligence technique: Joining calls without announcing seniority generates two outcomes. Buyers speak more candidly when they do not know they are talking to the founder, producing unfiltered market intelligence. And the CEO’s presence, even unannounced, signals no barriers to leadership access, a trust signal that costs nothing. McConville used these conversations to calibrate pricing, identify onboarding friction, and diagnose whether objections were product- or category-related.
Response speed was non-negotiable. Slow follow-up during the evaluation signals the quality of post-purchase support. Buyers who wait three days for an answer during demos conclude they will wait three days as customers. Klipboard built rapid, substantive follow-up into the sales process as a deliberate trust mechanism, not a customer service nicety.
This is something I work on with B2B tech founders when we build their content systems: the sales process itself is a published signal. Every buyer who goes through it reads it.
What Proof Points Actually Convince Skeptical Buyers
Generic testimonials do not move buyers who distrust a category. McConville found that social proof in field service software needed to be operationally specific to the register: same trade, similar operational complexity, and a named outcome. A roofing contractor who reduced administrative time by a specific number of hours per week outperformed broad efficiency claims with another roofing contractor. Referral calls with unscripted access to existing customers carried the most weight because buyers knew those conversations were not managed by Klipboard, making the reference’s account independent evidence rather than vendor-curated content.
The instinct for most SaaS founders is to build a large case study library. McConville’s instinct was different: fewer case studies, more specificity.
A buyer in electrical contracting did not trust a case study from a facilities management company. They wanted to hear from a business in their own vertical, running comparable-sized operations, that had implemented Klipboard and seen a specific outcome they could name. This required staying narrow on customer acquisition in the early stages. Klipboard went deep into trade-specific verticals rather than spreading across every field service category. That focus enabled the operationally specific proof points that skeptical buyers needed.
The most powerful trust mechanism was unmediated: connecting prospects directly with existing customers for unscripted calls. The willingness to do this, handing a skeptical prospect an unmanaged conversation with a real customer, was the most credible proof available. Buyers knew these calls were not curated. That independence was the signal.
Research supports this hierarchy. B2B buyers consult roughly seven internal and external sources before making a purchase decision. Among the most trusted: third-party content and peer-reviewed, user-generated accounts, each cited by 64% of buyers as among their most credible sources. Vendor-produced content ranks lower not because buyers don’t read it, but because they discount it as a category of social proof. The unscripted reference call sits at the top of this credibility hierarchy because buyers know the account is independent.
How Do You Scale B2B Sales Trust Beyond the Founder?
Culture becomes a trust signal when it shows up consistently in buyer interactions. Klipboard maintained consistent attentiveness from the initial inquiry through the demo, handover, and support. When releasing features, the team framed every release as “here’s what the community asked for” rather than “look what we built.” Productboard (which McConville credits by name) gave customers visibility into the roadmap, confirmation when their requests shipped, and a channel to upvote upcoming features, making product development feel collaborative rather than broadcast.
Sales, customer success, and product were not siloed at Klipboard. There were clear channels between departments so that what a prospect said in a demo reached the product team. What a customer reported in a support call fed back into roadmap prioritization. This became systematized rather than personality-dependent as the company grew.
On distribution partnerships: McConville learned early that full reseller arrangements are risky for early-stage companies without the internal frameworks to manage them. The control of sales quality, and therefore trust quality, shifts to the partner. His alternative was a referral model.
Klipboard joined the Xero marketplace as a referral partner rather than a reseller. Leads from Xero’s customer base were referred over with a referral fee. Klipboard maintained complete control over the sales process, demonstration quality, pricing discipline, and post-sale onboarding. The trust Klipboard had built remained Klipboard’s to deliver. The channel generated opportunity without diluting the trust system.
A Series A fintech founder I work with faced a similar choice between reseller and referral arrangements with an accounting software platform. The referral structure, as McConville found, is almost always the right call at this stage.
AI, Domain Knowledge, and the New Competitive Moat in B2B
AI has democratized software development, but it has not democratized domain knowledge. McConville argues that the competitive moat in vertical SaaS is no longer the code. It is the accumulated understanding of a specific industry’s workflows, pain points, and buyer behavior. Anyone can build software now. The founders who win are those who know the problem space well enough to architect the right solution, and have the customer relationships to know what right means.
During Klipboard’s growth years, investors pushed for AI stories regardless of whether buyers in field service trades were ready for AI capabilities. The gap between investor narrative and buyer readiness was real and expensive for founders who chased the former.
McConville’s test was consistent: does this feature deliver a return to customers, or does it deliver a story to investors? Features that passed the first test were worth building. Features that only passed the second were noise.
On the broader competitive question, his position was direct. “The domain knowledge is the moat.” B2B tech founders who have spent years in a specific vertical, with customer relationships, an understanding of failure modes, and credibility with buyers, are harder to displace than founders who arrive with technology alone. As building gets cheaper, that gap widens.
He also applied this internally: AI should optimize the organization, not just the product. How do you use AI to onboard customers better? How do you use it to onboard new employees more efficiently? The same toolset that democratizes software builds can be turned inward to make a lean team perform like a larger one.
💡 CEO Takeaway: How to Build Trust in B2B Sales
- Diagnose before you iterate. If your sales cycle is stalling, identify whether the problem is product, pitch, or category trust before changing anything. Treating a category trust problem as a pitch problem wastes money and time.
- Solve one problem completely before expanding. Klipboard’s name deliberately described its initial product scope. Prospects who trust you with one problem become customers who buy the rest.
- Price structure is a trust signal, not just a revenue variable. No setup fees and a strict no-discount policy signaled to Klipboard’s market that the company was serious. Opaque or inconsistent pricing tells buyers the opposite.
- Make your sales process mirror the product experience. If you promise responsiveness post-purchase, your demo follow-up speed is the first proof point. Buyers read it as a preview.
- Use referral partnerships before reseller arrangements. Referrals generate opportunity while keeping sales quality in your hands. Resellers at an early stage shift trust delivery to partners you cannot fully manage.
Frequently Asked Questions: How to Build Trust in B2B Sales
How do you build trust in B2B sales quickly?
The fastest path to B2B sales trust in a skeptical market is solving one specific problem completely before pitching the full platform. McConville found that buyers who trusted Klipboard with paper-form capture became multi-module customers. Naming the category’s failure record in early conversations also shortens the timeline: it addresses the real objection rather than working around it.
What is a category trust problem in B2B sales?
A category trust problem occurs when buyers reject an entire product category before evaluating any specific vendor. It differs from a product objection (which targets your offering specifically) or a pitch problem (which targets how you communicate). Category trust problems show up as phrases like “we’re not ready” or “our team won’t adopt it,” language that targets the idea of change rather than the product’s capabilities. Diagnosing this correctly is the prerequisite for addressing it.
How does pricing affect trust in B2B sales?
Pricing communicates company confidence before any conversation begins. Klipboard’s no-setup-fee, no-discount model told field service buyers the company had set a fair number and intended to stand by it. In markets where previous vendors charged hidden implementation fees, publishing transparent pricing was a differentiator visible before the first call. Discounting on request has the opposite effect: it signals the original price was wrong and makes buyers question what else is negotiable.
What proof points work best with skeptical B2B buyers?
Operationally specific case studies from the same vertical outperform generic testimonials with skeptical buyers. A roofing contractor trusts a case study about another roofing contractor of similar size more than a broad productivity claim. Unscripted referral calls, where prospects speak directly with existing customers without vendor management, carry the highest trust weight because buyers know the account is independent. Building a smaller, deeper library of trade-specific proof points beats a large library of generic success stories.
How can a B2B founder build trust without being present on every sales call?
McConville’s answer is culture systematization. The listening posture he established early- respond fast and communicate roadmap progress transparently- became embedded in each department. He used Productboard to give customers visibility into the roadmap and confirmation when their requests shipped. He built formal feedback channels between sales, customer success, and product. The founder’s presence becomes unnecessary when the culture carries the same trust signals.
Conclusion
McConville’s playbook is not complicated, but it requires a founder to resist the common shortcuts. Stop improvising and build like a real organization from day one: clean governance, proper contracts, and a CRM. The founders who skip these steps spend acquisition due diligence trying to reconstruct what they should have documented four years earlier.
On trust, his diagnostic is practical. Before hiring another salesperson or rewriting the pitch, ask whether the problem is with the product, the pitch, or the category. If it is category, fix the sales narrative first. Name the category failure. Lead with the one problem you will solve completely. Build from there.
The Klipboard story, from $3 million in patient capital to a 2024 acquisition by a group serving 55,000 customers, is what a founder produces when trust is an operational discipline rather than a sales technique. If you want to build trust in B2B sales through content systems and authority assets that compound over time, this is the exact problem I help solve at Sproutworth.
Some topics we explore in this episode include:
Listen to the episode
Subscribe to & Review the Predictable B2B Success Podcast
Thanks for tuning into this week’s Predictable B2B Podcast episode! If the information from our interviews has helped your business journey, please visit Apple Podcasts, subscribe to the show, and leave us an honest review.
Your reviews and feedback will not only help me continue to deliver great, helpful content but also help me reach even more amazing founders and executives like you!
Related Episodes
If this episode was useful, these related conversations on the Predictable B2B Success podcast go deeper on adjacent ground:
- Predictable B2B Success — Browse all episodes
- Building a B2B Sales Process That Earns Trust at Scale
- How B2B SaaS Founders Build Authority Through Content
