3 psychological ways to know what app you should build

3 psychological ways to know what app you should build. So how do you make it so psychologically easy for someone to actually pull out their credit card and pay for something that you built? So I'm gonna talk about three concepts that you should know if you wanna be successful in app building right now. So Steve Jobs talks a lot about how people don't actually know what they want until you give it to them. And while I think that's partially true, I think that people do know what they want, they know which problems they want solved, they just don't know who's gonna solve them or how they're gonna do it. So for a little bit of context, my name is Jack, I'm 20 years old. I currently run the largest vibe coding & startup community in the world. I've built multiple apps and I'm currently working at a startup that does over $9 million a year in revenue. And I really just nerded it out on one of my niche obsessions. So the first concept is substitution and it's finding out what people are already paying for, but then finding problems that they're still having. So I talk about this all the time, but Cal AI did this very well where they identified that people are already paying for my fitness pal, but there's a lot of friction where people have to constantly be entering every single thing that they're eating. So they remove that barrier with AI by allowing them to take a photo of anything that they're eating. Probably the number one mistake that I see people constantly making is that they're trying to make their own market. They're trying to make a market that doesn't exist yet, but it's 10 times easier to just build an app for a specific demographic who would already pay for what you're making. No 2 is a little bit more AI specific and I talk about this a lot as well, but it's building vertical AI tools. So these exist because Chat gpt, Claude, these general LLMs are bad at very specific industries. So if you're a lawyer, you probably aren't gonna use Chatgpt to help write up a contract. If you're in accounting, you aren't gonna use Chat gpt to help balance your books. I made a video on exactly how you can build this, but you build a tool that is good at one specific thing and then you cater to that industry. So you might be thinking that ChatGPT or Claude is only gonna get better and be able to do whatever your vertical AI tool does, but as the model gets better, it's only gonna make your tool better because you're running on that model. And then the third concept isn't really technical at all, but it's understanding why people would actually buy something. So people are gonna pay for your app for two reasons: it's either gonna solve a pain point for them or it is gonna give them some sort of identity. So it is significantly easier to solve a pain point for someone like we just mentioned with Cal AI than it is to give someone identity. You want to have a good mix of both. A really good example of this is notion. People are paying for notion because they wanna feel organised and they wanna feel like they have their life together. So if you can nail a really strong pain point and then add an identity layer on top of it, that is how you make people pay for something without even thinking about it. If you wanna learn more about this stuff or talk more about it, join the discord or the school community.