Also for anyone interested, we are looking to expand our software portfolio so if you have a solution we would be happy to have a chat! Our main client base is in the Fintech, Gaming and Investment industries.
Ask HN: Any good essays/books/advice about software sales?
61–70 of 98 posts
Re: Ask HN: Any good essays/books/advice about software sales?
#62Believe it or not, for "selling software": Selling Microsoft - https://www.amazon.com/Selling-Microsoft-Secrets-Successful-... The fundamentals of software sales haven't changed much since this. While B2C SaaS is different, the B2B platform world is still much as described in this book, and more importantly, the buyers are still the people who were buying when this book was published. While selling today should have…
Re: Ask HN: Any good essays/books/advice about software sales?
#63As someone who has made lots of purchasing decisions for software (ERPs, Electronic Health Records, productivity tools) at places I've worked over the last 18 years: I don't want to talk to salespeople, only product designers, developers, executives, and support staff. They are the people who make the stuff and/or are left holding the bag for the product when the salesperson is jetting off to their next meeting. Same…
Designers and devs and makers too busy doing their jobs to bother with your arcane requirements and need to do an 'apples-to-apples' comparison on every bid, respond to hundred-page RFPs in nitnoid detail, buy you drinks so they can suss out why you don't actually know your own requirements, navigate your own effed up procurement process, your politics, your internal power struggles, and your primadonna self-belief that you are special.
Buyers are in the power position for sure; you write the checks!
But just know that there's a whole layer of people out there who end up in sales who have to clench their teeth and endure the bullshit of dozens of companies in their portfolio – in the same way you might feel like you have to endure theirs.
Be a qualified lead. Show you have your shit together, and then yeah we can start bringing sales engineers and devs and designers into the conversation so you're not wasting their time.
If you want an easy procurement process and no regrets, follow best practices: come to the table with your internal and external research done, with a clear list of requirements, an executive sponsor with actual decision-making power. Understand that if you change your requirements midstream the budget will change. Pad your budget so I don't have to pad my estimate.
Sales guys can be douchey for sure, but that doesn't mean they're trying to scam you. Their incentives are more closely aligned with yours than anyone else's.
Re: Ask HN: Any good essays/books/advice about software sales?
#641. Customer Centric Selling
https://books.google.com/books/about/CustomerCentric_Selling...
2. Never Split The Difference (from buyer angle, but still good)
Re: Ask HN: Any good essays/books/advice about software sales?
#65Are you trying to sell a product or build a services business? Very different things! I have some books I like on software sales, but not for services businesses; most of the successful services businesses I'm familiar with didn't include a salesperson in their founding team.
We are 2 engineers who want to find businesses and create value for them from scratch, not only be concerned with technical stuff(like in our current careers). This is what we are passionate about & we are trying to sell service. BTW here is the landing page: https://www.mazeg.io/en
Your website looks pretty nifty but the different speeds with which the tech and domain listings scroll made me motion-sick, I realize this is a me problem. Maybe slow down the tech listing or have them going at the same speed? (I only checked on desktop btw)
Also if you can it would be nice to book a photographer to take portrait shots of you and your co-founder, maybe a combined photo for mobile? Just a suggestion because I believe it would look cooler than simple profile pictures and it would showcase your personalities even better. (You both seem cool dudes)
Re: Ask HN: Any good essays/books/advice about software sales?
#661. Get a lead and qualify it. Red flags for qualification are small company size, weird location which isn't in your geography (e.g. middle east), person enquiring is not sufficiently senior in the organisation etc.
2. Understand the customer's problem better than anyone else. This includes visiting them, sitting down in person, clearly stating their problem on some slides so they know you understand it. If you are the only person to visit the customer in person, you will probably win the lead.
3. Describe how you plan to solve the customer's problem, and demonstrate how you have relevant experience and how this won't be a challenge. This isn't an exciting project for you - you want to work together but this is an easy problem that you have solved a hundred times before and you can solve it with confidence.
4. Be flexible in the sales process - ask the customer to help you tweak the proposal until it's exactly what they want.
5. Tailor the solution to the size of the business - don't sell a giant over-engineered solution to their problem if they are tiny, find a way to solve it with no frills or quick hacks. On the flipside, don't sell a no-frill's solution to a giant enterprise, they will want to believe they are getting something suitably engineered. Also tailor the sales process - if you are winning a massive contract you put in more effort than a tiny contract (and if sufficiently small, your proposal can just be an email back).
6. Give a clear and reasonable commercial model that fits in-line with the customer's expectations. If it doesn't fit with their expectations, adjust the scope and price (don't significantly adjust price without adjusting scope - it's bad for relationships)
7. Be super flexible when closing the deal. You are a small agency, your benefit is you can do things that bigger agencies can't. Don't endlessly argue over meaningless contract terms - just make sure they pay your first invoice which should 'cover your ass' until the next invoice, and work from there.
The main difference in agency selling compared to standard software selling is that it is high-engagement and high-effort. If you spend 5 days winning 20 days of work, you are probably doing pretty well.
Also, the big mantra is "doing is selling" - doing a good job on one project will lead to both more work from the same client, and recommendations which brings in even more. Everyone employed at a consultancy/agency is responsible for selling, some directly, others indirectly by making sure they do a great job. The company doesn't exist without winning projects!
Re: Ask HN: Any good essays/books/advice about software sales?
#67As someone who has made lots of purchasing decisions for software (ERPs, Electronic Health Records, productivity tools) at places I've worked over the last 18 years: I don't want to talk to salespeople, only product designers, developers, executives, and support staff. They are the people who make the stuff and/or are left holding the bag for the product when the salesperson is jetting off to their next meeting. Same…
> I don't want to talk to salespeople, only product designers, developers, executives, and support staff. They are the people who make the stuff Designers and devs and makers too busy doing their jobs to bother with your arcane requirements and need to do an 'apples-to-apples' comparison on every bid, respond to hundred-page RFPs in nitnoid detail, buy you drinks so they can suss out why you don't actually know your…
The salesperson has a vested interest in getting the customer everything they need to win business so they get their commission. A good one is an utter pain in the ass internally because servicing them and the customer is quite often at the expense of everything else. 1:1 sales tactics don't scale unless the customer is huge. It's a classic 80:20 rule - 20% of customers normally drive 80% of revenue, so it's only sensible to focus on certain customers and ignore others - but obviously that only makes sense in a vacuum where businesses don't rise and fall, and suppliers alongside them, so you need to toe the value threshold when it comes to exposing customers to engineering - which is where a good salesperson is gold.
Product designers, developers, executives, and support staff - all of them have better things to do than service a single customer most of the time. Building features, marketing, hiring staff, documentation, validation, and making new products. All these things are 1:N activities. If they're sucked up talking to one customer, they're not doing 1:N. It quite often feels like the salesperson works for the customer, not us, because it's clear to everyone that the demands are hurting the product in the long run by sapping everyone's time doing servicing when the opportunity:cost ratio isn't there.
To your point, it feels great when a customer follows the expected flow. Planning/marketing/engineering/executives can be brought in as and when needed, rather than when they're demanded of. Almost all customers demand the time and attention of everyone but the sales team, but I've often found that the ones who provide all the info and jump through all the hoops get what they want much faster.
Re: Ask HN: Any good essays/books/advice about software sales?
#68Believe it or not, for "selling software": Selling Microsoft - https://www.amazon.com/Selling-Microsoft-Secrets-Successful-... The fundamentals of software sales haven't changed much since this. While B2C SaaS is different, the B2B platform world is still much as described in this book, and more importantly, the buyers are still the people who were buying when this book was published. While selling today should have…
4 reviews. 3 stars. A hundred quid. This has got to be the most erudite book recommendation in the history of HN. I’m very tempted to get it just to see the fuss.
Re: Ask HN: Any good essays/books/advice about software sales?
#692. Speak in conferences that interests your customers. If you are a techie, default attraction is to speak in tech conferences. Unless you are selling to CTOs or VP(Engineering), none of your customers come there. You shouldn't just participate in these conferences where your customer's come. You should be a speaker. Speakers have a certain authority and your customers will crowd to that awesome speaker of the conference. It might only generate lead, but it will be a strong, qualified lead. From sales point of view, these conferences will give a pretty good idea of what matters to your customers.
3. Find the decision maker as quickly as possible and speak to them rather than wasting time with gate-keepers who can say no but not yes. Decision maker is the one who writes the cheque or the sponsor of the project or who can say yes as well as no. Decision maker need not be a CEO all the time.
4. Roleplay sales calls. Record these roleplays and keep improving your tone, words, tempo everything. You should be able to establish quickly why you, why now, and why at the price point you mention.
5. In every step of the journey, they should see value in interacting with you. As often as the prospect says, "of all the agencies I'm talking to, you folks come with depth and present with structure", it is better for you. Even if they don't close because of price, they will come back to you.
6. Make them smile during the sales call. There are many ways to do it. They will forget what you told them, but they will never forget how you made them feel. If you make them feel good, they will come back. At the least, they will refer you to others.
7. As a techie, you might have dealt with logic and deterministic outcomes. Sales is emotional and probabilistic. Get used to it. It is not easy.
Finally, good luck.
(P.S: If interested you can read what I wrote about: Mastering sales as a CTO: https://jjude.com/cto-sales/; it is not as agency owner, but I get on sales calls for an IT services company. So probably we are closer in that sense).
Re: Ask HN: Any good essays/books/advice about software sales?
#70As someone who has made lots of purchasing decisions for software (ERPs, Electronic Health Records, productivity tools) at places I've worked over the last 18 years: I don't want to talk to salespeople, only product designers, developers, executives, and support staff. They are the people who make the stuff and/or are left holding the bag for the product when the salesperson is jetting off to their next meeting. Same…