Skip to main content

Getting early sales

I wrote this to a friend of mine who is creating a startup and I figured that it's worth sharing:
...My advice to get early sales is to figure out what your market really is: 1) who is willing to pay for this stuff 2) where are those guys spending their time? 3) are there partners who are in the same verticals who you can leverage? I would suggest getting hands on with people and investing into good flexible sales people first. Early in the game you don't know how people feel about your software. The best way to find out is to meet them in person. When you do a demo you can sense when people start drifting off. You can see how people react when you present them pricing options. I don't believe you "create a market" as a startup. I believe you find a market that emerging or that already exists. What is your market? Until you can put quotas on sales people you probably don't know for sure. Once you have an educated guess for question #1 and #2 I would suggest that you find a trade show. That's a great way to get in front of a lot of people right away. You can get a modest booth or a table top space and also walk the expo floor. Meet people, talk about your software, set up some meeting for after the show. 70% of communications is non-verbal and you can get a pretty good scientific sample at a big show.
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…