Do you Sell or Partner?

Share This Post:

In an earlier article, I argued that just as all new products go through a beta phase followed by a production phase, startups should follow a structured commercialization process starting with Partnerships, followed by Sales.

To be clear, when I refer to ‘partnerships’ in this context I’m talking about a reciprocal relationship with prospective customers where both parties are learning and deriving value.

Customer partnerships are essential for any new product introduction and should form the base of all customer engagements until you can achieve a handful of happy, referenceable customers.

During the partnership phase the Founder, CTO, CEO or head of Business Development is responsible for ongoing engagements with prospective customers.

In this blog, I’d like to share some components that I believe are part of a strong B2B customer partnership strategy. For more information on each of these, please contact the Evidology Group and we’d be happy to share specific tools, templates and best practices.

Customer Validation: This is the critical first step of testing and validating your ideas by having “discovery” conversations with many prospective customers. These Customer Validation discussions are designed to learn what is most important for customers and why. The Customer Canvas tools and methodology developed by the Evidology Group were specifically designed to guide this effort.

Trusted Expertise: As a by-product of Customer Validation discussions, you will hopefully find a handful of early adopters who are interested in follow-on conversations to learn more about your proposed solution and benefit from your expertise. These informal partnerships can help you build a much deeper understanding so that you can design and deliver a better solution.

Customer Advisors: Ongoing discussions with early adopters will hopefully lead to a formal Customer Advisory relationship where early adopter customers are retained as formal Advisors to the company, often compensated with stock options when allowed by their company policies. Unlike figurehead advisors promoted on slides and websites, I encourage you to hold regularly scheduled monthly 1-hour calls with each advisor. Each call should include a pre-mail with background and topics or big questions to be discussed and a follow-up email with a summary of key take-aways. In the spirit of partnership, be sure to share insights with your Advisor such as technology trends and non-confidential insights you’ve learned from others in the industry.

Design Partner Program: Complex products can often benefit from shortening the communication path between customers and your design team. Involving these early adopters in product spec reviews, UX design, or feature demos can help immeasurably in designing a better product faster that is better aligned to a real-world customer environment. Whereas a Customer Advisor is typically one individual providing advice, a Design Partner Program typically involves one or more people in a customer organization sharing their requirements and feedback, and should therefore be documented with clear terms of engagement around resource commitments, IP ownership, financial considerations, timelines and deliverables.

Beta Partner Program: The objective of any beta program is not to make money or recover costs, although that may be a worthy by-product. It serves several purposes beyond product hardening such as helping you ensure the product truly solves the customer problem and providing a valuable reference to the media, investors and other prospective customers in the form of testimonials, interviews or white papers. Moreover, the beta program should be designed to help you collect the information you need to measure the economic and KPI impact your solution has had on the customer’s business. A formal proposal may be effective in clarifying the expected contribution of both parties.

Sales ahead of partnership is certainly putting the cart before the horse. By nurturing a productive and mutually beneficial partnership engagement with prospective customers, you’ll learn, adapt and collect the necessary evidence that will ultimately set you up for a successful sales strategy.

For more information, please contact the Evidology Group and we’ll lead you through the partnership process. We’ll also share more templates, tools, and best practices.

More To Explore

Customer Discovery: Do You Pitch, Use a List of Questions, or Follow a Script?

