3 ms·
If your product is Enterprise or B2B, you need a few things (in my experience): 1) A first client to take a chance on you, because no one wants to be the first
by sbarre 7y ago
If your product is Enterprise or B2B, you need a few things (in my experience):
1) A first client to take a chance on you, because no one wants to be the first client, very few companies will buy something that no one else has bought. In my experience your first client (or first few) is the result of some existing personal connection to the client (i.e. a favour/referral), and expect to be at their beck and call for a while, and probably take a bath on the price.
2) You need an experienced sales team that knows how to sell to enterprise/B2B. This is not something you can "pick up" or learn on the job (or at least is very difficult to do). You need to hire someone who has done it before, otherwise you will stumble and spend your way through months-long sales cycles only to have them fail at some late stage because you didn't know how to prepare.
3) You likely need standards certifications and third-party testing. Look into ISO 27001 and other similar standards if you're a software company. Get third-party security testing done up front. Have pre-written answers and "white papers" around privacy, data governance, scaling, deployment, etc..
I've been on both sides of selling into enterprise and medium/large B2B and it's a solid 50/50 mix of your actual product capabilities and your company's ability to navigate procurement and due diligence.
- ghiculescu 7y ago#2 and #3 are probably true for enterprise but definitely not true for SME B2B. Source: we’ve been targeting that niche (15-500 employee companies) for 8 years. Have made two experienced sales hires both in the last year, and dont have any standards certifications. Most businesses are very reasonable and just want you to solve their problems.
- sbarre 7y agoFair enough, I was definitely thinking medium-size B2B and up, where the people you're dealing with while trying to sell the product are (probably) not the internal stakeholders who want to buy it (i.e. procurement, IT/security, etc) It also depends on what you're selling of course. My experience is in data management solutions (including PII data), and standards/requirements can be pretty demanding in that world.
- danieltillett 7y agoYou forgot the most important thing - a 2 year runway. There is a trick to speed things up a little with Enterprise sales - find out who is an approved supplier for the enterprise you want to sell to and get them to “sell" your product for you under some sort of licensing deal, but where you actually do all the selling. This cuts out a huge amount of pointless activity dealing with said enterprise’s lawyers and purchasing people.
- jon-wood 7y agoYou definitely can get in the door without ISO 27001, but you'll spend way more time on due diligence for each deal because you can't just point at the badge. Whether that's a trade off you're willing to make probably depends on your exact company, but ISO 27001 itself is a painful process to get certified for, especially if you're a young company without any established internal processes.
- sbarre 7y ago100% agree, but even if you don't go through the whole certification process (which is painful and expensive), it's worth spending the ~$1,000 on a "cert-in-a-box" kit to understand the framework of the standards and what kind of processes your company will eventually need to put in place as it grows. Also in my experience, being able to produce existing docs around your standards and processes, versus producing them on-demand, helps inspire confidence in the prospect's due diligence team, because it shows them you've thought of this before they asked about it. :-)