Sign up for our newsletter.

times popup
Apply to PearX

Blog and/or Founders Guide: Founders Guide

Debunking common myths: what technical founders need to know about sales

Posted on by jill

As a technical founder, you’re no stranger to challenging assumptions and pushing boundaries. Yet, when it comes to sales, many technical founders fall prey to common myths and misconceptions about sales that can hinder their startup’s growth. Let’s debunk these myths and uncover the truth about sales:

1. Myth: A Good Product Will Sell Itself, so I don’t need to worry about sales: Especially from a technical point of view, it’s easy to believe that if you’ve built a great product, customers will come flocking. While a strong product is undoubtedly essential, it’s not enough to guarantee success. In reality, ideas are cheap, and execution is critical. Competitors will inevitably emerge, and without a solid sales strategy, your product will get lost in the noise– even if it’s better than the alternatives. Early sales are crucial for validating your idea, learning how to talk about it and gaining traction in the market. 

2. Myth: I Can’t Sell Because I’m Not “Salesy”: Many technical founders shy away from sales, believing it’s a skill reserved for natural-born salespeople. However, this couldn’t be further from the truth. In Geoffrey Moore’s “Crossing the Chasm,” he highlights the importance of early sales to tech enthusiasts – a group that technical founders are uniquely positioned to identify with and sell to. Your deep understanding of the product and its technical intricacies can be a powerful asset in connecting with early adopters. Sales isn’t about being pushy or overly charismatic; it’s about building relationships and solving problems. 

3. Myth: Sales Is a Necessary Evil: Some technical founders view sales as a necessary evil – something to be delegated while they focus on building a product-centered company. However, the best businesses understand that success lies in being customer-centric from the get-go. Sales and technical teams should work hand in hand throughout the lifetime of the company, both driven by a shared commitment to delivering value to customers. Interweaving the shared success of both teams early on fosters collaboration and ensures that the customer remains at the heart of every decision. Ultimately, the most successful companies recognize and appreciate the unique contributions that both technical and sales teams bring to the table.

This image has an empty alt attribute; its file name is Startup-success-requires-the-founder-to-be-the-bridge-between-the-technical-and-sales-sides-of-the-org-Medium-Banner-US-Landscape-1024x512.png

Technical founders must challenge traditional myths about the sales profession and recognize the pivotal role that sales will play in their startup’s success. A great product is just the beginning – it’s how you sell it that sets you apart. Embrace sales as a strategic imperative, leverage your technical expertise to connect with early adopters, and build a customer-centric organization from day one. By doing so, you’ll pave the way for sustainable growth and lasting success.

Want to know more about leading GTM as a technical founder? Check out our additional resources for technical founders here. 

Minimum Fundable Team: how early team shapes seed fundraising

Posted on by jill

My role at Pear is to directly support pre-seed founders that participate in PearX with their hiring needs. PearX is our hands-on, 14-week bootcamp designed to position founders to raise seed rounds from top tier investors. We’re experts at helping companies raise this capital; over 90% of PearX companies go on to raise capital from top investors.

We have found, that at early stage, the four largest themes driving an investor’s decision to invest in a company are:

  • Market
  • Product
  • Traction
  • Team

To successfully raise capital, you need all four to be great OR one or two to be exceptional. 

However, at pre-seed in particular, markets are difficult to size and product or traction are often still too early to measure with a high degree of conviction. For these reasons, investors will often place an outsized emphasis on the quality and completeness of the team when making an investment decision.

At Pear, we refer to the completeness of a team at this stage as Minimum Fundable Team or MFT.

Prior to raising a pre-seed or seed round, founders should ensure their MFT is a competitive advantage. We suggest that all founders ask the following three simple questions to determine the completeness of their team prior to raising:

1. Is someone on the team a deep subject matter expert with the market or product you’re building?
2. Has someone on the team built a successful product from zero? 
3. Do you have the right mix of skills across the team required to ship a quality product quickly? 

If the answer to any of the questions above is no, what steps need to be taken to fill in any gaps to achieve MFT? 

We believe that hiring is one of the best ways to do this quickly. 

One of the advantages of joining PearX is that helping founders achieve MFT is a core part of our offering. Over the last 12 months, I have worked with 30 different teams and helped fill over 25 roles. Each of these hires have played a critical role in helping those teams reach MFT and close a successful round of funding. 

If you take away one learning from this article, it’s that hiring plays one of the most critical roles in early stage fundraising. Founders who achieve MFT prior to fundraising will have a higher likelihood of success compared to those who don’t.

Building an effective sales strategy: Part 3 – Crafting the perfect customer pitch

Posted on by adam

Pear’s Partner, Pepe Agell, learned the importance of mastering sales during his entrepreneurial journey with Chartboost, a mobile advertising company. Pepe led Chartboost and built sales and go-to-market strategy for the company from its earliest days to its acquisition by Zynga in 2021. He is now a Partner at Pear VC, based in Barcelona and focused on Pear Europe.

This is the third part of our three-part series on building an effective sales strategy, focused on three essential stages of the sales process founders need to master. Before diving into part two, don’t miss part one and part two!

Now that you’ve learned how to run your client meetings effectively, let’s talk about how to construct the perfect sales pitch.

One of the most common mistakes I see is that sales people will often launch into the finer details of the product offering without sharing the bigger vision first and the impact that the solution can have in the customer’s life. Here is how I recommend structuring your pitch to most effectively close deals:

1. When pitching to a client, start with the why before focusing on the how or what.

After you gather as much information as possible from your client, you are ready to pitch your product. I like to follow the why, how, what method.

Simon Sinek has a well-known TED talk all about how great leaders talk about their products by leading with the why. I go back to this TED talk all the time, and I’ve found that the same framework can be applied in sales when talking to clients about your product or solution.

Why: You should lead with a strong explanation of why your solution is the best for the customer. This can include who you are, what is happening in the market, the challenges you’re solving for, and why the customer should listen to you.

Example of a strong why statement: “After watching my dad go through diabetes and battle with insurance companies to get the treatment he needed, I was compelled to start a company that made it easier for elderly adults to navigate the health care system. I found that I had to be my dad’s advocate, calling and negotiating on his behalf, and I realized that not every older adult had that same support system.”

How: Next you can explain how you’re solving the problem the customer has, what your approach is, and some of the details about the product.

Example of a strong how statement: “We decided to build a marketplace where patients could easily onboard their medical information and get paired with the most suitable insurance provider in just few minutes.”

What: Finally you can dive into the what, really explaining what benefit your customers will receive with your help (revenue growth, etc.) and the specific features you offer.

Example of a strong what statement: “For every patient request we get on the platform, we process thousands of insurance quotes and select the most appropriate one for each case. We manage the contractual process, payments and medical claims. All in one mobile app.”

2. Get to a demo as quickly as possible.

