302. Stop asking which AI tool to use. Ask this instead.

The internet is full of people telling non-technical founders which AI tool to use to build their product. Lovable. Claude Code. Cursor. The list grows every week.

But the tool is almost never the real problem.

In this episode, Sophia Matveeva cuts through the noise to help you figure out exactly where you are in your founder journey — and what you actually need to do next. Because the move that will save you time, money and momentum depends entirely on your stage, not your tools.

You'll learn:

• Why "which AI tool should I use?" is almost always the wrong first question — and what to ask instead
• The three types of non-technical founders, how to identify which one you are, and the mistake each one is making right now
• Why Snapchat and Airbnb — despite having unlimited budgets — still test obsessively, and what that means for you
• When AI tools hit their limit and you need professional developers

Whether you have an idea you haven't acted on yet, something you've built with AI that's gone as far as it can go, or a product that isn't growing — this episode will tell you exactly what to do next.

Mentioned in this episode: Lenny's podcast - Snapchat CEO: Why distribution has become the most important moat | Evan Spiegel

BOOK A CALL with our team to figure out your next move as a non-technical founder

https://calendly.com/sophia-matveeva/new-meeting

Timestamps: 

• 00:00 - Introduction: The real problem isn't tools, it's knowing where you are
• 03:40 - Type 1: The Idea Stage Founder - You have a validation problem
• 05:05 - Why validation determines your tech stack and build approach
• 07:30 - Type 2: The Stuck Builder - When AI tools hit their limit
• 09:48 - Why you still need professional developers 
• 12:10 - Type 3: The Stalled Founder - Testing never stops
• 14:32 - The security risk of handling data without developers
• 16:00 - Summary: Three types of founders and what each needs next

Free AI Mini-Workshop for Non-Technical Founders

Learn how to go from idea to a tested product using AI — in under 30 minutes.

Get free access here: techfornontechies.co/aiclass

Follow and Review:

We’d love for you to follow us if you haven’t yet. Click that purple '+' in the top right corner of your Apple Podcasts app. We’d love it even more if you could drop a review or 5-star rating over on Apple Podcasts. Simply select “Ratings and Reviews” and “Write a Review” then a quick line with your favorite part of the episode. It only takes a second and it helps spread the word about the podcast.

Listen to our podcast on:

• Apple

• Spotify

• YouTube

• Audible

• Pandora

Transcript: 

[00:00:00] Sophia Matveeva: One of the biggest mistakes I see non-technical founders make is actually not the one that they think they are making. They think that they have a tool problem. So should I use Lovable or should I use Claude Code or should I hire developers or should I find a technical co-founder? And actually that's almost never the real problem that they need to face. Today, I'm going to help you figure out where you are on your founder journey and what you actually genuinely need to do next.

[00:00:31] Hello and welcome to the Tech for Non-Techies podcast. I'm your host, Sophia Matveeva. If you're a non-technical founder building a tech product or adding AI to your business, you're in the right place. Each week, you'll get practical strategies, step-by-step playbooks and real-world case studies to help you launch and scale a tech business without learning to code. And this is not another startup show full of jargon, venture capital theater or tech-bro bravado.

[00:01:03] Here, we focus on building useful products that make money without hype and without code. I've written for the Harvard Business Review and lectured at Oxford, London Business School and Chicago Booth. So you are in safe hands. I've also helped hundreds of founders from concept to scalable product. And now it's your turn. So let's dive in.

[00:01:31] Hello, smart people. How are you today? You know, I got trolled online last week for saying that you cannot build a fully scalable tech product just with AI tools. I mean, that did put me in a bad mood for about an hour, but then I thought people are so passionate about the subject. How interesting and also a bit weird. Anyway, because there are so many people on the internet fiercely screaming that AI can solve all of your product problems, you might be swayed by them, especially if this is your first journey into building a tech venture. And I am here to be your voice of reason. I've been in this industry for over a decade and I've helped hundreds of founders build tech products without a technical background. And I've seen what works, what doesn't, what causes smart people to waste serious money. And also I've seen, you know, great tools come and go. And look, the people who disagree with me, they're not wrong to be excited because AI tools have genuinely changed what is possible for us, for non-technical founders and I use them myself and we teach our clients to use them too. So that excitement is real and it's justified because honestly what we teach and what we expect to see as successful results, that has changed as a result of the generative AI revolution. But

