Selling in mid- to large-sized businesses is never as straightforward as selling to small businesses. The MIT Entrepreneurship Center uses the term “Jury” to refer to the group of stakeholders that must get involved in B2B customer development.
As we saw before, the Jury includes the decision makers, the influencers and the Economic Buyer in B2B customer development.
This week, we look at the role of one of our key Jury members: the Technical Buyer — the person most concerned with the security and feasibility aspects of your solution.
The Technical Buyer in B2B Customer Development
The technical buyer doesn’t typically have final approval, but they have the power to reject your proposal.
They bring specialized expertise to the evaluation team and typically play different roles. Their approach is often that of skepticism.
Technical buyers care that your solution does what you say it does. Their concerns relate to the measurable and quantifiable aspects of a proposal.
They’ll ask questions about the specifications, implementation and expected challenges in transitioning to your solution.
Next, we’ll look at the role of the last important Jury member: the User Buyer.
⚡⚡ Enjoyed this content? I go into way more detail on this subject in Lean B2B. It covers the ins and outs of finding traction in the market for B2B products. Check it out »
Download the First 6 Chapters for Free
This sampler covers the differences between B2B and Business-to-Customer (B2C) product-market validation, shows you how to define your vision for success, find early adopters, select market opportunities and assess a venture's risk. Download The First 6 Chapters Today »