Product demos help clients picture your solution in their daily workflows. It is also a clear way of visualizing how are you really solving their problems. From my experience, aha moments and even wow moments in a sales pitch happen during the course of the demo, not while going through slides. That’s why, I strongly recommend to get to the demo part as quickly as possible.

3. While explaining your product to the client, integrate your client into the story.

Slides need to connect to each other through an overarching narrative or story. It’s also important to bring your client along on the journey.

I’ve seen many salespeople feature the client’s logo on the opening slide. That’s great, but it’s much more impactful if you bring the client into your entire story. You can feature pictures of their products, their people, and statements they’ve made. Don’t forget to clearly explain what’s it in for that particular customer or for similar companies that are already working with you (see next point). Remember that your clients don’t care about your product features but the impact that you will have in their day to day.

4. Show proof of benefits from other clients.

I’ve found that it helps to share how other clients have found success with your product, but I recommend talking from a client’s perspective.

Instead of saying: “Our product is really strong at automation, and that’s why clients go with us.”

Try something like: “Clients in a similar growth phase experienced exactly the same pain points, but by implementing our automation tools, they were able to become 50% more efficient.”

5. Explain the next steps and how to get there.

Make sure you clearly explain the onboarding process, using screen shots where necessary, so the clients can really grasp what onboarding your product actually looks like. You should clearly explain how long it will take for the client to go live with your product. Also, if you haven’t already discussed pricing, make sure you do that before you wrap up.

6. Engage your audience meaningfully.

During the sales pitch you shouldn’t just ask “Any questions?” Instead, you’ll get more engagement if you ask meaningful questions like “Does this resonate with you?” or “Do you experience something similar?”

To sum it up, all founders have to implement a successful sales strategy in order to truly succeed. These are the best strategies I’ve developed while building and leading sales teams across regions. I hope they help you be more effective in getting new customers and growing revenue. And remember that “when the pressure is on, you don’t rise to the occasion. You fall to the highest level of preparation.”

This is part three in our series on sales!

If you’re interested in hearing more Pear news and seeing more posts like this, please subscribe in the footer below. We won’t spam you, and it’s easy to unsubscribe at anytime.

Building an effective sales strategy: Part 2 – Preparing for a customer meeting and leading it effectively

Posted on by adam

Pear’s Partner, Pepe Agell, learned the importance of mastering sales during his entrepreneurial journey with Chartboost, a mobile advertising company. Pepe led Chartboost and built sales and go-to-market strategy for the company from its earliest days to its acquisition by Zynga in 2021. He is now a Partner at Pear VC, based in Barcelona and focused on Pear Europe.

This is the second part of our three-part series on building an effective sales strategy, focused on three essential stages of the sales process that founders need to master. Before diving into part two, don’t miss part one!

Once your outbound sales efforts have been successful, it’s time to prepare for the meeting and lead it effectively. That starts with thinking carefully about how to use the short amount of time that you have with a client. My suggestion is to allocate your time according to the Pear Guide for Sales Meetings.

The Pear Guide for Sales Meetings

Now let’s double click into some of these steps. Here are a few of the strategies I find effective:

1. Before you even meet with the client, try to diagnose their needs, priorities, and budget. This will set you up for success in the meeting.

Aim to walk into the meeting with a solid understanding of the client’s needs. This will allow you to better understand the opportunities that exist within the company you’re selling to. Specifically, you should:

Learn the basics of the company: make sure to look at the company’s website, Crunchbase profile, and social media pages like LinkedIn, Youtube, and Twitter to understand the stage of growth and number of employees.

Assess the client’s strengths, problems, and pain points: take their products for a spin so you can understand the benefits and challenges first hand. Try to assess how your product could add value to what they’re already doing. If it’s a larger public company that you’re selling to, you should listen to their earnings call or read their investor relations report to learn about the company first-hand from its leadership.

Determine whether it would be beneficial to add a C-level team member in the meeting: as you grow, you can leverage the meeting opportunity to include a VP or C-level executive from your side. This might push the client to include an executive or ultimate decision maker from their side as well, making it easier to close the deal.

2. Set yourself up for success before a virtual meeting begins.

Test the Zoom or Google Meet settings 5 minutes before the call begins. Make sure to setup your tabs for the meeting and turn off all notifications on your phone. You should send a courtesy email with a reminder of the dial-in information. And finally, make sure to send any relevant documents or materials to attendees ahead of time.

3. Kickoff the meeting with introductions and take some time to connect personally with attendees.

It’s a good idea to hop on a little early and make small talk with attendees as they’re logging on. Having a good rapport with your clients can go a long way in relationship building.

Once everyone logs on, introduce yourself properly and let others on the call introduce themselves. You should quickly verify the end time of the meeting so you can pace the meeting appropriately.

From there, I advise going through the agenda and sharing your top-line goals with the clients. You should also inquire about any goals they might have for the meeting. This is an important step, but I wouldn’t spend more than 2-3 minutes in total on this. Then dive in!

4. Discover and learn by using the SPIN method to uncover what the client’s true needs are.

Now that you’ve learned as much information as possible about the client and their needs ahead of time, you can put your best foot forward in the meeting. I like to follow the SPIN method to lead a client meeting.

The acronym SPIN refers to the four types of questions that guide sales conversations: Situation, Problem, Implication and Need. You want to breeze through the S and P questions, and really focus on the I and N questions to get the most out of your meeting.

S: Situation Questions – these questions help you understand the basic facts around the client. In my experience, the questions that fall into this category add very little value to a meeting, and most of these questions can be answered in your own background research ahead of time. My advice is to spend as little time as possible here. Example of a situation question: “How many people do you have on your team?”

P: Problem Questions – rather than focusing on situation questions for a long time, you want to jump into problem questions as soon as possible. Problem questions probe clients on the challenges they’re facing in their day to day and with their current product solution, if they have one. You should be careful not to offend the client, in case they were the one who previously decided on the tool or service being used. Example of a problem question: “What are you missing most in your current solution? Does your current tool ever fail?”

I: Implication Questions – after assessing the problems the team is having, you can really dig into the implications and consequences of those problems on their business. This helps to demonstrate why they need to make a change. Example of an implication question: “What’s the productivity cost when the solution fails? ”

N: Need Questions – these questions are designed to uncover the core needs of the prospective client, the benefits they are looking for out of their next solution, and to guide the client to see the benefit of your product or service as a better solution. Example of a need question: “Wouldn’t it be simpler if the process were automated?”

5. Summarize the learnings and then dive into a demo to share information about your company.

Quickly read back what you heard from the client. Example of a read back: “To make sure that I captured your needs correctly, you are currently missing an automated solution?”

From there, it’s time to dive into your presentation of your company. Share your screen and give a demo to your clients, if possible. Throughout the demo, you can link back to the client’s needs. Example of this: “To your point that productivity costs are high, we believed in keeping costs low by [XYZ solution].”

