Skip to main content

So you want to start a mobile app business...

I wrote this letter to a friend of mine who was looking for a technical co-founder for a mobile-first
startup.  I figured it might be a good idea to share this with my readers (after a bit of cleaning up).

Letter to Chris:

Hey man!  I am glad you got your entrepreneurial juices flowing.  So here is what I can tell you about exploring your idea further.

First of all there are a lot of ideas floating around and a bunch of people are building apps, however there are very few *good* ideas.  I trust that you have a good idea because I know you are a smart guy.

How do you prove to people that it's a good idea?  Actually building stuff is just a part of the equation.  Getting it connected to customers is the bigger part.  Think about it as if you were looking for oil.  Imagine you approach an engineer and say, "I need to drill for oil!" Drilling for oil is useful but where and how much oil is there is the bigger question.

How does this relate to your business?  First thing first - get in touch with people who would use it and buy it.  If you can't find those people, guess what - there ain't no oil there!

When you find those people the next question is: what's your plan for monetization?  Is it ad-supported, is it supported by people paying for a premium version or something else?

I don't know much about ad-supported things.  Those generally compete for your attention and there is a fair amount of psychology that goes into that, however, let's go with the app that people actually want to pay for.  In this case it's a little simpler to figure out if there is oil and how much oil there is.  Again get back to your potential customers and see what they think.  If you can't find 5-10 people who will spend time talking to you about it and then at the end won't say: "yeah I'd give you some cash for that," again, “the oil field” isn't that big and it might be time to go back to the drawing board.

Pro tip: when you talk to your potential customers you can grab software online that will sketch the app for you.  It's not going to do anything functionally; it will just be screens with outlines.  You can use http://proto.io/ or FluidUI for almost no money to just create a few screens.  Run them by the your potential customers, you will be surprised how much additional feedback you will get from just giving them something to look at.

So now you are thinking - "WTH!  I need to spend all this time to just get a basic app running, and I don't even have an app.  That's too long and boring!"  Actually what you did do there is some really good market research.  At the end of the exercise you will have (a) a few people to beta test the app, (b) maybe even a couple that will help you fund the development and (c) a sketch of what you want that's been vetted by your early adopters.  This is a well-defined idea and at that point you are actually an entrepreneur with a definite plan.

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!

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…