Chapter 3
Your Sales Process—The Road to Repeatability

Illustration of a framework depicting the four steps involved in the sales process of customer relationship management.

Figure 3.1 Your Sales Process

Process is something that people associate with structure and bureaucracy—but I see it as a liberator and creativity enabler. Why is there such a difference in thought? One of the things that is interesting about process is that, in my opinion, it's meant to create the flywheel for repeatability so that you are free to work on important, high priority, and nonrepeatable “things.”

My third and fourth jobs were as a network administrator. I fell in love with UNIX and the concept of making a world of processes that just worked so that I could focus on the real problems that need a solution. My first business, Net Daemons Associates, was named in support of process. A daemon is a program (kind of) that runs in UNIX whose only purpose is to keep things working. My business partner lived by the philosophy that if you were going to do something more than once, you should write a program for it so that you could just push the button the next time.

Sales is an art and much of it is a formula. There is a beginning a middle and an end to every sale. If you are doing sales correctly, you are using strong brand and messaging which needs to be repeated and amplified so that every person that is being sold is getting the same message. The art is making sure that there is a strong core of process—how do you pitch, what tools do you use, what stories do you tell, what is your pricing, how do you negotiate—with a personal and emotional wrapper that humanizes and engages. If you don't have the process, you will spend less time on that bespoke, emotional element, and, as a result, sell less.

I think one of the most important parts of business is listening. With sales, you need to listen to what your customer is in pain over so that you can propose the right solution for them. You have time to be focused on listening when you have the ordinary and the day-to-day delivered by the engine of process.

Process is a liberator. It lets you put definition and reliability, accountability and efficiency around things that should happen in a repeatable and accountable way and then lets you use the rest of your time to be creative, innovative and work on big picture issues.

—Jenny Lawton, COO Techstars

Why Having and Knowing Your Sales Process Is Important

It took me a little while to get started on writing this chapter. There are a number of reasons for this; first of all, writing (or reading) about process isn't typically very exciting for many founders and sales leaders, who prefer to be in the real world, creating and doing more faster. Process can sometimes feel very boring and tedious (or what big companies do, not startups). I'm personally not one to create process simply for the sake of having a process, however, my experience (and the experience of almost any sales leader in a well-run sales organization) is that one of the keys to selling more faster is a well-defined sales process (Figure 3.1).

The other reason that this chapter took me a little while to get started is because there are so many resources out there already that discuss “the sales process.” If you Google “sales process” there are 2.4 billion results. If you Google “books on sales process,” it narrows your search to 393 million search results.

I don't want to waste your time providing the same information you can get in literally millions of other places; however, I do recognize how crucial your sales process will be to your ability to scale your sales organization and your company. Instead, what we will do in this chapter is to use the work we've done up until this point and start to tease out the first iteration of your sales process.

I also want to stress “first iteration.” Creating your sales process is a lot like being at the beach and digging a hole near the water. Once you hit water in your hole it's nearly impossible to make much progress because the hole keeps filling up with water, caving in the sides, and you don't make nearly as much progress as you think you should. Getting to the point (at some time in the future) where you have a truly repeatable sales process will feel a lot like digging that hole. You'll have many iterations of your process as you learn more about the sale and what is important to your customer relative to your company. You'll have iterations as your product matures and starts to fill in gaps where you previously needed process. And you'll also have iterations as you hire more salespeople and learn how different people and selling styles inform the process. Finally, you'll have sales process iterations as you define (and change) what is important to the company in terms of selling and reporting. This chapter deals only with your first sales process iteration, but without this first iteration you'll have nothing to iterate on (and no path to your repeatable sales process).

Now I realize there are people out there who love and thrive on creating process. If you are one of those people, then this chapter should be a quick read and affirmation to your thinking.

If you aren't a process lover, however, I want you to rest assured that I've done my best to keep this chapter interesting while also giving you very tangible steps to teasing your (first crack at a) sales process out of the work you've done from the book up to this point.