It also helps to share use cases and case studies of other companies and how they found success with your product.

6. Leave time for answering the client’s questions and to do a proper close.

Summarize your findings and some key points. I find a three-point summary works great, but I try to never make it longer than three points.

Thank everyone for their time, and follow up on next steps. Try to have concrete next steps, and again, no more than three.

You should verify that all goals were met and that the clients don’t have any outstanding questions about the product. Log off the meeting (and make sure everything is logged off, like screen sharing).

7. Send a quick follow up note.

After a sales pitch, schedule a few minutes on your calendar to send follow up notes. I recommend make it a bit fun and memorable (i.e. add a picture of the meeting, or your team using the customer’s product…). Don’t let perfect be the enemy of good – timeliness matters, and it’s better to send a good follow up email quickly vs. a perfect follow up email a week later.

Make sure you also save some time to debrief with team members on your side to plan next steps.

In conclusion, you want to be prepared walking into a client meeting, and you should be extremely thoughtful on how you spend your time in the meeting itself. In part three of this series, we’ll dive deeper into how to craft the perfect sales pitch.

This is part two of a three part series on sales. Stay tuned for more!

If you’re interested in hearing more Pear news and seeing more posts like this, please subscribe in the footer below. We won’t spam you, and it’s easy to unsubscribe at anytime.

Building an effective sales strategy for startups: Part 1 – Mastering a customer-centric sales approach and outreach strategy

Posted on by adam

Pear’s Partner, Pepe Agell, learned the importance of mastering sales during his entrepreneurial journey with Chartboost, a mobile advertising company. Pepe led Chartboost and built sales and go-to-market strategy for the company from its earliest days to its acquisition by Zynga in 2021. He is now a Partner at Pear VC, based in Barcelona and focused on Pear Europe.

One of the biggest obstacles founders face early in their journeys is building a successful sales strategy. To take your company from 0 to 1 requires putting the customer at the center of what you do and building momentum in sales and product adoption. Whether they like it or not, founders are forced to wear a salesperson hat. To make their job easier, I’m excited to share a few of the lessons I learned over my decade leading sales for Chartboost.

1. Think about the Law of 250 to remember that each and every interaction with a prospective client is critical.

Joe Girard is acknowledged as the world’s greatest salesman, and he famously coined the Law of 250, which he believed to be the radius of influence for an average person.

The basic principle is that if you do a crummy job of selling your product, you could potentially lose 250 more customers. If you do a great job, you could potentially gain 250 more customers.

You might only get one shot to make an impression, so you have to prepare yourself for each and every interaction you have with a prospective customer.

2. Remember that HOW you sell is as much of a differentiator as WHAT you sell.

Founders focus on perfecting their product and service offerings for good reason – it’s critical to success. But, in my experience, founders often don’t carve out enough time for getting to know their target customers and crafting a sales strategy that reaches the right people in the right way.

The more you know about a client, the more leverage you have. The key to learning more is to research your clients, identify what they need to achieve, understand the impact your product or service can have on their business, and then engage your clients in a meaningful way.

3. Adopt a customer-centric sales approach every step of the way: don’t simply sell your products and features, sell the impact your product will have on helping your customer’s business improve.

Try to understand what is going on inside your client’s organization: What are their objectives? What are their obstacles? What stage of the journey are your clients on?

This can be easier said than done, so I like to break down this customer-centric sales approach into 4 buckets, which I call the 4 D’s:

Discovery: research and prepare for client interactions

Diagnose: identify where the areas of opportunity exist within the client’s organization

Design: create a proposal with the pitch tailored to the solutions your client needs

Deliver: clearly share your vision and close the deal

4. We operate in a social world. Put your best foot forward online.

First impressions matter. Your clients are very likely to look up your online profiles, so make sure you are building your online presence in a professional and clear way. Consider updating your LinkedIn profile with an updated photo (professional and smiling), a tagline or title that captures what you are passionate about, and share a clear blurb about your company story and what you’re trying to achieve. Put simply, don’t make a prospective client dig for information about what you’re selling, but rather make it easy to access and understand.

Establish contact with prospective clients. Don’t connect on LinkedIn blindly, but instead, send a quick note with context to make a connection. If you have a mutual contact with a strong connection with a potential client, you can ask for an introduction. Alternatively, you could just reach out and mention the common connection without directly asking that person for an introduction. These tactics boost the chances that the client will respond or accept your invitation to connect.

5. Be really thoughtful about how to structure your outbound messages and emails: aim to be clear, concise, and personal.

The shorter the email, the better. My rule of thumb is for a email to take no more than 30 seconds to read. If you can get your message across in 15 seconds, that’s even better.

In terms of what to say in the email, I suggest following the 3 R’s method to construct your outreach message:

Research: share more about what you learned in your research. Example: I can imagine you’re very busy right now with the success of your current [XYZ product] hitting the market.

Reference: reference an existing client or situation that relates to them, or something else. Example: We have several tools that might be helpful to you as you continue to scale [XYZ product] offering.

Request: state a clear request at the end: a meeting, a call, or whatever your hope to do. Example: Let me know if you are free tomorrow to discuss more.

6. Don’t overlook the importance of the sales meeting calendar invite. The invite itself is a powerful sales tool.

Once your client agrees to chat more, you have to get to work on making the best first impression. Creating a quality meeting invitation sets the tone for the meeting and creates brand awareness for your company. To put your best foot forward in the invite: state a goal of the meeting, add any relevant context, share any useful resources (example: a one pager of the product you’ll be pitching), include dial in information (and test out the dial in 5 minutes before the meeting begins), and include a backup phone number in case the dial in fails.

Your client may accept the invitation and add other team members to the invite. This will give you an opportunity to do some background research prior to the meeting to better understand who is on the team and who the decision makers in the room might be.

Carefully and thoughtfully compiling the invite will allow you to build brand awareness and create understanding and camaraderie, before even have your first meeting.

7. Prepare. Prepare. Prepare.

I’ve mentioned this already, but it’s worth underlining. I can’t emphasize enough the importance of preparation in the sales outreach process. You never want to wing an interaction with a client. The more you know about who you’re talking to, the clients vision and strategy, and the size of the opportunity, the more successful you’ll be.

In conclusion, these seven concrete steps can help you to become more customer-centric in your sales approach and outreach strategy. This is just the beginning of what you need to do to be successful on your sales journey.

In part two, you’ll build on the lessons you learned in part one, and we’ll move into the phase of the sales process where you’ll learn how to prepare for a customer meeting and effectively lead the meeting.

This is part one of a three part series on sales. Stay tuned for more!

If you’re interested in hearing more Pear news and seeing more posts like this, please subscribe in the footer below. We won’t spam you, and it’s easy to unsubscribe at anytime.

