During the next six months, you and your team will systematize your sales process by installing Salesforce and creating a sales wiki, hire your first sales leader/rep/pod, and scale your pipeline and net-new customers. This phase usually covers months 12–18 in our timeline.
Up to this point, we’ve been using an 18-month timeline, but it’s important to call out that it’s not the end of the world if your timeline stretches to 24 months. If you need to spend more time in any of the three phases we’ve outlined (innovators, design partners, early majority) you can factor in a six-month buffer. If you start going beyond 24 months and haven’t hit the milestones for your next fundraising, then it becomes problematic.
Just like engineering teams use tools like GitHub as a central repository for all things code, your GTM team needs a similar repository, and that’s where Salesforce comes in.
Salesforce gets pigeonholed as a tool that only salespeople use, but in reality it functions as your GTM database and a source of truth for everything and anything related to your USER/BUYER journey. Even if you end up using tools like Amplitude, Marketo, Clearbit, Gainsight, or have all these sync to Snowflake, AWS, etc., Salesforce will still be the GTM GUI (graphical user interface) that all non-engineering teams default to.
The good news here is that we’ve already defined these stages — discovery, scope, validate, negotiate & close — so you can just input those.
Any prospects and associated companies that you want to pursue, have interacted with, or are currently trialing your product. Paying customers are not included here.
This is how you’ll track each sales opportunity, and it will include all the details around who you're working with (prospects/company), what you’ve learned about their current state, what products could solve their problem, and where they are in the sales process.
When you look at your sales opportunities and sales process, you’ll have to make a determination on when they are qualified to forecast for the quarter. This simply means you're X% confident that, based on what you’ve learned, they will buy from you by a specific date, for a certain price. Typically, when a sales opportunity enters "validate" in the sales process, you’re more than 60% confident, and would forecast it as “Best Case” for the quarter. When an opportunity is in the later part of the validate phase and you’re compiling the testing results, you should be 85%+ confident and would forecast that as “Most Likely”.
Forecasts usually have a breakdown that looks something like this:
If you were to make a call on what you would close that quarter based on the snapshot above (let‘s assume you’re halfway through the quarter), you might tell the board you’ll close at least $650K (all of your most likely deals, and half of your best-case deals).
During a quarter, you’ll probably start with the majority of opportunities in pipeline, have a bell-curve distribution in the middle of the quarter, and then should have the majority of opportunities in "most likely" by the last month of the quarter.
Dashboards & reports
Dashboards allow you to see different aspects of your GTM data/progress in real time across teams (marketing, sales, customer success, etc). Reports can be used for individuals, teams, or company-wide either for weekly workflows or quarterly board meetings.
Here are some examples of stats and questions you should track that your board (and potential investors) will likely want to see as well:
We’re aware that the majority of founders have never installed Salesforce (SFDC) before. Even if you have, it’s a 40–60-hour process that can require consultants or a lot of trial and error to get right.
That’s why we created The Unusual Salesforce Package for founders to download and install. This has our recommended configurations for all the features we outlined above, right out of the box. Documentation for installation, setup, and use is included.
This unmanaged package is meant for founders who purchased an SFDC Enterprise license and do not have a current instance of SFDC running with real data in it. Since the Unusual package has custom fields, if you install this on an existing SFDC instance, you run the risk of getting errors in your data.
Founders often ask us when they should bring on their first salesperson and what their profile should be. Whether you’re running a product-led or qualification-led sales process, this tends to occur at the same point in time and the profile you’ll look to recruit with is very similar across companies and products.
When you’re ready to start scheduling installs with design partners, you will probably be ready to recruit your first sales hire to offload managing the sales process. It's at this point when founders such as yourself tend to find themselves overloaded with all the responsibilities across the business.
Keep in mind, however, that you should never offload interacting with USERS, design partners, and customers. What you do offload is the tremendous amount of work around prospecting, scheduling, running the sales process, keeping SFDC up to date, etc. Anytime there's an interaction with a USER or potential user, especially when product feedback will be discussed, founders need to attend at least 60% of these meetings to always stay close to what the market is saying. If you’ve gone two weeks without talking to a USER or potential user, course correct immediately.
Since design partner installs are focused on product usage and feedback before you can even contemplate converting them to paying customers, it would be impossible to give a sales hire a quota to hit since 1.) that's not your focus at the moment and 2.) your pricing model hasn’t been figured out yet. This is why we advise founders to look for a sales hire who has the skill set and functions more like a revenue-generating product manager.
Recommended salesperson attributes:
Many of the sales hires you’ll interview will only be comfortable in a role where they have a playbook they can learn, sales enablement to bolster that learning, warm leads to start working, and a clearly defined quota they have a decent chance to hit if they work hard. This is not the environment of a Seed or Series A startup during the design partner phase.
You can use the qualities above as qualifying questions in your sales interview with them, and should also reference the list of sales interview questions we’ve built out in Hiring your first sales leader.
The first sales hire or “revenue-generating PM” is the one who helps you pioneer what’s possible in their role and what expectations should be across prospecting, sales process conversion rates, average sale prices, average time to close, etc.
You’ll also have an early indication of your sales yield. Sales yield is what a sales hire generates in revenue after you subtract their cost to the business. Ideally, you want to hit a sales yield of one ASAP, but will be below that threshold for the first few months.
For context, companies similar to Databricks, Segment, MongoDB, Sumo Logic, and AppDynamics would expect a commercial/mid-market sales rep to hit a quota between $500K–$1M annually, and would cost the business $160K–$240K in target earnings (OTE) between base and commission. This would produce a sales yield between three and four. The sales yield expectations would be similar for enterprise sales reps.
With your first hire, you’ll want to create a sales wiki. This is where all your sales materials and tooling live, including best practices and documentation. You'll standardize on this material as a basis for all sales activity as you expand your team. Examples of items you’ll need in that sales wiki are:
Once you have all of this documented, and after the first five to 10 customers, you should have a good idea of the repeatable aspects and sales yield, and can now create a “standard” sales role to fill, along with the supporting cast required. These sales reps are focused only on hitting and overachieving their quota by learning your product and sales playbook.
The sales attributes you’ll want to look for:
Then, some of the individual attributes you want to look for are:
We advise founders who need to scale their sales teams to think about doing so in pods of sales reps, solutions engineers, SDR/BDR, or support engineers. Your specific combination will derive from your learnings with your first sales hire and what your team needs to look like to support your initial customers. For some companies, landing the deals is harder and requires an SE/SA to de-risk and expedite that process. Others might find that their average time to close is relatively quick, but customers need more support post-sales, where support engineers come into play.
Whatever your combination is, we recommend trying to hire one pod first to support your initial sales hire and see what the sales yield is for that unit after three to four months. If things are working well, and you have the ability to do so, you can hire an entire additional pod, and so on. This allows you to increase your sales capacity and sales productivity quicker than hiring a team rep-by-rep. This approach can dramatically accelerate pipeline and revenue growth, as long as there isn’t a break in the product, process, or pod members that would cause you to pause hiring and triage.
Here are some of the main differences between commercial, mid-market, and enterprise salespeople.
A key aspect of scaling a sales team is being able to speak the same language when qualifying deals and reviewing the team/individual pipeline and forecasts.
Earlier in our design partner article we talked about using the requirements for the gates in the sales process as qualification tools. Now, we'll dive into the default qualification methodology we use at Unusual that’s powered some of the most high-profile and successful B2B IPOs: MEDDPICC. This stands for Metrics, Economic buyer, Decision criteria, Decision process, Paper process, Identify pain, Champions, Competition.
There’s a chance you may have Googled “sales method” or “sales qualification method” which showed tons of frameworks, all slightly different than the other. In the acronym MEDDPICC, each letter simply represents a piece of information you need about an opportunity to determine if it’s qualified (aka real), and if so, how qualified. By capturing the information required by each of these letters, you will not only have a common language internally for how to talk through and evaluate opportunities, but you will also significantly derisk your sales forecast.
Before we dive into each letter, a brief disclaimer: truly mastering a MEDDPICC qualification method is hard. You’ll hear many people say they use this method, but only a select few have truly built it into their sales DNA (mostly from the companies I just mentioned). So, our goal here is to get founders conversant in the method and comfortable enough to start trying it out in your calls with potential design partners and customers.
Metrics: Quantifiable business benefits that your product provides based on past customer success.
Economic buyer: The individual who has the final say on if your product gets adopted, and can allocate budget to do so.
Decision criteria: Formal product requirements that the prospect needs, which will be used to judge all competing solutions.
Prospects process for selecting, evaluating, and purchasing a solution.
Prospects required paperwork (legal, security, new vendor forms, MNDA, etc.) that needs to be completed in order to sign an order form and generate a PO (if required).
The technical and business pain that are driving a new product evaluation and compelling reason to change/buy.
The USER who has access and influence over the economic buyer that sells on your behalf, and has a vested interest in your success.
Competitive strengths, weaknesses, and differentiators between your product and the other solutions being evaluated (including the status quo and homegrown solutions).
An easy way to start capturing this information for each potential design partner or customer is to use a slide like the one shown below (and linked here). This way, when you want to confirm what you’ve learned so far, all the information is in one place to present back to the customer to make sure you understand their situation accurately.
We’ve also created a simple sheet for questions to ask that map to each letter in the MEDDPICC acronym here. So, if we distribute the letters of MEDDPICC over the sales process we outlined, and focus on when we can uncover the required information it would look like this.
Depending on how comfortable you are with the method, you might have more of an even distribution of letters between Discovery and Scope, but the most important thing to note is that every letter of the acronym should be populated and verified by the customer before any formal product evaluation occurs when you’re looking to sell any version that isn’t a freemium or OSS available.
This way, by the time you go into a product evaluation, you already know everything about the opportunity, people involved, competition in the mix, and if your product performs well there should be a high degree of confidence (85%+) that they will close as a design partner or new customer.
The information you have for each letter will enhance after every customer interaction/meeting, so it each aspect will always be influx, but the earlier you start uncovering this information the quicker you can qualify and opportunity in/out, which drastically improves where you spend your time (i.e. only with qualified accounts that have a high propensity to buy).
Continue to: Nurture a self-serve USER/BUYER journey
Installation and usage documentation for the Unusual Ventures Salesforce package.
The Modern GTM
Nurture a self-serve USER/BUYER journey