I also want to reiterate that this is not a chapter about “what a sales process is.” While I'll provide you with a simple definition shortly, this chapter is about taking the work from the first few chapters of this book and using it to begin building your sales organization on the road to finding YOUR repeatable sales process. The reason this is important is because without a repeatable sales process, you don't have a repeatable sales process. Yes, you read that correctly, that's not a typo. Stop and think about that for just five seconds.

It is impossible to build a scalable sales organization without a repeatable sales process because there isn't any sale to (knowingly) repeat, which means you don't have a product that can scale to many organizations. You won't be able to hire and retain salespeople because they won't know what it is that they are selling, how to sell it, or to whom. Additionally, having a repeatable sales process gives you the ability to model out sales growth so you know how your hiring will affect revenue and cash burn. And finally, without a repeatable sales process, which enables all of the above, it'll be much harder to win the confidence of your investors (or future investors).

More specifically in this chapter we will discuss two basic methods. First, we will learn how to tease out your (first iteration of your) sales process from the work we did with W3 and through the customer development process. Within that, we'll talk about the importance of a customer relationship management (CRM) system, which I strongly encourage, to make your job easier. Next, we will talk about and start to do some work around sales modeling so that you can begin to put all of this work together and start growing your business. In the final part of this chapter I've included two exercises so that you can build out your sales process and build an early sales model.

Defining the Sales Process

So what is a sales process? A sales process is a repeatable set of steps your sales team takes with a prospect to move them from early stage to a closed customer. A good sales process helps your reps consistently close deals by giving them a framework to follow. Figure 3.2 is a visual representation of a sales process:

Illustration of the sales funnel depicting a list of steps for a successful sales process.

Figure 3.2 Sales Funnel

Source: Courtesy of Austin Dressen.

In Figure 3.2 I've intentionally used the visual of a funnel. The list of “steps” is what's crucial here, but I'm killing two birds with one stone. You see that aside from understanding the steps of your sales process, your sales process will also inform your sales funnel, which are the steps your prospects move from lead to closed customer. In each step some prospects will fall out and others will move on (hence the narrowing funnel). Understanding both why prospects fall out as well as move on is critical to growing your business, coaching your salespeople, and understanding what is working and what is not on your path to building a repeatable sales process.

Seeing the Benefits of a Repeatable Process

I'm on the board of a company called ScaleFactor. ScaleFactor provides automated accounting and bookkeeping services to small and medium businesses. I first invested in ScaleFactor in 2017 when they joined Techstars Austin. At that time, the business looked more like a services business than a software business. They were doing about $1.5 million in revenue and had a loose idea of who they thought their customer was. They had only one salesperson in addition to the CEO. One of ScaleFactor's main goals coming into Techstars Austin was to become a scaleable software company. While in the three-month program, we worked on identifying our W3 and proving it through the customer development process.

Shortly after Techstars, we hired David Loia as our chief revenue officer. He took that initial work and has since developed a highly repeatable sales process, which has resulted in exponential revenue growth. The work we did in Techstars was foundational to attracting David to ScaleFactor because it gave him a decent understanding of what we did, for who and why, which gave him the confidence and understanding to accept the job and start building out the sales organization. I've been extremely impressed with the work David has done at ScaleFactor specially around putting a repeatable sales process in place.

Here is an excerpt from David on what he did and why it proved to be critical to growing ScaleFactors revenue exponentially over the following 18+ months, which has resulted in incredible sales growth as well as raising over $40 million from both Canaan and Bessemer.

It is imperative to reinvigorate the sales process much more frequently than a founder team might realize, and target revenue tipping points roughly on Fibonacci's sequence, that is, $1 million, $2 million, $3 million, $5 million, $8 million, $13 million, and so on.

Nothing that is working well at each revenue tipping point will be sufficient to get you to the next one. Massive change is a constant necessity, all the time, especially at high-growth, since you will be blowing through tipping points every few quarters. The second something starts working, pour gas on it, because you are sure to be changing it for something better.

