<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by justinbenson on Medium]]></title>
        <description><![CDATA[Stories by justinbenson on Medium]]></description>
        <link>https://medium.com/@justinbenson?source=rss-4c92efd50578------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*E-XPzLijXF6a0vmV.jpeg</url>
            <title>Stories by justinbenson on Medium</title>
            <link>https://medium.com/@justinbenson?source=rss-4c92efd50578------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 17:49:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@justinbenson/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Discount seeking prospects and vampire customers]]></title>
            <link>https://medium.com/@justinbenson/discount-seeking-prospects-and-vampire-customers-41673a6a3b82?source=rss-4c92efd50578------2</link>
            <guid isPermaLink="false">https://medium.com/p/41673a6a3b82</guid>
            <dc:creator><![CDATA[justinbenson]]></dc:creator>
            <pubDate>Sun, 10 May 2015 19:33:48 GMT</pubDate>
            <atom:updated>2015-05-10T19:33:48.415Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Discount seeking prospects and vampire customers</strong></p><p>At Spreedly we have 3 types of prospects. The vast majority never question our prices. They decide whether the value outweighs the cost and sign up. The second group emails and asks about a discount and when told no they fall into the first group. There is a third group though that is more problematic. When told no they come back and again ask for a discount (perhaps more than once) with little more than a slight rephrasing of their original argument for why they believe they should receive a discount.</p><p>In the beginning I thought of the 3rd group as a subset of the 2nd group with a little more persistence. Over time though I’ve come to recognize that this is a distinct group of customer with it’s own unique set of challenges. At Spreedly at least there is a very high correlation between the discount seeking prospect and the vampire customer. (Vampire customer’s consume a disproportionate amount of your company’s resources; support, development and management)</p><p>Discount seeking prospects become vampire customers in 3 major ways:</p><ol><li>They&#39;re cheap: Just as they tried to drive your price down they take that same approach to all aspects of their business. Spreedly is an API service thus requiring a developer to do the integration. DSP’s often use the cheapest developers — either on a project/quote basis or on staff. What that inadvertently does is shift the implementation work from their side to your side of the fence. DSP developers are the most likely to show up in your support channel with very little understanding of what your service does and wanting answers to questions at every stage of the implementation.</li><li>They&#39;re entitled: That same sense of entitlement that drove their discount request shows up in their expectations around what your service should do and how your support should be. They&#39;re the most likely to expect that your service support every single nuance of their use case and demand changes if it doesn’t. They have little respect for the fact you&#39;re trying to scale your service and stay focused on your core value proposition or that they&#39;re on your cheapest plan. They just need the “fix” implemented immediately as you&#39;re holding up their go live.</li><li>You&#39;ll never delight them: Perhaps denying their discount request up front set the tone but either way you&#39;ll never delight this customer. Any change over time (say to your API or the way your service works or if they need to upgrade to a new plan based on their growth) will kick off a new round of complaints. Their overall negativity will weigh on your support group who realizes they “can&#39;t win” with this customer.</li></ol><p>In short they&#39;re not worth having as customers. However I will also acknowledge we haven&#39;t found a good way of handling the issue now that we&#39;ve identified it. In some cases we&#39;ve been successful in steering them away during pre-sales by emphasizing the lack of technical fit and our concern that they&#39;ll sign up and pay good money only to be disappointed. However if an obvious opportunity like that doesn&#39;t present itself then we&#39;re kind of stuck. For now we’ve recognized the problem and will continue to explore what we can do to solve for it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41673a6a3b82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Depression, founders and enterprise sales people]]></title>
            <link>https://medium.com/@justinbenson/depression-founders-and-enterprise-sales-people-83e6e5a3848b?source=rss-4c92efd50578------2</link>
            <guid isPermaLink="false">https://medium.com/p/83e6e5a3848b</guid>
            <dc:creator><![CDATA[justinbenson]]></dc:creator>
            <pubDate>Sun, 15 Jun 2014 15:14:07 GMT</pubDate>
            <atom:updated>2014-06-15T15:14:07.997Z</atom:updated>
            <content:encoded><![CDATA[<p>This post was inspired by Sam Altman’s recent post on <a href="http://blog.samaltman.com/founder-depression">Founder depression</a>. Sam’s post was brief and didn&#39;t really cover new ground. It did get me thinking though about the causes behind depression. (BTW I’m thinking of ‘depression’ as a temporary state of affairs not the more serious medical condition) Why is a Founder more likely to end up being depressed compared to someone who has a very important, stressful occupation at a technology company?</p><p>Having lived in both world’s I think there are two key differences. Firstly, when you found a company it becomes more than a job. Friends, family and your extended network view you differently. Therefore success and failure are amplified. Think of it this way. How do you respond to hearing a friend didn&#39;t like their job and quit and now works somewhere else? Compare that to hearing your friend’s startup burned through all the money they raised and then failed. Or hearing that a peer you worked with in the past just got a big promotion vs hearing another peer’s startup got acquired by Google/Facebook/Cisco etc. So Founder’s are acutely aware that the spotlight is shining brighter and that nothing is ever “left at the office”</p><p>The second main issue is the velocity of momentum swings. I think this is the single biggest issue that overwhelms many founders and is perhaps least discussed. In Sam’s post he states “The world can be falling down around you—and most of the time when you’re running a company, it is” If that were really true you would most likely be put out of your misery within a few months. Secondly, human’s seem pretty good at managing steady state environments. It’s unpredictability to unsettles people more, at least in my experience.</p><p>The real challenge is that most of the time your company is succeeding really well in some areas, failing miserably in others and treading water in others. It’s not unusual to spend the morning really pleased with a new customer win to then spend the afternoon reeling from an investor who’s backed out of your next round at the last minute. Or to have a major design improvement measurably improving conversion stats only to have a key engineer hire decide to stay where they are and not take the leap after sleeping on it over the weekend. All these things regularly happen over the course of a week/day/hours.</p><p>Startups are an extension of the Founder’s being and as Founder’s you&#39;re exposed to all areas of the business simultaneously. It’s this one two punch that creates incredible stress and sustained stress can result in depression.</p><p>We experience these velocity swings at <a href="http://spreedly.com/">Spreedly</a>. In the past I was an enterprise sales person. I’m regularly thankful for that experience when it comes to managing the velocity of momentum swings.</p><p>In enterprise sales usually 50% of your salary is tied directly to your performance. And often the difference between missing, meeting or beating your number comes down to closing or not closing 1, 2 or 3 deals per year. This experience helps you as a Founder in 2 major ways. Firstly, due to the amount of your salary tied up in performance your career extends further into your personal life. Most of the downpayment on our first house came after closing my first major deal as an outside salesperson. And 24 hours before that deal was supposed to close the buyer got cold feet and tried to push it out 100 days. Try telling your wife and extended family that you in fact won’t be making an offer on a house for 90 more days and you begin to understand your professional success and failure bleeds into your personal life.</p><p>As a sales person heading into the end of quarter/year there is one deal that’s looking really good, one that could break either way and one that had committed now falling to pieces at the last minute. All in the same day. The first time I had all 3 come in at the same time I was on cloud 9. My then VP of Sales patted me on the back and said “Never let the highs get you too high or the lows get you too low.” That was good advice next quarter where I turned in a zero.</p><p>This might be one reason why failed founders succeed on later startups. There’s nothing that trains you for dealing with the stress of momentum swings quite like doing them. If you havent’ experienced that before and you have the chance to add someone to your founding team that has I’d strongly recommend it. And as that VP said “Don’t let the highs get you too high and the lows get you too low”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=83e6e5a3848b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Cold” email advice for startup sales people]]></title>
            <link>https://medium.com/@justinbenson/cold-email-advice-for-startup-sales-people-64633685e3ca?source=rss-4c92efd50578------2</link>
            <guid isPermaLink="false">https://medium.com/p/64633685e3ca</guid>
            <dc:creator><![CDATA[justinbenson]]></dc:creator>
            <pubDate>Tue, 13 May 2014 18:55:10 GMT</pubDate>
            <atom:updated>2016-01-18T19:01:49.593Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m a big believer in sales. On sales as a skill and a trade. A good salesperson is similar to a medical specialist. By asking a series of questions they can define and quantify the pain a business is experiencing. As any good doctor knows, letting patients self assess and then prescribe a solution to what ails them is bad medicine. Good sales people know when they can help and when they’re not needed based on a series of thoughtful questions.</p><p><a href="http://spreedly.com/">At my company</a> we proactively email prospective customers. I like to do it. We also receive inbound sales emails too. I’m not sure why (my theories would be a separate post) but the quality of these emails varies wildly and is trending to worse. This is my attempt to help as I suspect many of those trying aren’t getting great direction or help.</p><p>Firstly. What is the goal of your introductory email? Your goal is to *get a response*. That’s it. Of course, it’s pretty hard to do. But that’s all you want from your initial email. And yes a “No we&#39;re not interested” is a valid response.</p><p>A response is someone taking time out of their day to reply to your unsolicited interruption. So it’s a pretty big deal. You need to earn that reply by making your email as polite and succinct as possible. Here’s a general outline and approach:</p><p>First Paragraph: Introduce yourself and your company and tell them why you are emailing them. (I&#39;m assuming you&#39;ve done some homework and aren’t just spamming)</p><p>i) Avoid all buzzwords. Buzzwords tell me you don&#39;t actually know what your service does to help customers in a real way.</p><p>ii) Contextualize. If you&#39;re emailing a 10 person startup don&#39;t brag about 7 F500 companies you have as customers.</p><p>Here’s a quick example:</p><p>“Hi Joe,</p><p>I’m Mary Wrecker from Acme Corp. We’re a 50 person startup determined to solve the challenge faced by online merchants who need to work with multiple payment endpoints simultaneously. I’m emailing your company because we have existing customer’s (one or two examples) who appear to share similarities in their approach to payments as (your company). My guess is as Director of Payments you’d have the best view into whether what we provide is worth exploring further.”</p><p>Joe has context on your company. On what you do at a high level in plain speak. You&#39;ve displayed some confidence that you can help without sounding arrogant. Intellectually he’ll be engaged to see if your confidence is misplaced and will read on.</p><p>After that intro paragraph you want to spell out 2 — 3 ways you help companies. Again, don&#39;t be too presumptive.</p><p>“If we can help Acme Corp it will be because one or more of the following is something you want to fix now or prepare for in the short term;</p><p>i) You are currently working with a single payment gateway but growth in your business means you&#39;ll be expanding beyond one soon.</p><p>ii) You&#39;d rather do your own credit card tokenization but the cost and complexity of PCI compliance scares your company away meaning your data is locked in at a payment gateway limiting your flexibility.</p><p>iii) Newer customers are asking for you to support industry booking/ordering API’s and you have no way to solve that right now.”</p><p>I might have 5 or 6 bullet points in total. I pick 2 or 3 (no more) based on the profile of the company and what I therefore think are most relevant. For example, if I were targeting a SaaS platform my number i) bullet point would change to “You’re currently supporting 5 to 6 payment gateways but know that by supporting more you could grow faster”</p><p>Now we close up….</p><p>“If any of this is resonating let me know and I’ll be happy to explain more in a call or a longer email. If we&#39;re not a fit that’s ok too — if you can tell me that and why in one sentence or two that would be really helpful. I’ll try emailing you two more times over the next couple of weeks and then if I don’t hear from you after the 3rd attempt I’ll stop.”</p><p>It’s always good to add something unique at the end that reflects who you are. It can be funny or serious or industry related. Again, just be genuine.</p><p>Joe knows you&#39;re serious about getting a response but not heading for stalker territory. If he’s not interested he can either a) sign up for two more unsolicited emails or b) shoot you back a quick note and avoid the additional ones.</p><p>As I said, the goal is simply to get a response. A good salesperson wants to know what’s going on. Let’s say the CEO/VP of Sales approaches your desk and says “I just saw Acme Corp raised $10 mil in a Series B. Shouldn’t they be using us?” “I’ve talked to their Director of Finance 3 months ago and they’re not interested just yet. They want me to talk to them towards the end of the year when they’ve finished building out the sales team in Europe” A MUCH better answer than “Let me try and email them again as they never respond to me”</p><p>Why is an email that’s respectful of Joe’s time and sincere important? In Joe’s mind a sales email has 4 potential outcomes:</p><ol><li>Not an interesting service and the sales person sounds like a jerk/douche (delete)</li><li>Not an interesting service (ever or for at least 12 more months) but the sales person seems professional and respectful.</li><li>An interesting service *but* the sales person sounds like a jerk/douche</li><li>An interesting service and the sales person seems professional and respectful.</li></ol><p>The douche has no chance of getting an answer if the fit is not good today. And they have a limited chance of getting an answer even if the fit sounds interesting. No one wants to engage with someone who seems insincere or arrogant.</p><p>DONT’S</p><p>Even if you don’t like my format here are some things NOT to do.</p><p>i) Don’t have a generic first sentence that’s insincere praise for the target company. “Hi I’m Mary from Acme and I really love what you’re doing for online payments. It looks really cool. Anyway….” I see that way too often these days.</p><p>ii) Stop closing in the first email. You haven’t earned the right to go straight to the meeting/phone call next steps yet. You just want to find out if you’re even on the track.</p><p>iii) Don’t highlight very large F500 customers to startups. Make all your examples specific.</p><p>iv) No features. Force yourself to explain the solution in the language of how your prospect defines the problem. Put yourself in their team/all hands meetings. How do they talk about the problem you solve?</p><p>v) Don’t dictate the medium of communication. At most offer up alternatives and let them decide.</p><p>vi) Never send more than 3 emails to someone in the same sales process if they&#39;re not answering. It’ll just tick them off and put you in the “douche” category. No one follows up with a douche even if circumstances change in 3 months and they now are interested in what you do.</p><p>Ok, rant over. I hope this is genuinely helpful.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64633685e3ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>