[00:02:44] excitement is not the same as a complete picture. And if you're making significant decisions about your venture based on what you've read on LinkedIn or heard from somebody who has built something impressive looking over the weekend, what you need is more context. You need to know is their product scaling? Are customers paying for the thing that they've created? And can their product hold secure data? And I bet you if you actually delve into those questions, the answers are going to be no.

[00:03:13] And in this episode and in the next one, we will cover when to use AI, the latest AI tools, and also their very real limits. But today we're going to start with something more fundamental because before we talk about tools, we need to talk about you. That's far more important surely. And where you actually are in your founder journey. In my experience, non-technical founders fall into one of three types and which type you are determines everything and determines basically what you need to do. So it determines what you should be doing right now, what you should stop doing right now, and also the mistake that you're probably going to make. So let's listen to this and let's find out which one you are.

[00:03:40] Type 1: The Idea Stage Founder - You have a validation problem

Before we dive into the three types, if you already know that you need help figuring out your next move as a non-technical founder to bring your tech vision to life, then I suggest that you book a call with us. So go to the link in the show notes or go to techfornon-techies.co and book your call there. We work with founders at every stage that I'm about to describe and we'll tell you honestly what you need right now and whether we can help you. And now let's figure out which type of founder you are.

[00:04:13] So here's step one, the idea stage founder. You have an idea that you believe in and you've been researching tools, you've been researching Lovable and Claude and no-code platforms, but you haven't built anything yet. And you're asking, should I use AI? Which of the AI tools should I use or should I get a developer or should I ask a developer friend? Should I hire somebody, should I hunt for a CTO co-founder? And this is actually my favorite stage for my clients to be at because if you set your foundations correctly here, then the rest of the journey is easier and cheaper. And also you build good habits that are going to essentially make your company and your experience better for the rest of your time doing this. But if you're wondering the how, if you're wondering how to build your app or your platform, that's actually the wrong question most of the time.

[00:05:05] Why validation determines your tech stack and build approach

The right question that you should be focusing on is, has anybody actually confirmed that they want this? Do I have confirmation that they would pay for this? Who would use it? How would they use it? Why would they use it? And only once you find out these answers should you actually start building anything, because these answers will actually determine what you need to build. So for example, if you find out that your users are going to be using your product using wifi versus mobile internet, that will literally affect your tech stack. So this is why these are not just kind of nice to have. Like if you ever want to build something really proper, like really sophisticated that you're going to charge for, that's basically going to be the backbone of a tech venture that you might eventually sell, you need to start here.

[00:05:52] So if you haven't started building anything yet, good. And don't worry about tools for now because you don't have a tool problem, you have a validation problem. So what you actually need is a simple test version that you can get in front of real potential customers. And this is where AI does come in. And so you need to create that test version before you build anything real. And this is how you find out the answers to the above questions. Honestly, this is not a shortcut. Just yesterday, I was listening to a podcast interview with Evan Spiegel, and he is the CEO of Snap. And that interview was on Lenny's podcast. We'll post it in the show notes. It was really, really good. Anyway, Snap, you know, the owners of Snapchat.

[00:06:38] They are known to be the most creative people in tech because if you think about it, they basically constantly get ripped off by Meta. So they create stories first, they created filters first, all the stuff that Instagram basically copies. And Lenny, the podcast host, he asked him, do you believe that testing is important? Is this a process that you follow? He literally asked him that. And Evan Spiegel, the founder of Snapchat said, yes, this is a really necessary process and this is exactly what we expect all of our product designers to do. So listen to me, listen to Evan. If a publicly listed company with hundreds of millions of users still tests every feature, what are you doing? You should too. So the good news is that stage one is the cheapest and most valuable stage to be at because this is where you can build those good habits correctly and basically do what they do at Snap. So get it right here and then everything else that follows is going to be easier. So that's stage one.

[00:07:30] Type 2: The Stuck Builder - When AI tools hit their limit