At pre–$1 million in revenue, founders are immersed in the daily struggle of testing markets and ICPs, honing messaging, building MVP, and generally also doing the prospecting and selling themselves by necessity. When the smolder shows some small flames, the founders proceed to hire some dedicated salespeople to fan the fragile flame. But then, they find that what they learned to get the first $1 million of revenue doesn't work well to get to $3 million, and none of it works at the $5 million tipping point.

David Loia, chief revenue officer at ScaleFactor

Teasing Out Your First Sales Process

In chapter 1 we talked about developing a strategy so that you can start the customer development process. Then in Chapter 2 we took that work and applied it to the customer development process with the goal of being able to move from customer development to sales by firmly identifying our ICP. The other byproduct of the customer development process we haven't discussed yet is the sales process.

My experience has been that, although there are many similarities between sales processes, no two are really alike and it takes a solid customer development process and a clear understanding of your ICP before you can define the process that optimizes for your business.

In this section, we will talk about how to tease out your sale process, through understanding your sales funnel. In that process we will also touch on some basic tools to build and manage your team. Then in the “Building Your Sales Model through (Not) Guessing” section, we will take that information and build an early sales model.

What I avoid as a pro CRO, and you should, too, if you want to scale fast: The “strategy of convenience.” Meaning doing something because it's obvious and easy. It's a method of decision making that is a necessity in the under $1 million tipping point and therefore a darling of many founders.

At later tipping points, however, and especially post A, if the path you're on happens to be the easiest one to execute in the moment (a.k.a. the strategy of convenience), it's probably wrong for high growth. Growth is always hard and high growth takes a lot of hard work plus flawless execution. That's not easy, so the strategy of convenience is likely going to lead you away from high growth, not toward it.

Likewise, how things were at previous tipping points, however nostalgic they might be for the founders, mean little for the new players, whose incremental ideas and efforts are levered exponentially to scale up to future tipping points. Looking backwards distracts from cementing the vision of where the company is going, and the changes that need to be made to get there. Historians inadvertently rally the more tenured teammates against the massive and frequent change that scaling up requires, usually with phraseology like “This is how we did it when we started the company.” Scaling up is about making the new people succeed quickly, never perpetuating the status quo.

—David Loia, chief revenue officer at ScaleFactor

Focusing on Your Sales Funnel

Let's start with your sales funnel. If you ask most businesspeople, they will tell you that the sales funnel is simply a list of companies you think will become customers and where they are in the process. This simply is not true; the real answer is much deeper than that.

I think about the sales funnel as a visual representation of your sales process that tells you what work you need to do in order to drive revenue, as well as the priority and importance of that work. A great funnel tells you not only the stage a given prospect is in your process but also who you need to be talking to (inside and outside the company), the materials you need to be preparing, the questions you need to be asking, what you need to do to close the deal and the things you need to know to keep your customer satisfied and delighted after the sale is closed.

When you first kick off your customer development process it's pretty hard to have any idea of your sales process or what your funnel will look like. What I usually tell people is to pick four to six stages that feel right and just start tracking and recording data. Some common first-pass stages are:

  • Lead > First Contact > Demo > Proposal > Negotiation > Close

From a nomenclature perspective, something like that might always be your stage names but what changes is what you learn and know about each stage. It's also common to add/change/delete some of this as you learn more about your actual process.

For example, let's use the negotiation stage. For a simple sale (or B2C sale), negotiation may not be a stage because there is nothing to negotiate. For a slightly more complex product or selling to a midmarket customer, you may need some simple negotiating with your business buyer and you may need to build tools and rules for your salespeople to follow so they are empowered to close business or you may decide that you always bring in a manager for negotiating. Then on a more complex sale, and especially if selling to an enterprise, there is also a procurement process that often restarts some (or all) of the negotiation and may bring up new points, which may change who on your team works with each person at your prospects company (including bringing lawyers in). Depending on how you define your stages, this may be part of the negotiation stage or a stage all by itself. As you can see, with this one stage, negotiation, we've defined several different ways to think about it that will dictate the process you build out.

