📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past behaviour, not your idea, so you can't be lied to. If a founder reads one thing before talking to a single customer, it's this.
From
momtestbook.com
by Rob Fitzpatrick
~130 pages
- Talk about their life, not your idea.
- Ask about specifics in the past, not opinions about the future.
- 'That's so cool, I'd totally buy it' is a compliment, not data, dig for commitment and evidence.
Open
momtestbook.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A short, free primer straight from the person who coined the term, useful when someone on your team thinks an MVP just means a cheap version of the full product. It clarifies that an MVP can be as small as a landing page or a manual service as long as it produces real learning. Read it to reset the definition before you scope anything.
From
Lean Startup Co.
by Eric Ries
~8 min read
- An MVP is about learning, not about a smaller product
- It can be a page, a video, or a manual service
- Customers must take a real action for the test to count
Open
leanstartup.co →
📖 Book
✓ Link checked
Free
Intermediate
Why we picked it
Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary source, free in full. The antidote to over-planning your roadmap.
From
Basecamp / 37signals
by Ryan Singer
free online book
- Work in short cycles with a cool-down between them.
- Fix time, vary scope, use 'appetites,' not estimates.
- Make bets, not plans; no runaway backlog.
Open
basecamp.com →
📖 Book
✓ Link checked
Free
Beginner
Why we picked it
Free to read online, with chapters like "Build Less" and "Half, Not Half-Assed" that name your exact trap. It argues that cutting scope is a feature, and that the version with fewer things done well beats the bloated one. A fast, opinionated read you can skim straight to the chapters that sting.
From
Basecamp / 37signals
by Jason Fried, David Heinemeier Hansson (37signals)
Free online, ~4 hr
- Build half a product, not a half-built product.
- Every feature you add is one more thing to maintain and explain.
- Deliberately underdo the competition on scope.
Open
basecamp.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The two ways to fake a product while you test real demand. Do the work by hand in the open (concierge), or hide the manual work behind a front so users think it is automated (Wizard of Oz, the way Zappos started). Clear examples of when each one fits.
From
LogRocket
~12 min read
- Concierge is transparent, Wizard of Oz is hidden.
- Both let you sell before you build.
- Match the method to what you are unsure about.
Open
blog.logrocket.com →
📄 Article
✓ Link checked
India
Free
Beginner
Why we picked it
This gives concrete cost ranges by MVP type, from a landing page build up to a full app with backend and integrations, which is useful for calibrating what a quote should look like. It is written by an agency, so read it for the ballpark and the scope tiers, not as a neutral price. Use its bands to sanity check whoever you ask, then still get your own three quotes.
From
Riolabz
by Riolabz
- Costs scale sharply from landing page to full backend build
- Cost bands help you spot a quote that is wildly off
- Treat any agency figure as a starting point, not gospel
Open
riolabz.com →
📄 Article
✓ Link checked
India
Free
Beginner
Why we picked it
This is written from a Bengaluru agency's actual project experience, so the numbers reflect what an India-based team charges rather than a US rate card converted down. It grounds the whole conversation in real tiers: a lean prototype at $1,000 to $3,000, a production MVP at $3,000 to $8,000, a B2B SaaS MVP at $8,000 to $15,000, plus an honest note on hidden costs like maintenance and hosting. A good first read to calibrate whether a quote you have been given is in the sane range before you negotiate.
From
Startupbricks
by Suresh, Startupbricks
~15 min read
- MVP cost is a range, not a figure: expect roughly $3,000 to $8,000 for a real production MVP built with an India-based team, more for AI or marketplace complexity.
- India developer rates in the $25 to $60 an hour band are why the same build costs a fraction of a US or UK quote, so compare like for like when a vendor's number looks high.
- Budget another 15 to 25 percent on top of the build for maintenance, hosting, and post-launch iteration, because those costs are real and usually left out of the headline quote.
Open
startupbricks.in →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
The number that blows a build budget is rarely the first quote, it is the additions that pile on afterward. This piece explains how vague requirements let scope (and cost) creep, and how a written spec with an explicit out of scope list protects you. It gives you the vocabulary to hold a vendor to what was agreed.
From
DECODE
by DECODE
- Vague requirements are the root cause of budget overruns
- Write down what is explicitly out of scope, not just in
- Handle new requests as priced change requests, not freebies
Open
decode.agency →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Once no-code has carried you to traction, this is a grounded guide to building the early team you eventually need, including that first engineer. It helps you time the switch from doing it yourself to hiring, which is exactly where the short answer points. Save it for when the product clearly works.
From
Lenny's Newsletter
by Lenny Rachitsky
- Hire when execution, not clarity, is your bottleneck.
- Early hires set how the whole company will build later.
- Wait for real traction before adding permanent engineering cost.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The idea that started the lean movement, from the person who coined it. No business plan survives first contact with customers, so stop defending assumptions at your desk and go test them on real people. Short, blunt, and foundational.
From
steveblank.com
by Steve Blank
~8 min read
- Your idea is a set of guesses until customers test it.
- Facts live outside the building, not in your plan.
- Expect to be wrong, and plan to learn from it.
Open
steveblank.com →
Why we picked it
The book that gave the world 'MVP', 'build-measure-learn', and 'validated learning'. It reframes a startup as a series of experiments, not a bet, the mental model everything else in this category builds on.
From
theleanstartup.com
by Eric Ries
~330 pages
- Progress = validated learning, not features shipped.
- Build the minimum that produces a real learning loop.
- Decide pivot-or-persevere on evidence, on a schedule.
Open
theleanstartup.com →
Why we picked it
The permission slip to recruit users by hand, do things manually, and deliver 'insanely great' experiences to your first few customers. The cheapest, most honest way to validate demand is to go get it one person at a time.
From
paulgraham.com
by Paul Graham
~15 min read
- Recruit your first users manually, don't wait for them to come.
- A tiny group of users who love you beats a big group who like you.
- Manual, unscalable effort early is a feature, not a failure.
Open
paulgraham.com →
Why we picked it
The most systematic step-by-step process for de-risking an idea, built around the Lean Canvas. Where The Lean Startup gives philosophy, Running Lean gives you the exact sequence of experiments to run this month.
From
LEANSTACK
by Ash Maurya
~240 pages
- Capture your business model on one Lean Canvas before building.
- Rank and attack your riskiest assumptions first.
- Run problem interviews, then solution interviews, then an MVP.
Open
leanstack.com →