In an earlier blog post, we covered the five major elements of a Customer Discovery Conversation Plan. One of the elements was a Conversation Script. Our clients tell us this script has more value than they ever imagined prior to creating and using one. What exactly is a “script” and why is it needed? Isn’t a simple list of questions sufficient? Briefly, our version of a customer conversation script for concept validation has: A framework of topic areas and their planned order in the conversation Statements to set the context, for discussion, and to transition between topic areas A list of specific questions to be asked under each topic Sure, you could just make a list of questions but here are three reasons why you should consider creating a script: The context you set, the order in which you explore topics, and the way you ask questions can make a huge difference in the relevance and quality of information collected This approach is more likely to foster a true conversation, rather than a transactional Q&A exchange, and one that could become the first of many conversations with that individual Conversations easily go in directions never imagined. Suddenly your time is up and call goals have not been met. A script containing a framework or roadmap makes it easier to keep your goals in mind. So for this post, let’s focus on the starting point – a general-purpose framework you can adapt for conversations based on the evidence you need to collect from each target persona. For each persona and set of conversation goals, develop a targeted script by keeping the topic sequence but removing non-relevant topic areas, adding/deleting/altering the number and type of questions in each area, and updating how you transition from one topic to the next. For example, when talking with end-users about simulation-based training you’re more likely to focus on their priorities and problems: how they do things now (simulators being used), and what capabilities deliver value for them. And when talking with department heads (budget owners) about the same subject, the focus will be on their priorities and problems: how they do things now (how simulation-based training fits within the curriculum), and how they fund and buy these types of things. With that in mind, here’s a master framework you can adapt to your own needs: 1. Conversation Expectations At the outset, you want to take a minute or two (literally) to set up the conversation for success. You want to demonstrate professionalism, establish credibility, and show respect for their time. This section is primarily statement-based where you: Introduce participants on your end and their role in the call (conversation leader, notetaker, observer, etc.) Restate the reasons and objectives for the call to reinforce prior communications leading to this moment Tell the customer what to expect during the call (you’ll make statements, ask a series of questions, etc.) and how their feedback will be used Confirm the available time 2. Customer Profile In this section, you ask questions to understand the scope of their role and responsibilities, about their team – its size and structure, how long they’ve been in that position and/or the industry, etc. Your goal is to understand the basis of each person’s perspective and what might be shaping their feedback. Equally important, you want to be able to identify common characteristics about them and their organizations for creating segment profiles when looking across all conversations for patterns or trends. Additionally, this information informs a more granular Ideal Customer Profile. 3. Problem Importance & Change Motivation Next, start collecting the evidence needed to answer the critical questions driving your conversation plan. We like to start with validating whether the problem you’re trying to solve exists in their mind and where it fits relative to your customers’ perceived priorities, problems, and their urgency to solve the problem. You want to know: The order of magnitude of this issue; is it a 5-out-of-5 burning issue or a 1-out-of-5 nice-to-have? How they measure the impact of this problem being solved or not being solved; the KPI or performance metrics impacted Whether solutions to problems like this get funded 4. Current State Once you know how your target problem fits in their world, it’s natural to shift the conversation to how they do things today, dig a bit deeper into how the problem manifests itself, and what current plans or projects exist to solve the problem. In this section, you uncover critical information such as: Existing tools, systems, and processes Competitive options with associated strengths and weaknesses Current economic impact if not covered earlier Solution compatibility considerations Change management challenges General background for interpreting responses in the next topic area 5. Solution Value Drivers & Differentiators Now with an understanding of the problem from their perspective, how things are being done today, and what’s being considered for the future, the conversation easily shifts to getting feedback on your proposed solution. This part of the conversation is about getting their thoughts on each major capability that makes up your solution. Does each capability have value, how much value, how is that value measured, and which capabilities are more important than others? You want to know the “why” behind their answers and dig into what they believe to be meaningfully different and better than other available options. 6. Future State. After receiving feedback and creating an understanding of your proposed solution, it’s time to probe a bit more on its relevance and overall value by assuming your solution – plus their view of the ideal solution – has been implemented. You want to further uncover the impact on their business, objectives, and goals. 7. Buying Process After validating the target problem and proposed solution, it is critical to gain an understanding of how customers buy. What triggers the buying process, who are all the stakeholders, what decision-making steps do they go through, where does funding come from, how does that process work, and how long does it typically

Read More »

What Did You Learn About Your Customers This Year?

As we round out the year, I think it’s been an incredible opportunity for startups to think about how we can do business smarter. There’s never been a better time to stop selling and start learning; to build a customer-centric culture and to look for an optimized path to product/market fit. We’re truly delighted to have helped many companies do just that – and we take great pride in the impact we’re making in transforming their businesses. For the Evidology Group, it was certainly an exciting time. Over the past year, we’ve built out a comprehensive repertoire of best practices and templates around customer discovery, concept validation and product validation which has enormous consequences on sales, marketing, product strategy, pricing, fundraising and recruitment. Below is a quick summary of the blogs we’ve written. For a copy of our best practices and templates, please reach out to us and we’d be happy to share this content with you. Here’s to a happy, healthy and prosperous new year! Adam and Dougwww.evidologygroup.com You know your product. We can help you sell it.

Read More »

Subscribe to Our Blog

Subscribe to our blog and find out about our upcoming webinars.