Now let's get to type two. Type two is what we call the stuck builder. So if you are the type two founder, you have already built something with Lovable, Claude Code, or with any other AI tool. And you're proud of yourself because you like the look of what you've just created. And you know, finally your idea is turning into an actual thing. You can see the thing. It's not just something in your head, but then you get stuck. So maybe there's a feature that you can't make work or you just, you know, you've created this thing and you don't know what to do next. So also with some tech tools, it's relatively easy to build something just for your own personal use. But then if you need to actually export it out of your computer and give it to other people, then that's super hard.

[00:08:18] So there is a limit to what you as a non-technical person can do with AI tools. So when you hit that limit, basically this is what you need to do. You need to do two things. Number one, most founders who reach this stage have skipped the important validation process that I talked to you about in stage one. So they went straight to building without doing proper user testing first. So before you go about fixing your technical problem, go back and do the work of type one. Get out in front of your real potential customers, run proper interviews as an anthropologist, not a salesperson. So you actually get real feedback about what people think about what you're doing. Find out if you're building the right thing for people who genuinely need it and are willing and able to pay for it. So find that out before you invest more time in making your product work.

[00:09:12] So after you've done that stage, after you've done that piece, you can get on to point two. Once you know, once you've confirmed what to build, then you need to work with professional developers. Because AI tools are super brilliant for building a test version, but they were not designed to build a scalable product by a non-technical founder. When you're at this stage, you have hit the natural ceiling of what a non-technical founder can build alone with AI. And this is not a failure. This is literally just a signal that, okay, you're done with this stage. You need to move on to the next stage. This is actually quite exciting, right? You're graduating to the next stage. And what does graduation look like?

[00:09:48] Why you still need professional developers (the doctor analogy)

Graduation looks like bringing in the professionals. So if you need to validate first, then bring in the professionals. And there are a lot of people screaming that developers are not needed anymore, or lawyers are not needed anymore, or basically any other profession can be replaced with AI. And maybe at some point in the future that is going to happen. But right now, today, you still need professionals because it's the professionals that understand the specific nuances of the situation. And if you are not technical, you don't even know what nuances to explain to them. You don't even know what to tell the AI to build.

[00:10:28] So, you know, I recently had to go to the doctor about some pain in my hand. And before I went to the doctor, before my appointment happened, I talked to AI extensively about what it might be. So I was saying like, this is what hurts, what might it be? Like, this is what I've been doing. But I still went to a professional, right? So AI actually did give me a clue. It said, well, we think it's repetitive strain injury and this is what we think you need to do. So I went to the doctor, the doctor said, yes, it is exactly repetitive strain injury, but the cure that the doctor gave me was different to what the AI said. This makes sense to you because you can all imagine that, okay, I go to a doctor with some sort of ailment and they give me a cure that the AI couldn't think of. So the same logic is going to apply to building your tech product. So professionals are not obsolete and yes, AI is useful. AI kind of calmed me down that I probably didn't have some sort of horrible disease, it's just repetitive strain injury. But the cure, like in order to actually get the proper cure, I needed to go to a proper trained professional who examined me properly and then gave me the cure.

[00:11:38] Okay, now let's talk about the type three founder. That is the stalled founder. So that basically means that you have a product and real people have used it, but it's not growing and you think you have a distribution problem. So you're wondering if you should run some ads or you're wondering if you should talk to influencers or should you use social media? Like should you start, should you grow your own social media or should you use somebody else's? You might've even paid money to Mark Zuckerberg to run some ads on Meta. But my dear smart person, before you spend a penny on marketing activities, answer me this. Did you do proper user testing before you built? Most of the time, the answer is no, you didn't because you didn't know how to do it properly.

[00:12:10] Type 3: The Stalled Founder - Testing never stops

That is likely where the problem lives and user testing not only gives you answers to who will use it, but also how to describe the problem to your target customers. And this is gold for marketing because this is what helps you build a marketing strategy that goes after the people that you want and speaks to them in a language that resonates. You know, if people are saying to you, yeah, okay, yeah, I will totally use this and I would use this, you know, when I'm feeling X, Y, Z, then you can literally take their words and turn that into marketing copy when you're doing your Facebook ads. This is why before you spend any money or effort on marketing, you really have to talk to your people, do the user testing and listen to them.