Each one of these stages is not just a simple word, but think about each as a more complex concept of where your prospect is in your funnel, For example, let's look at another company in my portfolio, Allstacks.

Allstacks: Finding the Right Sales Process

Allstacks is a data and analytics platform for developers (and their managers) to understand the data and metrics behind their development process. In other words, similar to Sales or Marketing, Allstacks gives companies insight into how their development projects are moving through their development cycles.

When Allstacks joined Techstars Austin in January 2018, they had about a dozen (early) customers and defined their sales process as

  • Lead > Demo > Customer

When I look at that funnel, it tells me:

  1. Identify a company as a good lead.
  2. Give a demo of their product.
  3. Win or lose that prospect as a customer.

What it does not tell me is:

  1. 1a. Whether there is a difference between lead types.
  2. 1b. How a prospect moves from lead to a demo.
  3. 1c. Anything about lead types.

It also doesn't tell me:

  1. 2a. What happens after a demo to move a prospect along.
  2. 2b. What happens if the prospect says no during the demo.

And while there might be something nice about such a simple funnel it doesn't answer any of the questions along the way as to why your prospect is or isn't progressing through your funnel.

Here Hersh, CEO of Allstacks, is telling you firsthand about his experience figuring out their funnel:

When we first started Allstacks we agonized over forming the sales funnel. What stages should we have? How should they be defined? Why do they matter? We had a ton of questions and were struggling to find answers. Being engineers, we had a certain disconnect with the sales process. The big learning was when we realized the sales process was more about throughput than any particular deal. It was tough to reconcile against software development because you can't just say as long as 15% of the features we define at the top of the funnel (“prospects”) get completed and delivered (“closed won”) the software will work. The particular features matter a lot.

With sales, we realized the buyers within our target persona were substantially equivalent so we needed to optimize our conversion through the sales funnel.

Still armed with a litany of questions in hand, we decided the best thing to do was simply embrace the questions and define our sales funnel stages as a series of questions. What do we need to ask to determine why a buyer makes it to the next phase? As we answered each successive question it revealed the next set of questions we needed to answer to build our sales funnel. Eventually, all of the questions had been answered and we knew where to focus. At a high level the questions started out quite simply:

  1. Will anyone respond to us?

    We had acquired a list of leads so we segmented the list, and tried different value propositions against them. Eventually, we found one that worked for us and we started to engage our prospects. Interestingly enough, it had little to do pushing a value proposition and everything to do with engaging a human. We asked, “What is a metric that you care about measuring for your software team?” This led to a massive increase in conversion to the next question:

  2. Will anyone take a demo?

    This question was fairly easily to validate. Once we were successfully able to engage our customers as a result of answering question 1, the demo came fairly quickly, our buyer persona was curious and always wanted to see the product. However, once in a demo, where to go from there? This led to our first diverging path. A lot of the buyers asked for access to a demo account or a free trial. What we found, consistently, is that the demo account fell flat and killed enthusiasm. The learning was that buyers had to see their own data in Allstacks, not dummy data. So we went onwards.

  3. Will they sign up for a trial?

    Luckily, in the mid-market buyer development and analytics tool space, this was pretty table stakes. Everyone expected a trial, however—

  4. Will they convert to paid?

    This was the tricky part. Wherever you can, the recommendation is always, don't give out free trials. This becomes challenging when buyers have been trained by the market to purchase in a certain way, as we experienced. So we had to search for the magic moment when a series of actions taken within Allstacks led to teams using the product consistently, and Allstacks became sticky. For us, when teams use Allstacks to drive their daily standups and run their retrospectives we achieve that magic moment. Guiding our buyers through that process helps drive our conversion.

    By defining our sales funnel as a series of questions we were able to understand where we had uncertainty. Anytime we couldn't answer a question we knew we were lacking data and needed to become more granular on the questions we were asking. This helped us tailor a sales funnel tightly to a critical path we knew worked for us without trying to arbitrarily match a generic funnel to our sales motion.

