How the Sales organization in a large company slows innovation

Startup founders are often asked by investors, customers, and employees "what happens if [some big giant company] gets into your business?" The standard answers are along the lines of, "it won’t be their focus and will be ours," or "what if they don’t?"

But there’s another reason. One of the very things that makes a giant company formidable is the thing that makes it hard for them to innovate. The giant sales force and distribution channels they use to take a product to market can get in the way of product innovation.

If you have a new innovative product inside a large established company, it can be much harder to reach product market fit than it would be for the same product in a startup. An established company with a large sales force is accustomed to selling. They build a product and take it to their buyers. The buyers buy.

A product that’s in search of a market fit doesn’t yet know who their buyers are. They don’t know what company would buy, why they buy, or who inside the company are the buyers and the users. They don’t know what business problems they’re solving at the companies, and who has those problems. They don’t know how the customer wants to pay and how much they want to pay. The search for product-market fit is, in part, experimentation to find the answers to these questions.

This is fundamentally incompatible with the sales force at a large product company. This sales force wants a stream of qualified inbound leads. They want to be able to walk in and say this is what the product does and the business problem it solves and we know this because there are other customers that bought to solve the same problem. They want a product that has all the maturity of the company’s other products and plays well with related products the company or their partners make.

These sales forces are designed for acquisitions at scale. They’re not designed for experimentation. But you don’t get the chance to experiment because this is the only sales force you have. You can’t build a small sales organization, and you can’t tell your existing one they aren’t allowed to sell this new shiny thing. The result is that a large enterprise sales force won’t sell the product or won’t sell it effectively. They’re going to just keep selling the things that they always sold because the easiest way to maintain their commission is to keep doing what they’ve been doing. Taking risks with their customers on this new thing that might not even work right is a recipe for lost sales.

When a company talks about disrupting itself and bringing a new, cheaper product to market before a startup does, one of the reasons this can fail is that the sales organization is resistant to the new product. Their paycheck depends on them selling a certain dollar value, and if you bring a product that’s much cheaper, they will resist selling it, even if it’s 5x as good, and even if they’re losing customers to a startup in their space. The natural tendency is to work in a way that maximizes their commission. You can overcome this with a compensation plan design, but it’s hard to get right and often won’t work.

The other problem here is that to find market fit, the creators of the product must be close to the customer. They need to do the selling, so they can learn why the customer likes or dislikes the product. Unless they’re working through the early product with the customer, they don’t truly understand what they’re selling. This is why it’s always good for a startup’s founder to be the primary seller until the company scales.

In a large company with a sales organization, this isn’t possible. The product creators don’t talk to customers, the salespeople do. The founding engineers and product managers might be brought in to help close the sale, but they’re almost never involved in the early stages of the customer discussion. This leaves a large number of discussions where the product founders never know that a sale was even in progress because the sales team disqualified the customer or the customer had needs that the product didn’t meet.

If your product is a close adjacent to something the company already makes, then this might not be an issue. The same customers are buying for the same reasons, or a new market is buying for the same reasons, your existing sales engine can keep working. This leads to companies having substantially all their new product work taking the form of incremental improvements on an existing product line. It’s why they build adjacent products that they know will be of interest to their existing customers. It’s why they rarely define new product categories.

Your comments:

Text only, no HTML. URLs will automatically be converted to links. Your email address is required, but it will not be displayed on the site.


Not your company or your SEO link. Comments without a real name will be deleted as spam.

Email: (not displayed)

If you don't feel comfortable giving me your real email address, don't expect me to feel comfortable publishing your comment.

Website (optional):

Follow me on Twitter

Best Of

  • How not to apply for a job Applying for a job isn't that hard, but it does take some minimal effort and common sense.
  • Movie marketing on a budget Mark Cuban's looking for more cost effective ways to market movies.
  • California State Fair The California State Fair lets you buy tickets in advance from their Web site. That's good. But the site is a horror house of usability problems.
  • Customer reference questions. Sample questions to ask customer references when choosing a software vendor.
  • Comment Spam Manifesto Spammers are hereby put on notice. Your comments are not welcome. If the purpose behind your comment is to advertise yourself, your Web site, or a product that you are affiliated with, that comment is spam and will not be tolerated. We will hit you where it hurts by attacking your source of income.
  • More of the best »

Recently Read

Get More

Subscribe | Archives


Assumptions and project planning (Feb 18)
When your assumptions change, it's reasonable that your project plans and needs change as well. But too many managers are afraid to go back and re-work a plan that they've already agreed to.
Feature voting is harmful to your product (Feb 7)
There's a lot of problems with using feature voting to drive your product.
Encouraging 1:1s from other managers in your organization (Jan 4)
If you’re managing other managers, encourage them to hold their own 1:1s. It’s such an important tool for managing and leading that everyone needs to be holding them.
One on One Meetings - a collection of posts about 1:1s (Jan 2)
A collection of all my writing on 1:1s
Are 1:1s confidential? (Jan 2)
Is the discussion that occurs in a 1:1 confidential, even if no agreed in the meeting to keep it so?
Skip-level 1:1s are your hidden superpower (Jan 1)
Holding 1:1s with peers and with people far below you on the reporting chain will open your eyes up to what’s really going on in your business.
Do you need a 1:1 if you’re regularly communicating with your team? (Dec 28)
You’re simply not having deep meaningful conversation about the process of work in hallway conversations or in your chat apps.
What agenda items should a manager bring to a 1:1? (Dec 23)
At least 80% of a 1:1 agenda should be driven by your report, but if you also to use this time to work on things with them, then you’ll have better meetings.

Subscribe to this site's feed.


Adam Kalsey

Mobile: 916.600.2497

Email: adam AT

Twitter, etc: akalsey



©1999-2019 Adam Kalsey.