[00:12:56] And what the best, the most experienced, the most successful founders in the world know is that testing never stops. So Brian Chesky, the CEO of Airbnb, he talks about how he and his team speak to customers about Airbnb's features constantly. Not just when they are launching a new thing, but literally at every stage of the company. Because this validation process that I'm talking about, it's not a one time step. It is a career long skillset because every product, every feature, every iteration, that's where you need to get feedback from your customers. And it doesn't mean that your customers say, we want this, and then you exactly build that because, you know, it's a conversation with your customers, but it is also your vision. So you need to combine your vision with what the market wants. So you're not just building exactly what people tell you they want, you're combining the two things.

[00:13:52] But that dialogue, that dialogue is super, super important because if it's only about your vision, you're basically an artist. So you're creating a piece of art, you're displaying it and if nobody buys it, that's totally fine because you created it for the benefit of yourself. But if you want to run a tech company, which I'm assuming is going to be a for-profit venture, which you might want to sell, you're not making art. So you basically need to get into this process.

[00:14:32] The security risk of handling data without developers

And there's also one more thing that is specific to stage three. So if you have reached this stage and you've got some real users, okay, not a lot, but you've got some real users, if you've got some real data, that means you've probably got potentially sensitive information. And if you got to this stage doing just vibe coding and using only AI tools, which is, it's going to be creaky, but it is possible for some simpler products. If you got to this stage without professional developers, my friend, you are in dangerous territory because if you're handling payments, you're handling personal data or any sensitive information, you need professionals because if you're handling sensitive information and it can be lost or it can be hacked because you didn't do something properly, because you didn't know what you were doing, you can be in serious legal trouble and also your customers are not going to be really happy with you. So what you actually need is yes, go back to the users, carry on testing, and then get professional help building what comes next.

[00:15:30] And think about incentives. I'm not telling you this because I want you to hire my development firm because I do not run a development firm. I don't have a team of developers that I'm trying to sell to you. What we sell is courses and consulting. So we will consult you to do the best thing for you. If we believe the best thing for you is to hire developers, we won't suggest exactly which firm to use because that's going to be dependent on your unique situation and your budget. And also we're not incentivized, like we're not tied to anybody. I'm telling you to get professional help, because for non-technical founders who want to build scalable tech products, this right now is the best possible advice. When it is no longer the best possible advice, we will change our view because we are not incentivized by a development firm, we're incentivized by the success of our clients.

[00:16:00] Summary: Three types of founders and what each needs next

Okay. Now let us summarize today's lesson. There are three types of non-technical founders and where you are determines exactly what you need right now. So type one, you have an idea, but you have not built anything yet. You might think you have a tool problem or you might have a co-founder problem. You actually don't. You have a validation problem. So before you touch any tool or developer, get a simple test version in front of real potential customers and get their feedback. And this is exactly what Evan Spiegel insists is done at Snapchat. So if they test, so should you.

[00:16:36] Here's the type two founder. You have built something with AI, but now you're stuck. So that means that you probably skipped the validation step or you didn't do it properly, which means that you need to go back and do it properly. And then your next stage is going to be to bring in professional developers because AI tools are brilliant for testing. This is what we teach you to do, but they are not designed to build a scalable tech product. And now type three. The type three founder is somebody who has built a product. So you've built a product, but it is not growing.

[00:16:56] So this is what I want you to know. I want you to know that testing does not end at your product launching. So Brian Chesky talks to Airbnb customers about new features and about existing features constantly. So this validation process that I talked about for type one, that is a career long skillset that you should be using all the time. And if you have reached stage three where you have some users and you're handling some data and you don't have any developers, this is a very, very risky stage to be in, especially if you're handling payments. So fix that now, get some professionals on board. But the through line is validate, test, and listen to your market. And then at stages two and three, bring in the professionals.

[00:17:42] So that's it for today's episode. Next week, we're going to cover what we are teaching our clients about the latest AI tools. So should you use agentic AI? What is agentic AI if you don't know? Should you use Claude Code? What are the limits? And should you also use AI native development firms? So there are development firms who literally say, we will build your product with AI. Is that a good idea or is that a bad idea? Should you use them because it's going to be cheaper or is it really going to be cheaper? So if you want the answers to these questions, make sure that you subscribe to Tech for Non-Techies so you don't miss next week's episode. And on that note, I will love you and leave you. Have a wonderful day and I shall be back in your delightful smart ears next week. Ciao.