Market Sizing Guide

Posted on by adam

A startup’s potential scale is bound by its future market size, and consequently “what is your market size?” is one of the determining questions that most VCs ask early stage entrepreneurs.

Why does market size matter? 
How to estimate your market size? 
What is the exact definition of market size? 
When should market size be estimated for? 

If you only take a few things from this article: 

  • Big companies can only exist in big markets. 
  • Estimate market size using a bottom-up approach not top-down. In other words, multiply the number of customers by the average revenue per customer per year (which you can estimate through multiplying transaction volume by price).
  • Present your total addressable market and your future revenue for 5+ years into the future. 

At Pear we consider an entrepreneur’s clarity of thought and enduring ambition as more important than the market size number in a pitch deck. The objective of market sizing is to demonstrate that you are targeting a big market opportunity that you understand deeply. Startups have many unknowns and market sizing is a rough estimation, so keep it simple. 

1. Why does market size matter?

Big companies can only exist in big markets. 

Founder perspective: If you want to build a company that has a DoorDash-sized impact on the world then make sure to commit yourself to a sufficiently large market opportunity. 

Investor perspective: If you want to raise capital from VCs then you need to convince them that your company will generate an exit value that returns their fund. In your pitch you should aim to convey that your startup has the potential to capture at least hundreds of millions of dollars of high-margin revenue within the next decade, within a multiple billion dollar market. 

2. How to estimate market size?

Use the bottom-up approach to estimate market size. Multiply the number of customers by the average revenue per customer per year. 

There are top-down and bottom-up approaches to estimating market size. The bottom-up approach is more convincing because its uses assumptions that are substantiated through other aspects of your pitch, such as customer definition, revenue model, and GTM. VCs also prefer bottom-up because the underlying assumptions can be tested and validated. Ideally you will only use top-down to sanity check the magnitude of your bottom-up estimate.

Keep your method simple and easy to explain. The underlying assumptions for market sizing will remain rough until you have ascertained your exact target customers and revenue model, so avoid undue complexity. 



3. What is the exact definition of market size?

There is no single definition of market size. Early stage companies typically present three estimates for TAM / SAM / SOM. I encourage you to skip the acronyms and present bottom-up estimates for your total addressable market and your revenue in 5+ years. 

We surveyed 30 VCs to better understand how other investors evaluate a startup’s potential scale. We learned that earlier stage investors tend to prefer market sizing presented as TAM / SAM / SOM, whereas later stage investors care more about recent revenue growth as well as estimates for future revenue. 

  • Seed VCs generally value TAM estimates more because they have limited additional information to inform decisions. We heard from seed investors that: “TAM / SAM / SOM works fine as long as the methodology is clear.” 
  • Series A VCs told us that they care more about future revenue even when looking at seed stage startups: “A bottom-up build of future revenue is more useful than basing SOM on a hypothetical % share of TAM or SAM.”
  • Growth-stage VCs pay less attention to market sizing and we heard that: “TAM is a crude indicator. Revenue growth is a better signal. It’s hard to grow 200% at scale if there’s a small TAM.”

The textbook definitions for TAM / SAM / SOM are vague.

You might have seen TAM / SAM / SOM in an article or a pitch deck. If you Google these acronyms and read a few articles then you’ll likely find varying fuzzy explanations (one example depicted below). Pitch decks often include a market sizing illustrated as three bold numbers within three concentric circles, without context or assumptions. Such minimalism saves one from committing to definitions that we might be unsure about, but it also forfeits this opportunity to present a compelling narrative that convinces investors. 

Based on our survey of 30 VCs, it seems that many investors do not know the exact definitions either. So when presenting your market sizing, explicitly state your methodology rather than assume universal definitions.  (These survey results also had me wondering whether later stage VCs are more honest about their knowledge gaps! )



The textbook estimation approach for TAM / SAM / SOM is TOP DOWN ⚠️

Marketing textbooks generally describe the TAM / SAM / SOM approach as: first estimate your largest possible market for $ TAM, of which estimate a narrower proportion that fits your company for $ SAM, and then estimate the % market share you can reach to get to $ SOM. However, the % market share assumption is often an unsubstantiated afterthought, which results in a meaningless estimate for your company’s potential revenue. This approach encourages top-down thinking and is unconvincing. 

The most consistent feedback in our VC survey was to dissuade founders from presenting their future revenue based on % market share of a large addressable market. So, what’s a better approach?


Present bottom-up estimates for your total addressable market and for your revenue in 5 years.

The market sizing definitions stated below are based on consensus across surveyed VCs. However, interpretation still varies so state your assumptions. Also, enough with the acronyms — replace the jargon with more meaningful descriptors. 

Some of the surveyed VCs encouraged founders to drop the conceptual distinction between TAM and SAM. However, opinions on this topic were mixed. Instead of presenting both TAM and SAM, you could communicate your plan for incremental expansion across customer segments and products.

eg. Start with an initial wedge of selling product A into customer segment X. Then expand through cross-selling product B into the same customer segment X. Followed by expanding further through selling products A and B to a new customer segment Y.


4. When should market size be estimated for?

Estimate your market size for 5+ years into the future. 

Surveyed VCs most commonly wanted to see market size estimates for 5 years into the future. If your company is many years away from IPO and/or riding a longterm industry trend (eg. transition to electric vehicles) then it’s more appropriate to estimate 7-10 years into the future. 

A significant proportion of the VCs surveyed also prefer to see market size now as well as 5 years into the future. If you’re targeting a rapidly growing existing market then you can highlight that growth through presenting both now and in 5 years.


Guidance on the underlying assumptions

Now that you understand how to estimate your market size, you need to source the underlying assumptions to feed into the bottom-up equations. You can follow the following steps to arrive at assumptions for calculating total addressable market, initial addressable market, and future revenue.

1) # of Customers

1.1) Define your customers

Precisely focus on the customer segment that will contribute the majority of your potential revenue. 

eg. While DoorDash could claim that every person in the US could potentially order food online, a more convincing segment might be: “Americans in the age range of 25-40, who are employed, and eat out at least once per week.”

If level of demand and/or willingness to pay varies significantly across your customer-base then you should capture such variation in your estimation through customer segmentation. Though keep it simple and only consider segments that will contribute significant revenue. 

eg. Market sizing assumptions can differ significantly between SMB and Enterprise customers. If we’re selling a product into both then we should segment the market. (100K SMBs x 5 seats x $10K per seat = $5B) + (1K Enterprises x 100 seats x $20K per seat = $2B) = $7B total.

1.2) Estimate the total number of customers