Hersh Tapadia, CEO of Allstacks

Working with Hersh was a great example of figuring out and understanding the sales process. First of all, Hersh was a developer at heart so he openly welcomed the concept of a process. Not to mention there is a direct correlation between the sales process (and need for it) with Allstacks and what he was building for developers. Figuring out and focusing on what the Allstacks process should be helped him think about how to develop the Allstacks product as well. Now, almost a year later and with a more mature process, their sales numbers are several orders of magnitude greater, they have better insight into who is a real prospect in their funnel, how long that sale will take to close, and how much they can expect from each sale. Not only does this give Hersh and the team confidence about growing the business (and future hiring), it gave potential investors the confidence in Hersh, the team, and the process to invest into a very healthy seed round (giving Hersh and team more financial ability to execute and sell more faster).

Using a CRM to Track Customers and Data

Okay, so let's go back to the beginning—what are the steps you think you'll need to go through to close a sale, then start tracking and recording data? What I mean by this is that you'll want to start tracking, at minimum,

  1. The number of prospects in any given stage.
  2. The time a prospect sits in any given stage/how long it takes to move from stage to stage.
  3. What needs to happen in any stage for that prospect to move to the next stage?
  4. Why prospects move (or don't move) from stage to stage.
  5. Proposed revenue before a prospect becomes a customer versus revenue once that prospect becomes a customer.
  6. The win/lose rate at each stage.

In order to do this well, most people (and I) highly recommend a customer relationship management (CRM) system. If you aren't already familiar, a CRM is a software tool used by most companies to track the entire lifespan of their customers (from prospect through the day when they no longer want to be a customer and become a prospect again). While using a spreadsheet can work in the earliest days, it very quickly ages, doesn't provide a good ability to track data or build reports and it doesn't scale as you add people.

At a minimum I'd start with something like Streak or Freecrm.com. There are tons and tons of CRMs out there. The most common is Salesforce.com, which is a very powerful CRM but can also work well for early stage companies. The two challenges I have with Salesforce are cost and complexity. It's a lot of work for an early stage company just trying to figure out who they are.

At Techstars Austin, we currently use Airtable. Upon writing this chapter, we've only used it for about a year but I love it because it's easy to customize, very flexible and easily allows for both multiple customer types (great when you are learning or more mature) and making changes to process and flow on the fly. If you do not already have a CRM you like, I would recommend trying Airtable. If there is already a CRM you've used in the past and like, just use that one. There isn't really a wrong answer here, other than to not use one at all.

Once you pick a CRM, set aside half a day or so and set up the first iteration of what you think your process will be—think of this as your V1, just like in the software development process. Take the time to think through how you will be using it. Here is a quick step by step to get you started. Keep in mind both that this process will evolve over time and that the process for your company will be different than most other businesses out there.

Step 1: Prospect Types

If you think you might have different prospect or customer types, then try to take this into account from the beginning. Different types could be enterprise customers, medium-sized businesses, or resellers. It could also be industry specific.

Step 2: Steps

Add in all the steps you believe you need to track, based on what you currently know about your sales process. If you aren't sure where to start, then you can use my example (Lead > First Contact > Demo > Proposal > Negotiation > Close). Make sure you have a definition (ideally in your CRM, for all to see) of what each step means to your company.

Step 3: Reporting

Set up some basic reporting on what you currently think you need to be tracking. Some common items are: projected sales revenue by month and quarter and weighted based on stage, time for prospects to move from stage to stage, stalled prospects, closed win/lose report. Note: This is one step you can punt on for a few weeks if this is out of your comfort zone. I'll cover this in “Evaluating Progress” section.

Step 4: Use It

This is the most important step—use it! Set an example for the entire company. The earlier and more accurately you have this information, the better positioned you are to sell more faster and communicate with your company, customers, and investors.

* * *

One important note to keep in mind for setting up your CRM: when you set up fields for collecting data, think about what needs to be free form versus what data needs to be cleaner data (i.e. choices) when you collect it. The more you can have defined fields, the easier it will be for you to understand the data and make projections; however, sometimes you need some free-form fields to record, for example, why someone has decided to buy or not to buy your product. You don't likely have enough information yet to formalize the “why,” so collect it free form and then in time change it to an option field once you have enough data to understand why.

Once you do this, you probably don't need to check in on your process more often than quarterly or whenever you learn something substantially new and obvious that needs to be added. Finally the most important thing, which I will say again: use it! Be diligent about taking notes and updating statuses. It takes a little work to build this muscle, but it will pay off in dividends because, aside from the great data you will have, it builds it into your culture from day one.

Evaluating Progress

Okay, so you've set up your CRM and started inputting data. Maybe you even have a couple of other people calling customers. After about three to six weeks, set aside half a day to think about and build out your first set of reports. Think about what you've personally learned about the prospects you've been calling, how they are moving through the funnel, and take your first stab at the data that you believe are the biggest indicators of learning how to close business. Then pick three to five metrics at maximum. These will be your first set of sales key performance indicators (KPIs). (Note: Keep in mind that this is different than your business KPIs; only one or two of these will likely be part of those KPIs).

Once you have your sales KPIs, it's time to create a weekly meeting with the key internal folks. At a later stage company, this is likely a manager and teams, separate managers and directors and VPs and up to CEO. At an early stage company, the CEO is likely one of the people (or the only person) doing customer development. It's still crucial to meet with key stakeholders, both to share learning and also to assign accountability. If you are super early and there are only a few people in your company, then invite everyone, including your developers, so they have visibility into what you are doing and how your mutual work impacts each other's ability to be more successful. There isn't really a wrong group of people here to be included, with the caveat that each person should understand how their work mutually impacts the other's. Groups can get too big, so as your company grows, try to limit the meeting only to key stakeholders as time goes on though I encourage you to share pipelines openly so anyone in the company can see progress.

Building Your Sales Model through (Not) Guessing

As an entrepreneur I was always comfortable with uncertainty and always felt that it was a necessary trait of a successful founder. But I now realize that while it is impossible to plan the trajectory of an early stage company, that you can remove a lot of uncertainty with a great financial model.

Let me be specific. I am not talking about “projections”: the only thing we know for sure about projections is that they are wrong. I am talking about a bottoms-up financial model that has assumptions as inputs and attempts to create a mathematical representation of how your business works. If each sales rep can make X calls and close Y percent of them, then if you know the number of reps you have each month and the size of the average sale, you can calculate the sales, salaries, and commissions fairly accurately.

If you want more sales, then you need more reps. In this model will come more expenses and more revenue—it represents what actually will happen. Contrast that with a “model” that just shows a consistent rate of growth (10 percent month over month, for example), but does not account for any of the expenses or work that it takes to get that growth.

Once you have a model, you should update it each month, updating your assumptions first to reflect reality more closely and then tweak the formulas if you need to make it even more accurate going forward. If you do this consistently it is almost like having a crystal ball into your business's future.

—Troy Henikoff, managing director, MATH Venture Partners

The final part of this chapter is building an early sales model. A sales model is a general framework that defines an organization's high-level approach to selling and is a mathematical representation of what you project your sales to be using historical data layered with future/new expectations (ideally also based on data).

You likely don't have nearly enough data to fully understand the sales process and typical sales cycle, much less to create meaningful long-term revenue projections. That being said, now is the time to build discipline around being a metrics-driven sales organization. This is important for several reasons, for one creating that culture early on helps with hiring, training, and growing your sales organization. Another reason is that as you grow, your current and future investors and advisors will need this information to understand how they can be helpful and when to invest (more) money. The more you understand your process and can talk to your sales funnel that is backed up with data, the more confidence you build with them for future support. Finally and most important, it's the blueprint for how you will run your business so that you have a deep understanding of how to grow and make money.

In the previous section we mention that many startup people don't love process; likewise, most startup founders or sales leaders would like to avoid building sales models. That said, at the end of the day every business is a math equation and the best founders and sales leaders I know have all developed (if they didn't already have it) a love/hate relationship with digging in and building their own models. Over time as your company grows, you'll likely have staff to help with this task, but early on I believe it is critical for each department head to build their own models because it both forces and demonstrates a deep understanding of what is happening in your department and helps instruct the rest of the company on how to work together to grow.

