TRANSKRIP 🔗
WEBVTT
00:00:00.239 --> 00:00:09.199
Once your friends know you're a developer, they're probably going to pitch you their app ideas, or their game ideas, or their cool website ideas.
00:00:09.439 --> 00:00:11.919
Most of these ideas are going to be terrible.
00:00:12.160 --> 00:00:17.920
A few will be decent, and once in a while you'll come across some truly great ideas.
00:00:18.320 --> 00:00:23.039
So, how do you evaluate these ideas and how do you respond to these pitches?
00:00:23.199 --> 00:00:28.960
And how do you let people down gently when you don't want to take on their idea?
00:00:29.199 --> 00:00:33.280
This is what we're going to discuss in today's episode of Dev Questions.
00:00:41.119 --> 00:00:44.560
Welcome to the Dev Questions podcast with Tim Corey.
00:00:45.200 --> 00:00:48.399
Software development is more than just writing code.
00:00:48.560 --> 00:00:50.000
So let's talk about the rest of it.
00:00:50.240 --> 00:00:54.880
Specifically, let's talk about evaluating app pitches from others.
00:00:55.119 --> 00:00:56.719
And let's start with the basics.
00:00:56.880 --> 00:00:58.719
Most pitches are terrible.
00:00:59.039 --> 00:01:00.960
That isn't the fault of your friends.
00:01:01.119 --> 00:01:03.039
They just don't know what they don't know.
00:01:03.200 --> 00:01:05.200
And this is a great place to start.
00:01:05.359 --> 00:01:13.599
Rather than just shooting down their idea and telling them no or that it's a horrible idea, provide a little education with your response.
00:01:13.840 --> 00:01:19.120
And that way you can help them understand why they should be saying no too.
00:01:19.439 --> 00:01:24.400
For example, not long ago I had a friend reach out to pitch me a game idea.
00:01:24.560 --> 00:01:31.840
He had a multi-page design document for the game that he expected to take about a year for one developer to build.
00:01:32.079 --> 00:01:36.959
After looking over the document, I explained how complicated the game actually was.
00:01:37.200 --> 00:01:41.760
I talked through what each part would take in a bit of detail.
00:01:41.920 --> 00:01:46.480
Not a lot, but just enough to understand, oh, that's that's a lot of work.
00:01:46.719 --> 00:01:56.560
In the end, it was clear the project required multiple developers, a designer, and then other people as well, such as voiceover and the rest.
00:01:56.799 --> 00:02:03.920
So instead of saying no, I explained why the conclusion was no, why it just wouldn't work that way.
00:02:04.879 --> 00:02:07.760
Not long ago, someone else pitched me an app idea.
00:02:07.920 --> 00:02:14.240
Their idea was simple enough, but their proposal was that I would do all the work and they would get half the profits.
00:02:14.479 --> 00:02:17.599
The app was a mobile app going into a crowded market space.
00:02:17.840 --> 00:02:25.360
I explained how difficult it would be to stand out from the crowd and how the odds were stacked against the success of the app.
00:02:25.599 --> 00:02:34.879
I
Load full transcript
pointed to other apps that I had been commissioned to build that were technical successes and overall failures because of the lack of traction in the market.
00:02:35.280 --> 00:02:41.439
I then discussed the inequity of me doing all the development work and them just providing the idea.
00:02:41.680 --> 00:02:44.800
Ideas are a lot cheaper than actual work.
00:02:45.360 --> 00:02:54.159
I outlined all the work that I would need them to do and how I would still require a bigger share than just half.
00:02:54.800 --> 00:03:00.800
And that's only after they could provide a clear plan on how they intended to market the app.
00:03:01.120 --> 00:03:15.199
By explaining the reality of the situation and then by showing them how much work that they would have to do, it made it easier on them to say no from their end because, and I was already saying no from my end.
00:03:15.360 --> 00:03:19.599
But but by that point they understood, yeah, I'm saying no too, right?
00:03:19.759 --> 00:03:25.919
So we're kind of mutually saying, yeah, this isn't a good idea, just because it it's it's a lot of work.
00:03:26.159 --> 00:03:30.800
And often people think that once they have the idea, they're done.
00:03:31.039 --> 00:03:41.199
And yet they can kind of reap the rewards of telling somebody else to do this and out pops an idea and it somehow makes them money.
00:03:41.439 --> 00:03:44.560
Um they just don't know what they don't know.
00:03:44.719 --> 00:03:54.319
And so helping to educate them helps to kind of ease that no from being a harsh no to a, oh, that makes sense.
00:03:54.560 --> 00:04:08.319
And it also helps kind of round or like head off any future pitches they might have where they go, oh wait, yeah, it's gonna take more than that, or I don't really want to spend as much time working on this idea.
00:04:08.479 --> 00:04:11.439
I just want to pass it off to somebody else, and that's not gonna work.
00:04:11.759 --> 00:04:18.639
So those are just a couple of the dozens of examples I have personally of handling pitches from my friends and my colleagues.
00:04:18.879 --> 00:04:24.319
So let's talk through some of the important things that I use to evaluate any new pitch.
00:04:24.720 --> 00:04:26.639
Because this is gonna happen a lot.
00:04:26.879 --> 00:04:29.519
Number one, is it even feasible?
00:04:29.759 --> 00:04:35.600
Like sometimes you get app ideas where you're like, yeah, that's not really possible.
00:04:35.839 --> 00:04:36.079
Right?
00:04:36.240 --> 00:04:44.319
Like it's just not, you know, the technology is not there, or the limitations of technology require that I can't do that.
00:04:44.480 --> 00:04:54.000
You know, for example, um, for a long time, I wanted to create an alarm clock for my iPhone because I think the the iPhone alarm clock is dumb.
00:04:54.560 --> 00:04:58.720
Um, there's just so many things that I wish I would I would like differently.
00:04:58.959 --> 00:05:07.199
But for a very long time, Apple wouldn't allow you to actually build an alarm clock because it had to run in the background and all this other stuff.
00:05:07.279 --> 00:05:09.839
And they just didn't allow those features.
00:05:10.000 --> 00:05:12.240
Well, for a long time, it just wasn't feasible.
00:05:12.399 --> 00:05:18.000
So if someone came to me, I've had this happen, they say, well, I want to build a different alarm clock for the iPhone.
00:05:18.800 --> 00:05:20.160
Nope, can't do it.
00:05:20.319 --> 00:05:21.839
It's just not feasible.
00:05:22.160 --> 00:05:26.879
Of course, now it is, and it's still my radar of things that at some point I like to do.
00:05:27.120 --> 00:05:29.920
But you know, if it's not feasible, then you're done.
00:05:30.079 --> 00:05:32.959
Just say, you know what, here's why it just won't work.
00:05:33.120 --> 00:05:36.639
Uh number two, do I have time for this?
00:05:37.680 --> 00:05:44.879
This is a harder question for developers who often have um, you know, bigger eyes than their stomach kind of thing.
00:05:45.040 --> 00:05:48.720
You know, I remember when I was growing up, that was always a phrase I heard a lot.
00:05:48.879 --> 00:05:57.759
Well, you know, if you if you took a lot of food on your plate and then just couldn't finish it, you were too full, you people would tell you, well, you had your eyes were bigger than your stomach.
00:05:58.079 --> 00:05:59.680
The same is true for developers.
00:05:59.839 --> 00:06:05.120
We often think, oh, that's a weekend project, which my wife knows at this point to laugh at that.
00:06:05.279 --> 00:06:10.000
Any kind of you know, project that I say it's a weekend project, yeah, it's gonna take months to do.
00:06:10.319 --> 00:06:13.519
Because it's you you always forget about the complexity.
00:06:13.680 --> 00:06:15.360
You always kind of gloss over that.
00:06:15.600 --> 00:06:20.879
So part of this is just evaluating honestly what it's actually going to take.
00:06:21.199 --> 00:06:26.319
But then also, do you actually have the side, you know, side time to do this?
00:06:26.800 --> 00:06:29.680
What are you giving up to say yes to this?
00:06:30.000 --> 00:06:32.000
Because your time is always full.
00:06:32.240 --> 00:06:37.759
Whether you know it or not, every 24 hours of a day, you use all 24.
00:06:38.000 --> 00:06:46.639
Just sometimes you use them for watching Netflix or sleeping or wandering out in the in the wilderness just to kind of have fun.
00:06:47.120 --> 00:06:52.240
You're gonna have to give up something in those 24 hours to be able to do this project.
00:06:52.480 --> 00:06:53.920
Are you willing to give that up?
00:06:54.160 --> 00:06:55.600
Do you have time for this?
00:06:55.920 --> 00:07:07.600
And by saying yes to this, you're probably saying no to almost everything else when it comes to other pitch ideas or other ideas you have of your own.
00:07:07.839 --> 00:07:12.800
So are you willing to say no to a whole bunch of things in order to say yes to this?
00:07:12.959 --> 00:07:14.319
Do you have time for it?
00:07:14.560 --> 00:07:18.639
Number three, is the monetary split fair?
00:07:18.800 --> 00:07:26.079
Now, this is not the time to have a detailed negotiation on percentage points and all the rest.
00:07:26.319 --> 00:07:31.199
But just take a rough sketch, look at it, and go, that doesn't make sense.
00:07:31.360 --> 00:07:36.800
Like my example of I have the app idea, therefore I get 50% of the profits.
00:07:37.120 --> 00:07:39.120
No, no, that's not fair.
00:07:39.279 --> 00:07:44.240
Um, if I'm gonna do all the work, then I'm gonna get most, if not all, the profit.
00:07:44.560 --> 00:07:50.639
Because I can't expect to just say that you know an idea is worth that much.
00:07:51.040 --> 00:08:00.800
So instead, we're gonna have to talk about how you're gonna contribute a lot more in order to meet some reasonable percentage for you too.
00:08:01.120 --> 00:08:03.759
So is a monetary split fair?
00:08:04.480 --> 00:08:13.279
Talk about the process, talk about how much work you put in versus them and what's what's really fair.
00:08:13.360 --> 00:08:16.319
Um, and just see if there's even a common ground here.
00:08:16.399 --> 00:08:23.680
Because if they say, you know what, no, I'm not gonna give you more than 50%, then it's probably not worth it if you're doing all the work.
00:08:24.079 --> 00:08:32.720
Now, here's the other thing when it comes to splitting money, this is where you're talking about potential partnerships.
00:08:34.720 --> 00:08:39.679
Try, if at all possible, to avoid partnerships.
00:08:41.519 --> 00:08:44.639
Just don't do it, if at all possible.
00:08:45.519 --> 00:08:51.200
So many companies struggle and fail because of partnerships.
00:08:51.679 --> 00:08:54.879
Where there's two people, it's like a marriage.
00:08:55.120 --> 00:09:04.080
You're marrying your business partner in a in a you know, business way, where you're tied to them and how they work.
00:09:04.240 --> 00:09:11.120
And at some point, you know, at first it's sunshine and roses, later on, you're like, you know, you're breathing too loud, right?
00:09:11.279 --> 00:09:29.600
So at some point, you're going to get frustrated where something's gonna come up and you don't like their decision, or you don't like how they're doing things, or they don't you don't think they're putting enough effort in, and all of a sudden you're frustrated at each other and the business can fail just because of that, or the partnership can fail because of that.
00:09:29.919 --> 00:09:34.159
So I would encourage you to not go into a partnership when doing this.
00:09:34.480 --> 00:09:48.320
It should be something where, like, if a person comes to me and pitches and they say, I want to build this, and I, if I were to say, yes, I think that's a good idea, then what I would do is talk through the fact that we're gonna do it under my business.
00:09:48.559 --> 00:09:52.720
And you will have, you'll be the client, essentially.
00:09:53.039 --> 00:09:57.679
But
instead of paying me to do this, we'll do this in percentages.
00:09:58.000 --> 00:10:04.639
So that's how I would pitch it so that um we're this is not a partnership.
00:10:04.960 --> 00:10:13.679
This is a uh a business and client relationship, because those are much more easily separated.
00:10:14.159 --> 00:10:18.799
So that kind of leads into number four, which is who makes the final decisions.
00:10:19.200 --> 00:10:24.000
You need to understand and be very clear about who makes the final decision.
00:10:24.159 --> 00:10:34.720
Because if they come to you an idea and their idea is two sentences long, which is very common, there's a lot of work that has to be done to flesh out that idea.
00:10:35.120 --> 00:10:45.759
And at some point, the two of you are going to disagree about where which direction to go with one of those fleshed out points.
00:10:46.320 --> 00:10:47.679
Who makes a final call?
00:10:47.840 --> 00:10:50.080
It can't be an equal partnership.
00:10:50.320 --> 00:10:58.639
Again, partnerships are problems, and you've got to have a clear pecking order where you say, this person's in charge.
00:10:59.039 --> 00:11:00.879
This person makes the final call.
00:11:01.120 --> 00:11:08.559
And usually it's the person who has the most to gain or lose based upon making that call.
00:11:08.960 --> 00:11:13.200
So that's important to know up front.
00:11:13.519 --> 00:11:17.360
Number five, is there a market for this product?
00:11:18.000 --> 00:11:20.720
It does not matter how great the product is.
00:11:20.879 --> 00:11:23.759
It does not matter how cool the idea is.
00:11:23.919 --> 00:11:38.799
It does not matter if it solves all kinds of problems, if it's not a market for it, or if you can't get it to that market, if you can't prove that you can get it to that market, it's just not gonna be valuable.
00:11:39.039 --> 00:11:55.360
If you ever want to kind of prove this, go to the app store, go to the Android App Store or the iOS App Store and look through not the home page, not the top 50 page of games or apps.
00:11:55.679 --> 00:11:59.919
Do a search and search for basically any topic.
00:12:00.080 --> 00:12:09.679
And then just scroll through all of the options because you will find that there are lots of solutions.
00:12:09.840 --> 00:12:11.840
Search a simple one, to-do list.
00:12:12.320 --> 00:12:15.279
Figure out how many apps do to-do lists.
00:12:15.440 --> 00:12:31.200
And there's gonna be some big market players in there too, where they have word of mouth, they have major advertising budgets and all the rest, and can kind of force their way to the front of the line in front of little old you who has basically no marketing budget.
00:12:31.840 --> 00:12:34.799
So is there really an app, a market for this product?
00:12:35.039 --> 00:12:37.519
And can you make a dent in that market?
00:12:37.840 --> 00:12:50.559
Can you get in front of people and say, yes, this is more valuable, and have them say, Yes, I want this product over all the hundreds or thousands of other products on the market.
00:12:50.799 --> 00:12:57.039
There are thousands of apps that have one or fewer users.
00:12:57.360 --> 00:13:03.759
There are thousands of apps that have never been downloaded by an actual user other than the actual owner.
00:13:05.440 --> 00:13:09.759
Not every app succeeds just because it got to the app store.
00:13:10.480 --> 00:13:14.080
You need to have a plan for marketing it.
00:13:14.480 --> 00:13:16.240
And you know what?
00:13:16.480 --> 00:13:22.480
If you don't have a market for it, or if you can't figure out how to break in, you probably won't succeed with that app.
00:13:23.200 --> 00:13:25.840
Number six, and this kind of goes along with this.
00:13:26.240 --> 00:13:29.840
What would be the outcome if the app failed?
00:13:30.159 --> 00:13:41.039
So you put in this work, you decide, yes, we're gonna do this, you build this app, whatever it is, a web app, or if it's a desktop app, or if it's a mobile app, or whatever it is, game.
00:13:41.360 --> 00:13:45.600
You build this thing and you spend, you know, you estimate how much time you're gonna spend.
00:13:45.679 --> 00:13:47.440
Let's say you're just gonna spend six months on this.
00:13:47.600 --> 00:13:48.799
You spend six months on it.
00:13:48.960 --> 00:13:59.360
Your partner in the meantime has built up a marketing campaign and worked on that and hired contractors to design flyers or whatever they're gonna do.
00:13:59.600 --> 00:14:05.759
And you've gone through the process, and at the end of it, you have five users.
00:14:06.559 --> 00:14:06.879
Okay.
00:14:08.000 --> 00:14:09.440
What happens then?
00:14:09.840 --> 00:14:11.919
Is that going to be devastating to you?
00:14:12.159 --> 00:14:14.799
Because if the answer is yes, you're gambling.
00:14:14.879 --> 00:14:17.919
You're not actually doing good development.
00:14:18.080 --> 00:14:20.159
This is a this is too much of a gamble.
00:14:20.559 --> 00:14:27.039
So you need to know can I make it if this does not succeed?
00:14:27.279 --> 00:14:37.440
Don't look at you know the top app in the category and go, oh, you know, this app just sold for a million dollars, or this app just has 500,000 users.
00:14:37.600 --> 00:14:40.080
Look at the apps that have five users.
00:14:40.720 --> 00:14:43.200
Could you survive if that's the case?
00:14:43.440 --> 00:14:46.799
Are you putting too much money and too much effort into this?
00:14:47.360 --> 00:14:50.639
Or are you saying, you know what, I can take a chance.
00:14:50.799 --> 00:14:53.440
I can I can put a little bit of money in this and it won't hurt me.
00:14:53.600 --> 00:14:55.759
I can put some time in this and it won't hurt me.
00:14:55.919 --> 00:14:59.840
And if I get nothing else out of it, I have a good portfolio project, right?
00:15:00.159 --> 00:15:02.879
If that's the case, cool, go for it.
00:15:03.440 --> 00:15:10.080
Number seven, do I have the experience necessary to build this type of
app?
00:15:11.440 --> 00:15:14.639
It takes a lot of work to build new things.
00:15:14.879 --> 00:15:22.399
And often you'll find that there's a lot more to different areas that you haven't done than you thought initially.
00:15:22.559 --> 00:15:28.080
Um, you know, example of this simple example might be maybe you've never dealt with authentication before.
00:15:28.320 --> 00:15:32.960
That can be a big hurdle because not just slap a username and password in front of that.
00:15:33.039 --> 00:15:40.639
How do you do password resets and how do you do locked-out users and how do you do uh lost passwords and so many other things?
00:15:40.720 --> 00:15:42.480
How do you do two-factor authentication?
00:15:42.559 --> 00:15:43.919
There's tools out there for that.
00:15:44.240 --> 00:15:50.559
But that's a simple example of if you haven't done it before, that's gonna be a bigger hurdle.
00:15:50.720 --> 00:15:53.840
Learning how to do it first and then implementing it in your app.
00:15:54.159 --> 00:15:57.679
So, do you have the experience necessary to build this type of app?
00:15:57.919 --> 00:16:05.360
Because sometimes that just means it's a bigger unknown, which expands your timeline and your expenses.
00:16:05.600 --> 00:16:11.120
Number eight, is this app reliant on things outside of your control?
00:16:12.879 --> 00:16:15.039
This is one people don't often think about.
00:16:15.200 --> 00:16:17.519
Um, a big one right now is AI.
00:16:18.000 --> 00:16:23.759
Let's just say you decide I'm gonna create an AI chatbot, which don't do that.
00:16:23.840 --> 00:16:25.600
That's just a wrapper for chat GPT.
00:16:25.679 --> 00:16:30.240
But let's say you create this wrapper for chat GPT that's somehow different or better.
00:16:30.320 --> 00:16:33.759
You put a prompt in there that makes the AI talk like a pirate.
00:16:34.000 --> 00:16:35.360
Okay, whatever.
00:16:35.919 --> 00:16:44.879
You're reliant now on ChatGPT, which means that if they decide to change their API, you're in trouble.
00:16:45.039 --> 00:16:51.120
Or if they decide to raise their rates, which they have done, you're in trouble.
00:16:51.440 --> 00:16:55.679
So is your app reliant on things outside of your control?
00:16:56.559 --> 00:17:01.279
One that I would love to do is, you know, I play fancy football.
00:17:01.440 --> 00:17:03.440
I just did my draft recently.
00:17:03.600 --> 00:17:13.440
Um, you can kind of tell you when my this video has been recorded, but um, I love fancy football and I love the idea of getting that data and doing different things with that data.
00:17:13.599 --> 00:17:16.240
Maybe not a fancy football app, but something different.
00:17:16.480 --> 00:17:22.000
The thing is, that data, I'd be completely reliant on a different company providing it to me.
00:17:22.160 --> 00:17:24.000
What if they decide to go out of business?
00:17:24.160 --> 00:17:26.240
Does my app go away?
00:17:26.480 --> 00:17:28.400
That could be a real risk.
00:17:28.640 --> 00:17:31.039
And is it a risk I'm willing to take?
00:17:31.279 --> 00:17:34.240
So is your app reliant on things that are outside your control?
00:17:34.720 --> 00:17:39.440
Number nine, do we know enough about this field?
00:17:40.400 --> 00:17:51.759
One of the benefits here is if your friend is pitching you an idea, sometimes, not always, but sometimes they know a lot about the field and know where a gap is.
00:17:51.920 --> 00:17:55.519
And they can pitch the idea for how to fill that gap.
00:17:55.920 --> 00:17:58.960
But maybe they don't know quite enough about the field.
00:17:59.039 --> 00:18:10.400
And again, Dunning Kruger raises its ugly head and they might think they know, or you might think you know enough about the field when you don't have any experience at all in the field.
00:18:10.720 --> 00:18:18.640
And that's a big risk for your app because you're gonna build something that isn't gonna actually work well.
00:18:19.279 --> 00:18:28.160
So make sure you know enough about the field to actually understand what the users really want.
00:18:29.279 --> 00:18:34.799
Number 10, can I get a proof of concept to market fast enough?
00:18:36.160 --> 00:18:41.680
Maybe the app is gonna take a year to build, but can you get a proof of concept out to the market in three months?
00:18:41.920 --> 00:18:47.920
A beta version or something that you can put in front of users and make sure you validate the idea?
00:18:48.319 --> 00:19:03.680
Can you build a sample app that doesn't actually work, but can you kind of walk people through so that you can understand if it's even valuable, if it's going to be valuable enough, and if people are saying, yes, take my money, or if they're like, yeah, it's cool.
00:19:03.839 --> 00:19:06.000
I might, I might use that if it's free.
00:19:06.240 --> 00:19:08.079
Like, that's a big difference.
00:19:08.319 --> 00:19:10.880
And the sooner you know that, the better.
00:19:11.200 --> 00:19:20.559
So it's perfectly fine to have a clear no-app ideas policy for people where you auto-reject every idea they have.
00:19:20.880 --> 00:19:23.279
Some people do that because you know what?
00:19:23.440 --> 00:19:29.119
It's just you get inundated sometimes with the amount of things that people want to do.
00:19:29.599 --> 00:19:35.920
But people with experience in industry know where the gaps are and what might fill them.
00:19:36.160 --> 00:19:42.000
Every once in a while, you're gonna come across a really good idea that could have a big impact.
00:19:42.559 --> 00:19:50.240
Just make sure that your friend has contacts in the industry for marketing the app and the idea is sound and that you're prepared to take on this app.
00:19:50.400 --> 00:20:00.160
Go through a list of 10 questions to ensure that you're giving this decision the proper evaluation before committing to it being a possibility.
00:20:00.400 --> 00:20:05.599
Now just remember that once you say yes, you have an even bigger list of tasks to undertake.
00:20:05.759 --> 00:20:15.599
This list is not about what to do once you say yes, because that list includes creating a business, drawing up contracts, getting legal counsel, and a lot more.
00:20:15.920 --> 00:20:20.079
Saying yes is a lot of work, but it can be rewarding.
00:20:20.319 --> 00:20:24.240
Just make sure you pick the right opportunity before saying yes.
00:20:24.559 --> 00:20:25.599
Thanks for listening.
00:20:25.839 --> 00:20:28.000
As always, I am Tim Corey.
00:20:28.319 --> 00:20:31.279
Thank you for joining us for this episode of Dev Questions.
00:20:31.440 --> 00:20:39.839
When you're ready to learn to think and code like a professional developer, head over to I am TimCorey.com and enroll in a course.