The most relevant data sources vary by business category, eg.

  • Consumer: If you can define your target customer (or user) segment in terms of socio-demographics then use the US Census Bureau data on US Population.
  • Vertical-specific B2B: You can identify the number of relevant companies within an industry vertical using US Census Bureau data on US Companies.
  • Enterprise: If you your future revenue will be concentrated in big enterprise accounts then identify what proportion of companies within the Fortune100 or Fortune500 would buy for your product.

Additional example data sources:

  • Research reports (eg. Gartner, Forrester, McKinsey, BCG)
  • Government agencies (eg. Bureau of Labor Statistics, Bureau of Economic Analysis, US SBA, trade.gov, Bureau of Transportation, Dept of Housing, US Dept of Agriculture)
  • Industry bodies (eg. National Business Group on Health, National Restaurant Association, National Association of Realtors)
  • NGOs (eg. UN Dept of Economic & Social Affairs, UN World Tourism)
  • S-1s of companies in your category

1.3) Estimate the number of customers you could acquire in 5 years

You will acquire only a proportion of total customers We need to estimate a realistic number of customers captured by around the time you IPO, so 5-10 years from today. Its best to build this bottom-up through considering how many new customers you’ll be able to acquire (and retain) per year over the next 5-10 years.

Sense check your implied market share. Look at the market shares of existing dominant players in your category and in adjacent categories. Also consider strength of network effects, how entrenched established players are, and ease of distribution (eg. capturing 10% of the Fortune100 is more realistic than capturing 10% of 100,000 SMBs). 

Our expectations for high market shares are often anchored in the dominant consumer-facing FAANGs, yet many other categories are more fragmented or under-penetrated. Pitch decks often state a 10% potential market share. Yet when tech companies IPO they have typically only attained a 0.1% to 2% share of their addressable market. See the chart below based on data in S-1s of recent tech IPOs.

2) $ Avg Revenue per Customer per Year

2.1) Select your revenue model

Identify the most relevant revenue model for your business. You might foresee multiple revenue streams, however its best to keep it simple and focus the market sizing on your core revenue stream.  See the table below for examples (though this is not an exhaustive list).

Each revenue model is split into transaction volume multiplied by pricing.

2.2) Estimate Transaction Volume

This requires you to understand your target customer’s behavior. (eg. How many product will they consumer per year, How much data storage will they require, How many seats per company, etc.)

2.3) Estimate Pricing

Pricing is an artform worthy of volumes, and in practice you might chose to implement multi-tiered pricing differentiation to maximize your profits. But again, for estimating market size, minimize the complexity. 

There are three main approaches to pricing. Value-based pricing is generally the best approach. 

  • Value-based: Estimate how much value your customer attains from your product, and charge a proportion of that value. You can charge more through: (i) creating greater value for your customer; and/or (ii) heightening your customer’s perception of that value creation. Attribution is as important as the actual impact of your product. A rule as thumb is that you can charge in the range of 10-30% of the value you create for your customer.
  • Competitor-based: If your industry has pre-existing comparable products to yours then your customers are likely anchored in pre-existing price ranges. When pitching to VCs you might need to explain why your product has a premium or a discount to comparable products.
  • Cost-based: Estimate the cost to deliver your product and add a margin. Fixed costs are generally low in tech companies, and this is more relevant to operationally intensive and/or asset heavy companies.

How to best apply these approaches varies by the business category, eg.  

  • B2B SaaS: Value-based pricing is the optimal approach to determine your customer willingness to pay. (eg. If your products increase your customer’s profits by $1M per year on a perpetual basis then you can charge a $100-300K per year subscription fee.)
  • Consumer: Anchoring to the price of adjacent products often informs the attainable price, unless your brand is highly differentiated. This also applies to consumer fintech. (See this article)
  • Healthcare: B2B healthcare solutions sold to payers or employers usually have a fee per member per month revenue model, and you can charge a proportion of the cost savings you deliver. D2C healthcare solutions usually a fee for service or a monthly subscription revenue model, and ideally you identify relevant reimbursement CPT codes. Healthcare also includes several more complex pricing models. 
  • Marketplaces: The % take rate in a marketplace is driven by how much demand you can drive to your customer and how much easier you make it to run their business, as well as how competitive your market is. (See Lenny’s newsletter)

Now multiple those assumptions out. Hopefully you arrive at a big number for the addressable market. If not then revisit your assumptions as well as your overall vision. 