Early modeling shouldn't be hard, especially if you've done the work to create a meaningful sales funnel that you follow in your CRM. Everything around modeling in this part going forward assumes you've done that work.

So let's get to it. Your company's size and how many customers you currently have will largely dictate the complexity and accuracy of your model. While you do want to be as complete and accurate as possible, it's more important to distinguish between what you know as fact (using data) and what you believe to be true (labeled as assumptions).

Let's step back and look at everything we've discussed so far. This is all the information you have, so far, that will help you develop your sales model.

First let's start with W3 and the customer development process. By now you should have a directional idea of who your customers will be and a very early idea of your sales process. Also, it should be pretty easy to identify all your expenses associated directly with sales. This includes ongoing costs like salary commission, materials, and potential travel and one-time costs like a computer. That is all the information you need to build the first pass on your first sales model.

For those of you who have never built a model before, here are some tips:

  1. Even if you are not familiar with using formulas, the ones you'll need for this first model will be pretty simple. Wherever you are doing any math (within or between cells), take the time to learn how to use formulas. We won't go into this here, but between tutorials in any spreadsheet and Google, it should be pretty easy to figure out.
  2. Next, build out models by month. Your columns will be months while your revenue and expense drivers will be in rows. Start by building out two years, but also know that each month further out will be less and less accurate, because we simply don't have enough information yet. The purpose here is not for accurate projections, but to build a model we can start tracking against to help us learn how to more accurately project in the future. The reason I say two years (versus one or three or more) at this early stage is simply because of the discipline in thinking into the future. Anything beyond two years (and really even just one year) is just a guess, but the mental exercise of starting to think about the future is what we're looking for here.
  3. Then, lay out your framework on a spreadsheet. Label the months (starting at column B or C) at the top, then down column A put in what your revenue drivers are, followed by a line break and then your expense drivers. These are just the labels, the data will go in the cells by month.
  4. Finally, make a pot of coffee, carve out four hours where you won't be interrupted, and get to work. Expect that you may have a couple of false starts (especially if you don't build models all the time). Don't let those frustrate you, they are a crucial part of the process in learning and figuring out how to actually manage your business.

