How to build an MVP without setting $17,000 on fire like me
How to build an MVP without setting $17,000 on fire like melessons learned from a time when I didn't know what no-code was or what customer discovery meant
Hey everyone, welcome to another edition of KP’s Column, a weekly advice column for founders who want proven playbooks on building products, using no-code tools, building in public and creating content. In this edition, you’ll learn about how NOT to build your MVP, followed by some advice on how to build it correctly. But first, here’s some real talk I haven’t shared that much publicly. I like to think I am somewhat of an “expert” on the domain of building MVPs *now*. I personally built nearly 15 MVPs and played a direct/indirect role in the creation of 500+ products/projects through coaching/mentoring founders in the last 4 years across all my work efforts. However, I made more mistakes than I can count in my early days. Here’s one such I poured and lost $17,000 into building an MVP for a SaaS product idea I had back in 2017-18. It was called “ClosingPage” and it was supposed to a content platform for sales reps at mid-market B2B companies. The problem? I outsourced the actual product development to an agency in India because I didn’t know how to code. Not only did they take more than 6 months to build an MVP but also cost me $17k for a shitty looking MVP 💩 Another problem? I never validated the problem/idea the right way before building out the MVP. Sure, I did a few customer discovery interviews but I didn’t follow “The Mom Test” method. (Google it!) Additionally, I had no “founder-market fit” which means I didn’t personally have any insider view of the problem I set out to solve (sales reps in mid market companies) .. so I was sitting on a bunch of assumptions. After 6 months, we finally went live to the market. Naturally, as you can predict, nobody became a customer of our MVP and I made $0 in revenue from that project. What’s worse is I had a team so we all wasted collectively wasted 6-8 months of precious time. I hit rock bottom after that experience and questioned whether I was worthy of being a tech founder at all. A huge challenge was that I had zero network back then so I couldn’t rely on any entrepreneurial friends/peers/ communities like Day One for real advice. Well, as some of you know the rest of the story, after this painful moment, I stumbled into no-code in 2018. Took it seriously and built 15+ MVPs/projects in public, became a top leader in the no-code low-code space, joined On Deck and built a massive startup network and a global Internet audience. By no means do I have all the answers but here are a few tips from my experience of sucking at building MVPs to eventually mastering the process: 6 key lessons I have for you while building an MVP:1. Treat your MVP like a food truck, not a fancy rooftop restaurant99% of the time you are likely to overthink how many features your MVP should have. I say focus on identifying one killer feature (by talking to people) and keep the scope of your MVP super lean. More like a food truck, less like a fancy eatery. This must be obvious to founders
But somehow it isn’t
Share this with those who could benefit from hearing some candid advice 👊 2. Launch a fake-door landing page to double check for demandThe social media scheduling tool Buffer is infamous for this clever hack. They launched a new landing page to test their messaging and whether people would pay or not. They placed a fake button and measured how many clicks they received. Having a fake-door or a placebo button on your landing page allows you to quickly/cheaply see if there was enough underlying demand in your problem. 3. Use a waitlist to collect emails and only obsess about the early adopters who actually *get* what you’re buildingA lot of founders make the mistake of directly unveiling their MVP to public without creating any buzz around the launch. Never open to a vague general audience. Set up a waitlist & let people share why they’re excited about your idea through filling out a survey/questionnaire. This makes it easy to filter out the hyper passionate fans and onboard them first to get feedback while you’re still refining the MVP. 4. Create an MVP or v1 using no-code toolsIn this day and age, there’s no excuse to NOT ship your MVP as early as possible. No-code is the fastest ramp to testing an idea without investing too much time/money. You can always iterate from there and build a robust v2 once you have a v1. A no-code MVP with 10 users is worth a thousand prototypes 🤔 Programming Wisdom @CodeWisdom “If a picture is worth a thousand words, a prototype is worth a thousand meetings” — IDEOHere are two resources to get you started in no-code : 5. Attract the first 1 or 10 paying customers yourself by doing things that don’t scaleEvery great startup begins with 1 paying customer. Then 10. This is the most invaluable stage of a founder journey and you HAVE to get your hands dirty. No shortcuts, no complex processes. Just onboard them manually.
Below is a screenshot of an email exchange between the legendary Stripe founder Patrick Collison and one of their early paying customers Daniel where you’ll see Patrick fixing a bug and doing customer support personally. Paul Graham also shared: At YC we use the term "Collison installation" for the technique they invented. More diffident founders ask "Will you try our beta?" and if the answer is yes, they say "Great, we'll send you a link." But the Collison brothers weren't going to wait. When anyone agreed to try Stripe they'd say "Right then, give me your laptop" and set them up on the spot. 6. Attract your technical co-founder by building in publicFinding a technical cofounder is a huge pain for so many people. That’s because they’re using a “desperate” playbook. Instead of pitching the CTO your deck, show them your momentum in public. Rally a community of early users, get them talking about your product in public & generate buzz even with an imperfect MVP. Technical cofounders want to join a party that’s popping. Show your leverage and then make the ask. Searching for a technical co-founder for your startup for a while now?
Don’t 🛑
Just use no-code tools and see for yourself if there's enough demand for your idea. And build it in public.
That will give you 10x higher change of attracting a CTO That’s all on this topic for now. Let me know if any of these tips resonated with you. Announcements:
Co-signs:
Fun stuff:
Anyway, it’s a wrap for this week’s newsletter edition. Thank you for reading and giving me a piece of your attention! If you liked this post from KP's Column, why not share it? |
Older messages
What is the coolest startup product demo you've ever seen? Here's mine 👀
Sunday, October 9, 2022
Steve Jobs famously said: “The most powerful person in the world is the storyteller.” In tech startups, however, there's a dangerous misconception that you should let the product speak for itself.
The building blocks of building in public [part 1]
Sunday, October 9, 2022
tactical tips for founders who always wanted to build in public but are stuck somehow
You Might Also Like
🚀 Google AI Updates, Top Tools, and Must-See Marketing Guides!
Friday, January 3, 2025
Explore the latest on Google's AI push, OpenAI's missed promises, and WWT's big acquisition. Plus, discover trending tools like SEOBot, Quick Mock, and expert tutorials to boost your growth
One year to change your life
Friday, January 3, 2025
Read time: 45 sec. one quick note before we dive in: our (insanely good) new years deal is almost over - snag it here before it's gone. -- It's that time of year when everyone posts the same
10words: Top picks from this week
Friday, January 3, 2025
Today's projects: LinkBoss • Travelnaut • Disney AI Poster Generator • SuprForms • GenYOU • Monibot • Crossworlds • Shy Editor • Helpello • Essembi • Page Roast • PowerDreamer 10words Discover new
Issue #133: Building $1K-$10K MRR Micro SaaS: Asset Management, AI-Powered Design of Marketing Graphics, AI Agent …
Friday, January 3, 2025
Build Profitable SaaS products!! ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
#38 Three Subtleties from the Busy Alleys of SaaS Growth
Friday, January 3, 2025
Enriching common knowledge into actionable SaaS insights for 2025 ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
The Biggest Opportunity of 2025 — The Bootstrapped Founder 367
Friday, January 3, 2025
Now that we're starting a new year, let's look ahead at the opportunities and challenges facing the software business world in 2025. ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏
🚀 2025 is your year for change—take the leap
Friday, January 3, 2025
Freedom isn't free, but it's worth every step. Join the 5-day challenge today! Hi Friend , It's a new year—the perfect time to start fresh, take bold steps, and build the life you've
European deeptech predictions for 2025
Friday, January 3, 2025
+ Checkout's latest results; climate and healthtech predictions View in browser Sponsored by Zoom Good morning there, 2024 served up a mixed bag for European deeptech. On the gloomier side some of
SaaSHub Weekly - Jan 2
Thursday, January 2, 2025
SaaSHub Weekly - Jan 2 Featured and useful products UserVoice logo UserVoice UserVoice integrates easy-to-use feedback, helpdesk, and knowledge base management tools in one platform that empowers users
BSSA #112 - Working with influencers for your app
Thursday, January 2, 2025
January 02, 2025 | Read Online Hey! First, Happy New Year! I hope you had a wonderful year-end and that 2024 was gentle with you. If you've had any problems or things that didn't work, remember