Additional Tips 

  • Think long-term and dream big. Most successful startups create or change markets, so you should estimate hypothetical demand for your product in 5-10 years, not just existing demand. Also consider how you will expand average revenue per customer through solving additional problems for your target customers.
  • Global market size is rarely relevant. If your strategy is US-focused then state an addressable market for the US only. If you’re starting in a smaller country and your strategy focuses on multiple similar countries then state an addressable market for those countries and be ready to explain your international go-top-market plan.
  • Ensure that the revenue you are presenting is annual. (eg. If there are 10M potential customers for your product and they might buy your product every two years on average, then you have 5M target customers per year. 
  • For marketplaces, include take rate in the market size calculation rather than presenting overall GMV. For financial products, include fees rather than presenting total transaction value or AUM. If your B2B startup is helping your customer to increase their profits, then you can only charge a proportion of that impact. 
  • Read S-1s of public companies with similar customers or products as your company. Search the SEC database for a public company of interest and open their ‘S-1 Prospectus’. S-1s are a goldmine of information and provide insights well beyond market sizing. 

About Pear VC

Pear partners with entrepreneurs from day zero to build category-defining companies. Our team has founded eight companies and invested early in startups now worth over $80B, including DoorDash, Gusto, Aurora Solar, Branch, and Guardant Health. We use this knowledge to provide founders with hands-on support in product, growth, recruiting, and fundraising. If you’re building a category defining company then reach out to our team.

The Data and Analytics Playbook for Startups

Posted on by adam


Ali Baghshomali, former data analyst manager at Bird, hosted a talk with Pear on data and analytics for early stage founders. We wanted to share the key takeaways with you. You can watch the full talk here. 

While a lot has been said around building go to market and engineering teams, there’s not much tactical coverage for analytics teams. Yet analytics is one of the most fundamental and crucial functions in a startup as it launches and scales. 

When should you start seriously working on analytics?
Why should you work on analytics?
Who should you hire?
What should be in your analytics stack?
What are some case studies of company analytics operations?
What should you do moving forward?

When should you start seriously working on analytics? 

You should start thinking about your analytics platform when your company is nearing product launch. After your product is live, you’ll receive an influx of data (or at least some data) from customers and prospects, so you want to be prepared with the proper analytics infrastructure and team to make the most of this data to drive business growth. 

If you are just starting out and would benefit from working with analytics but don’t have much in house, consider using third party data sources, like census data. 

Why should you work on analytics? 

If done well, analytics will pay back many, many times over in time, work, money, and other resources saved as well as powerful insights uncovered that drive meaningful business growth. 

Who should you hire? 

In conversation, people often use “data scientist” and “data analyst” interchangeably. While fine for casual conversation, you should clearly understand and convey the difference when writing job postings, doing job interviews, hiring team members, and managing data teams. 

Data scientists work with predictive models through leveraging machine learning. Data analysts, in contrast, build dashboards to better display your data, analyze existing data to draw insights (not predictions), and build new tables to better organize existing data. 

For example, at Spotify, data scientists build models that recommend which songs you should listen to or add to particular playlists. Data analysts analyze data to answer questions like how many people are using the radio feature? At what frequency? 

Similarly, at Netflix, data scientists build models that power the recommendation engine, which shows you a curated dashboard of movies and TV shows you may like as soon as you log in. Data analysts would conduct data analysis to determine how long people spend on the homepage before choosing a show. 

Unless your core product is machine learning driven, you should first hire data analysts, not data scientists. In general, a good rule of thumb is to have a 3:1 ratio of data analysts to data scientists (for companies whose products are not machine learning driven). 

For early stage startups, stick to the core titles of data scientists and data analysts rather than overly specialized ones like business intelligence engineers because you’ll want someone with more flexibility and who is open and able to do a wider range of work. 

What should be in your analytics stack? 

Here are examples of tools in each part of the analytics stack and how you should evaluate options: 

  • Database: examples include BigQuery and Redshift. Analytics databases are essentially a republica of your product database but solely for analytics. In this way, you can do analytics faster without messing up product performance. In general, it is advisable to use the same database service as your cloud service. 
  • Business intelligence: examples include Looker and Tableau. Business intelligence tools help you visualize your data. They connect to your analytics database. You should pick a provider based on pricing, engineering stack compatibility, and team familiarity. Don’t just default to the most well known option. Really consider your unique needs. 
  • Product intelligence: examples include Mixpanel and Amplitude. Product intelligence tools are focused on the product itself, rather than the over business. Specifically, they are focused on the user journey. They get code snippets inserted from the product. Because they don’t encapsulate the full code, you should consider this data to be an estimate and use the insights drawn more directionally. Product intelligence tools can be used to create charts, funnels, and retention analyses, and they don’t need to be connected to other databases. 

What are some case studies of company analytics operations? 

Helping Hands Community is a COVID inspired initiative that services high risk and food insecure individuals during the pandemic. 

  • Team: 7 engineers, no data analysts
  • Product: basic with 1000 users
  • Stack: Google Cloud, Firebase for product database, BigQuery for analytics, Google Data Studio for business intelligence, and Google Analytics for product intelligence 

Bird is a last mile electric scooter rental service. 

  • Team: 50+ engineers, 30 analysts, 8 scientists, 6 analyst managers
  • Stack: AWS for cloud, Postgres (AWS) for product database, PrestoDB for analytics, Tableau and Mode for business intelligence, Mixpanel for product, Google Analytics for website, Alation for data, DataBricks for ETL, and Anodot for anomaly detection (you generally need anomaly detection when ~1 hour downtime makes a meaningful difference in your business) 

What should you do moving forward? 

Make a data roadmap just like you make business and product roadmaps. Data roadmaps are equally as important and transformative for your startup. List the top 5 questions you foresee having at each important point along this roadmap. Structure your data roadmap in a way that your stack and team addresses each of the questions at the point at which they’re asked. 

We hope this article has been helpful in laying the foundations for your analytics function. Ali is available to answer further questions regarding your analytics strategy, and he is providing analytics and data science consulting. You can find and reach him on LinkedIn here. 

5 Guidelines for Introducing Product Management to Your Company

Posted on by adam

This is a recap of our discussion with Nikhyl Singhal, VP of Product at Facebook, former CPO at Credit Karma, and former Director of Product Management at Google. 

Watch the full talk at pear.vc/events and RSVP for the next!

Product management can be an elusive topic, especially as its definition changes as the company grows. Early on, product management is focused on helping the company get to product market fit. Once the company achieves it, product management can change dramatically depending on the type of product or service, the organizational structure, and the company’s priorities. We brought Nikhyl Singhal to demystify the product management process and share insights on when, how and why to add product management into your company.

Jump to a section:

In the “Drunken Walk” Phase, Product Managers Should Really Be Project Managers

For Founders Working on Product Market Fit, Maintain Healthy Naivete

If You’re Not a Product Person, Find a Co-Founder Who Can Own Product Market Fit

Introduce Product Management When Founders Shift Priorities

Look for Product Managers Who Can Scale with the Organization

In the “Drunken Walk” Phase, Product Managers Should Really Be Project Managers

While employees at early stage companies may have Product Manager as their title, they should really be owning project management and execution.

Product management, or the goal of helping that company get to product market fit, should be owned by the founders. 

It’s partially an incentive problem. Founders, as Singhal notes, are usually the executives with a larger share of ownership.

“They’re the ones that the investors have really placed money in and the extended team in some ways just aren’t at the same level in scale as the founders,” Singhal says.

However, execution and distribution are team responsibilities–and Singhal considers them much more of a utility than a strategic function. Understanding the allocation of responsibilities in founders versus product managers in early stage companies can be crucial to success.

“I actually embrace this and I [would] suggest, “Look, there’s no shame in saying that we need to bring in product managers to really own a lot of the execution.”

For Founders Working on Product Market Fit, Maintain Healthy Naivete

For early stage founders, Singhal says not to discount naivete. He recounts from his own experience that while others had insider perspectives or felt jaded, his own beliefs helped propel him through company building, ultimately helping him found three companies in online commerce, SAAS, and voice services. 

“I think that the lesson, if I were to pick one, is that healthy naivete is a critical element to finding product fit and actually fortitude around some of those ideas that are, ‘Hey, the world should work this way,’” Singhal reflects. “‘I don’t quite understand the industry, but I want to focus on that user, that business problem, and go forward on it.’”

If You’re Not a Product Person, Find a Co-Founder Who Can Own Product Market Fit

“The speed to be able to go through product fit is so essential for being able to efficiently get to the destination in the final course of action for the company,” Singhal says.

Thus, while it’s possible for founders to take other roles early on, purely outsourcing product fit to the rest of the team is still not a wise decision.

“If you’re not the person who’s owning product fit and you agree that product fit is sort of job number one, what I would say is—find a co-founder who can be essentially the owner of product fit. The reason why I use the term co-founder is for the economics to work.”

Introduce Product Management When Founders Shift Priorities

One issue founders often face with product management is determining when to introduce it. Introducing it too early may lead to conflicts internally, while introducing it too late means the company may have missed out on the prime time for strengthening execution. 

Again, product management is dependent on the founders’ backgrounds. For founders who have backgrounds in product, as long as there is clarity and predictability around what will happen, the company may proceed without product managers. The most common case for introducing product management, however, is when founder priorities need to shift from product fit to scaling the organization.

“This could be establishing new functions,” Singhal notes, “Or fundraising or thinking through acquisition. Marketing is also an important area, or thinking through company culture if the company starts to scale. At this point, if you fail to bring in product management, you’ll see dramatic reductions in efficiency.”

Look for Product Managers Who Can Scale with the Organization

For early product manager hires, companies should consider both the growth curve of the company and the growth point of the individual. Especially for companies that may be in hypergrowth, it’s important to have a mindset that “what’s gotten us here isn’t what gets us there.” This means the product management team must be adaptable. 

Being aware of how product management interacts with other functions is also crucial. 

“Product tends to essentially sit between the power functions of the organization as it deals with scale and growth,” Singhal says. It could be between marketing analytics and product engineering, or sales and product, depending on what the company’s business model is. 

Lastly, founders need to examine their own career trajectories in transitioning product power to teammates. It can be a tough emotional decision, Singhal acknowledges, but this question should be asked early on.

“I think that it’s almost a psychological question around: what is the person’s career ambition as a founder? Do they see themselves as moving into a traditional executive role? Shall I call it CEO or head of sales or head of product? If the goal of the person is to expand beyond product, then I think that the question really deserves quite a bit of weight,” Singhal says.

15 Mistakes Startups Make When Building Their First Engineering Teams

Posted on by adam

This is a recap of our discussion with Pedram Keyani, former Director of Engineering at Facebook and Uber, and our newest Visiting Partner. Keep an eye out for Pedram’s upcoming tactical guide diving deeper into these concepts.

Watch the full talk at pear.vc/speakers and RSVP for the next!

Mistake #1: Not Prioritizing Your Hires

The first mistake managers encounter in the hiring process is not prioritizing hires. Often, when faced with building a company’s first team, managers tend to hire for generalists. While this is a fine principle, managers must still identify what the most critical thing to be built first is.

“The biggest challenge that I see a lot of teams make is they don’t prioritize their hires, which means they’re not thinking about: what do they need to build? What is the most critical thing that they need to build?”

Mistake #2: Ignoring Hustle, Energy, and Optimism

People naturally prefer pedigreed engineers — engineers that have worked at a FAANG company, for example, or engineers that have built and shipped significant products. But for young companies that might not have established a reputation yet, they’re more likely to attract new college grads.

“They’re not going to know how to do some of the things that an engineer who’s been in the industry for a while will do, but oftentimes what they have is something that gets beaten out of people. They have this energy, they have this optimism. If you get a staff engineer that’s spent their entire career at—name-your-company—they know how to do things a particular way. And they’re more inclined to saying no to any new idea than they are to saying yes.”

So don’t worry too much about getting that senior staff engineer from Google. Often, bright-eyed, optimistic young engineers just out of school work well too. 

Mistake #3: Not Understanding Your Hiring Funnel

Managers must be aware of how their hiring funnels are laid out. No matter what size of company or what role, a hiring manager must treat recruiting like their job and be a willing partner to their recruiters.

Get involved as early as sourcing. 

“If they’re having a hard time, for example, getting people to respond back to their LinkedIn or their emails, help put in a teaser like, ‘Our director or VP of this would love to talk to you.’ If that person has some name recognition, you’re much more likely to get an initial response back. That can really fundamentally change the outcomes that you get.”

Mistake #4: Not Planning Interviews

Once a candidate gets past the resume screen to interviews, that process should be properly planned. Interviewing is both a time commitment from the candidate and from the company’s engineering team. Each part of the process must be intentional. 

For phone screens, a frequent mistake is having inexperienced engineers conduct them. 

“You want the people who are doing the phone screens to really be experienced and have good kinds of instincts around what makes a good engineer.”

For interviews, Pedram suggests teams have at least two different sessions on coding and at least one more session on culture. 

To train interviewers, a company can either have new interviewers shadow experienced interviewers or experienced interviewers reverse shadow new interviewers to make sure they’re asking the right questions and getting the right answers down.

Mistake #5: Lowering Your Standards

Early companies can encounter hiring crunches. At this time, hiring managers might decide to lower their standards in order to increase headcounts. However, this can be extremely dangerous. 

“You make this trade off, when you hire a B-level person for your company—that person forever is the highest bar that you’re going to be able to achieve at scale for hiring because B people know other B people and C people.”

What about the trade-off between shipping a product and hiring a less qualified teammate? Just kill the idea. 

“At the end of the day, these are people you’re going to be working with every day.”

Mistake #6: Ignoring Your Instincts

Failure #5 ties into Failure #6: Ignoring your instincts. If there’s a gut feeling that your candidate won’t be a good fit, you should trust it. 

“The worst thing you can do is fire someone early on because your team is going to be suffering from it. They’re going to have questions. They’re going to think, ‘Oh, are we doing layoffs? Am I going to be the next person?’” 

Mistake #7: Hiring Brilliant Jerks

During the hiring process, managers may also encounter “Brilliant Jerks.” These are the candidates that seem genius, but may be arrogant. They might not listen, they might become defensive when criticized, or they might be overbearing. 

The danger of hiring brilliant jerks is that they’ll often shut down others’ ideas, can become huge HR liabilities, and won’t be able to collaborate well within a team environment at all. 

So when hiring, one of the most important qualities to look out for is a sense that “this is someone that I could give feedback to, or I have a sense that I could give feedback to you.”

Mistake #8: Giving Titles Too Early

Startups tend to give titles early on. A startup might make their first engineering hire and call them CTO, but there are a lot of pitfalls that come with this.

“Make sure that you’re thoughtful about what your company is going to look like maybe a year or two year, five years from now. If you’re successful, your five person thing is going to be a 500,000 person company.” 

Can your CTO, who has managed a five person team effectively, now manage a 500,000 person team?  

Instead of crazy titles, provide paths to advancement instead. 

“Give people roles that let them stretch themselves, that let them exert responsibility and take on responsibility and let them earn those crazy titles over time.”

Mistake #9: Overselling The Good Stuff 

When a team’s already locked in their final candidates, young companies might be incentivized to oversell themselves to candidates—after all, it’s hard to compete against offers from FAANG these days. But transparency is always the best way to go. 

“You need to tell a realistic story about what your company is about. What are the challenges you’re facing? What are the good things? What are the bad things? Don’t catfish candidates. You may be the most compelling sales person in the world, and you can get them to sign your offer and join you, but if you’re completely off base about what the work environment is like a weekend, a month, and six months in, at some point, they’ll realize that you are completely bullshitting them.”

As Director of Engineering at Facebook, Pedram made sure to put this into practice. After mentioning the positives and perks of the job, he would follow up with “By the way, it’s very likely that on a Friday night at 9:00 PM, we’re going to have a crazy spam attack. We’re going to have some kind of a vulnerability come up. My team, we work harder than a lot of other teams. We work crazy hours. We work on the weekends, we work during holidays because that’s when shit hits the fan for us. I wouldn’t have it any other way, but it’s hard. So if you’re looking for a regular nine to five thing, this is not your team.” 

Make sure to set expectations for the candidate before they commit. 

Mistake #10: Focusing on the Financial Upside

Don’t sell a candidate on money as their primary motivation during this process. 

“If the key selling point you have to your potential candidate is that you’re going to make them a millionaire you’ve already lost.”

Instead, develop an environment and culture about a mission. Highlight that “if we create value for the world, we’ll get some of that back.”

Mistake #11: Getting Your Ratios Wrong

Companies want to make sure that they have the right ratio of engineering managers to engineers. Each company might define their ratios differently, but it’s important to always keep a ratio in mind and keep teams flexible.

Mistake #12: Not Worrying About Onboarding

Once a candidate signs on, the onboarding process must be smooth and well-planned. Every six months, Pedram would go through his company’s current onboarding process himself, pretending to be a new hire. This allowed him to iterate and make sure onboarding was always up to date. 

“It’s also a great opportunity for you to make sure that all of your documentation for getting engineers up to speed is living documentation as well.”

Mistake #13: Not Focusing on Culture

Culture should underscore every part of the hiring process. It can be hard to define, but here are some questions to start: 

  • How does your team work? 
  • How does your team solve problems? 
  • How does your team deal with ambiguity? 
  • How does your team resolve conflicts? 
  • How does your team think about transparency and openness? 

“Culture is something that everyone likes to talk about, but it really just boils down to those hard moments.”

Mistake #14: Never Reorganizing

Failure #14 and #15 really go hand in hand. As many companies grow, they may forget to reorganize. 

“You need to shuffle people around. Make sure you have the right blend of people on a particular team. You have the right experiences on a team.” 

Again, keep your ratios in mind.  

Mistake #15: Never Firing Anyone

Lastly, and possibly the hardest part of hiring, companies need to learn to let people go. 

“People have their sweet spot. Some people just don’t scale beyond a 20 person company. And, you know, keeping them around is not fair to them and not fair to your company.”

What It Takes To Go from 0 to 1: From 0.5 to 1 (Part IV)

Posted on by adam

This post is Part 4 of our four-part series on What It Takes To Go from 0 to 1.

Let’s assume you’re a SaaS company that’s now raised some seed money. You’ve raised from us and you have two customers, and the founder has done all the sales. 

Now your task is to prove two things:

  1. someone who is not you can sell your product
  2. you can optimize and scale that process 

This usually involves building a sales team or setting up a reliable marketing channel. The test for this stage is whether you have a reliable formula for your growth. That is, you should be able to confidently say, “if I do X, I will get Y new customers / users / revenue.”

Pure growth is not enough. You can be growing super fast, but if you have no retention, we know that growth will die. Again, you may be tempted to buy a bunch of ads right before your raise to spike your growth for two months, but smart investors know that that’s not real growth. 

You may be surprised to learn that pure revenue is also not enough. We have found that post-money valuation of series A companies and their monthly recurring revenue is not correlated at all:

If product love is the one thing that matters most to us at 0.5 stage, what is it for the 1 stage? That you’re going to be a “big company.” We are looking for predictors of success. You can think about it as the “second derivative” of your growth. 

In this stage, we want to make sure that people not only love your product, but that they love it enough to pay you enough money to make it profitable to grow. 

Even if you’re at only 200K in MRR, if we can see that you’ve gone from one person using your product to 20 people using your product, and those people are using you every day and they can’t live without you, you’re probably a great company, like Slack! They didn’t need to have 1 million in ARR for investors to know that people loved that product and that it was going to stick around.

Series A investors are going to look at your scale metrics, like LTV (lifetime value) to CAC (cost of customer acquisition).

To get to Series A from the seed stage (or from 0.5 to 1), the most important thing you need to do, as a seed founder, is to make a plan and measure your progress. Determine where you want to be in four quarters, then walk backwards and figure out what you need to achieve that. 

Look at everything you need to do. 

For example, if you want to be at $1 million ARR, with some amount of cash for six months at the end of Q4, you might determine that you need to hit $100K in revenue by Q2. You probably are also going to need enough leads by Q2. If this is a SaaS business, you may want to hire a salesperson for that. And if you have all these customers, you’ll likely want to support them and keep them happy, so you might have to hire a customer success person in Q3. To have something to sell in the first place to get to that Q2 revenue, you might need to have an MVP by the end of Q1 that requires hiring a certain amount of engineers.

You’ll need to do all this math to find out what that plan all costs and how much cash you need to have for it. It is likely you’ll need to iterate on this plan, which is why you also need to measure everything as you proceed. What gets measured gets done, and the bonus is that it’s easier to measure things at the seed stage! We love data driven CEO’s, and we even encourage founders to display their key metrics to everybody in their company. When you go out to raise our series A, you can just take your dashboard to the investors!

Once you have a plan, and you have your measurements, you’ll need to put those two together to figure out whether you’re on track or not. This sounds very simple, but we’ve had many founders suddenly call us with three months of cash left out of the blue. Force yourself to send reports to yourself, to your team and to your investors. When you do that, you’re actually committing to something, and that makes you true to the plan. 

Here at Pear, we make every one of our seed companies run through a planning exercise at the very beginning of our partnership with them, and we review the plan every quarter. When our founders are in trouble, we review it every week, so we can figure out what our goals are and what we need to hit. 

Final Stretch: Don’t Mess Up the Actual Fundraising

Fundraising is a little like selling a house. If you’re trying to sell a house, but you don’t have your inspections complete and you haven’t cleaned up the lawn, you’re probably going to get a lower final price than if you’d done all your work—even if you’ve got a great house!

Put another way: no matter how great your numbers look, you still need to have a great pitch. You have to actually communicate with data. You have to have a rational ask.

Remember, there are much fewer Series A funds out there than angels and seed funds, so the stakes are higher with each meeting, and it’s much slower and more complex. You can’t hand wave. You need to have concrete, quantitative answers, and investors are going to take several weeks to get back to you. It could take longer. The good ones do it fast, but it’s not 30 minutes. 

Also, think through your process. Don’t contact 20 series A investors at once with your initial pitch. Stagger your pitches so you can iterate and revise between each, and save your top choice investors for last, after you’ve gotten feedback from the others.

This brings us to our final piece of advice for this process: diligence who you work with! We’ve seen founders get desperate and take money from investors they shouldn’t. We’ve done that personally on our own entrepreneurial journeys. It’s absolutely painful. You have to know who you’re fundraising from.

If you’re considering us as partners on this long journey, we hope you’ll take the time to get to know us, just as much as we promise to take the time to get to know you.