At SurePayroll we had originally used benchmarks from Paychex, a public company that was also targeting small businesses, to drive many of our assumptions. One of the key assumptions is the number of employees per client company. You charge on a per employee basis, and so larger companies meant more revenue. We looked at the data from Paychex and assumed our average client would have 14 employees. It seemed appropriate.

As we started operating and building out client base, it quickly became apparent that our clients were skewing smaller, averaging just over six employees each. When we first realized this, we thought we were done. Revenue would be a fraction of what we had predicted and we would have trouble making ends meet. But, since we had a detailed, bottoms-up financial model, we were able to update the assumption for the average number of employees per client to 6.5 and immediately see exactly how revenue and expenses were impacted.

Sure, we had less revenue, but we also had lower expenses—fewer ACH fees, less customer support, and so on. In the end, the financial model gave us the confidence that in spite of the fact that reality was less than half of what we had initially predicted, that we still had a viable business, and we pushed forward. Ironically, 10 years later Paychex acquired SurePayroll for well over $100 million, and it became their solution of choice for the small end of the SMB market.

—Troy Henikoff, managing director, MATH Venture Partners

Your CRM Blueprint and Early Sales Model

There are two exercises for this section. The first is quick and is around building your first sales funnel and the first stab at your sales process. The second is building your first model. You won't be able to do this until you've completed the first exercise (and likely for a few weeks after).

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.133.109.211