{"id":633,"date":"2026-06-26T10:59:03","date_gmt":"2026-06-26T10:59:03","guid":{"rendered":"https:\/\/foundry-5.com\/resources\/?p=633"},"modified":"2026-07-16T12:40:41","modified_gmt":"2026-07-16T12:40:41","slug":"how-to-build-an-mvp","status":"publish","type":"post","link":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/","title":{"rendered":"How to Build an MVP in 4 Weeks: What to Scope, What to Cut, and What to Ship"},"content":{"rendered":"<p><b>Table of Contents<\/b><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What an MVP actually is, and what it isn&#8217;t<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How do you build an MVP in 4 weeks?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What to scope: the one problem worth solving<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What to cut: the features that quietly kill MVPs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What to ship: the smallest thing real users can use<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">How much does it cost to build an MVP in the UK?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Who should build it: freelancer, agency, or studio?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">What happens after you launch an MVP?<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Frequently Asked Questions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The right way to build an MVP in 4 weeks<\/span><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><b>Quick answer:<\/b><span style=\"font-weight: 400;\"> Foundry 5 helps founders build an MVP in 4 weeks by scoping one core problem, cutting every non-essential feature, and shipping to real users. It matters because 42% of startups fail from no market need, per CB Insights. Scope tight, cut hard, ship early, then learn what the market actually tells you.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">You have the idea. You have some money, maybe a slice of savings or a pre-seed cheque. What you do not have is twelve months to discover whether anyone wants the thing you are about to build. That is the real pressure behind every first product: not the code, the clock.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">The numbers explain the fear. According to <\/span><a href=\"https:\/\/www.cbinsights.com\/research\/report\/startup-failure-reasons-top\/\" target=\"_blank\" rel=\"noopener\"><b>CB Insights<\/b><\/a><span style=\"font-weight: 400;\">, 42% of startups fail for one reason above all others: no market need. They built something nobody was waiting for. A four-week MVP exists to answer that one question early, while you still have the runway to act on the answer.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">This is a working playbook, not a theory lecture. We will cover what to scope, what to cut, and what to ship, in that exact order, because that is the order that protects your budget when you build an MVP in 4 weeks. It is the same sequence we run on every <\/span><a href=\"https:\/\/foundry-5.com\/services\/mvp-development\"><b>MVP development<\/b><\/a><span style=\"font-weight: 400;\"> engagement at Foundry 5. Build the smallest honest version. Put it in front of real people. Learn something true before you spend the rest.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>What an MVP actually is, and what it isn&#8217;t<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An MVP is the smallest version of your product that lets you learn whether people actually want it. It is not a cheap version of the finished thing. It is not a demo you show investors and then throw away. The minimum viable product earns the most validated learning for the least effort. Learning is the real output, rather than a polished interface.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>MVP vs prototype vs proof of concept<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Three terms get used as if they mean the same thing. They do not, and confusing them burns weeks. If you are weighing MVP vs prototype vs proof of concept, anchor each one to the question it answers. A proof of concept asks can we build this at all. A prototype asks how should this look and feel. An MVP asks will anyone actually use this.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">A prototype answers a design question. A proof of concept answers a technical question. An MVP answers a business question. Build the one that matches the question keeping you awake at 2am, rather than the one that feels most impressive in a pitch.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>The test for what belongs in version one<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Here is the filter the best teams use: does this feature help us prove or disprove our single biggest assumption? If yes, it stays. If no, it waits. Picture a founder building a booking tool for personal trainers. The risky assumption is that trainers will pay to manage clients in one place. Calendar sync proves that. A loyalty-points engine does not. One belongs in week one, the other belongs in a backlog you may never touch.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>How do you build an MVP in 4 weeks?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">To build an MVP in 4 weeks, Foundry 5 runs a fixed four-week sprint: week one scopes the problem, week two designs and validates the core flow, week three builds the happy path, and week four tests and ships to real users. The deadline is the discipline. A fixed clock forces every decision to serve one outcome, rather than drifting toward a wishlist.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Week 1: Scope the one problem<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Week one produces clarity, not code. You write a one-sentence problem statement, name the single user you serve, and cut the feature list to the three to five things that solve that problem end to end. The output is a one-page brief everyone can hold in their head. Skip this week and you will rebuild everything in week five.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Week 2: Design and validate the flow<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Week two turns the brief into a clickable prototype and puts it in front of five real people from your target audience. Design here is communication, not decoration: it shows users what the product will do so you can catch wrong assumptions before they cost development time. Five honest conversations in week two save you a quarter of regret later.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Week 3: Build the happy path<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Week three is disciplined construction. Repositories, staging, and deployment are ready on day one, then the team builds the single most common user journey from start to finish. Authentication, payments, and analytics get plugged in rather than built from scratch. Each day ends with something you can click. Edge cases wait their turn.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Week 4: Test, fix, and ship<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Week four is where many founders flinch. You hand the product to someone who has never seen it, watch them struggle, and fix the friction that matters. Your MVP does not need to survive a million users. It needs to reach the first ten who are real. Then you ship, rather than polishing in private for another month.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>What to scope: the one problem worth solving<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Scoping an MVP means choosing the single problem your product solves and ignoring every adjacent temptation. The best first builds do one thing a real person genuinely needs, and do it well. Most successful MVPs ship with three to five core features, rather than the thirty a founder first imagines on a whiteboard.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Write a one-page brief first<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">The brief is the cheapest insurance you will ever buy. Before a line of code, learn how to write a good MVP brief that fits on a single page: the problem in one sentence, the target user, the core feature list, and the one metric that says it worked. A brief that needs three pages is a product that needs three more months.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Choose the feature set ruthlessly<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Every founder over-scopes the first build. It is human. The discipline is deciding how to choose your MVP feature set by ranking each idea against your riskiest assumption, then drawing a hard line after the top few. List every feature you want. Now cut most of them. What remains is the MVP. What you cut is the roadmap.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Validate before you write code<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Scoping and validation are the same muscle. Knowing how to validate a product idea before you build means testing demand with conversations, a landing page, or a concierge test before committing a budget. Seeing what people actually do beats asking what they would do. A waitlist that fills is a signal. A room full of polite nods is not.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><b>Already sure your idea is worth building?<\/b><span style=\"font-weight: 400;\"> You can map the four-week scope with us, or keep reading for the cut list that keeps budgets honest. <\/span><a href=\"https:\/\/foundry-5.com\/services\/mvp-development\"><b>See how MVP development works at <\/b><\/a><\/p>\n<p><a href=\"https:\/\/foundry-5.com\/services\/mvp-development\"><b>Foundry 5<\/b><\/a><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>What to cut: the features that quietly kill MVPs<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">What to cut is everything that does not prove your core hypothesis. The data here is blunt. Pendo found that 80% of features in the average software product are rarely or never used. Every feature you cut from the MVP buys back time, budget, and focus you can spend on the one thing that matters.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>The 80% you do not need yet<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Most founders build for the user they hope to have in year three, not the one they need to win next month. In its <\/span><a href=\"https:\/\/www.pendo.io\/resources\/the-2019-feature-adoption-report\/\" target=\"_blank\" rel=\"noopener\"><b>2019 Feature Adoption Report<\/b><\/a><span style=\"font-weight: 400;\">, Pendo found that 56% of features were never used at all and only 12% saw frequent use. Read that again before your next sprint. Settings panels, admin dashboards, and that clever integration can almost always wait.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>A simple rule for cutting<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Sort every feature into three buckets: must-have to prove the idea, nice-to-have later, and never. Be honest about how small the first bucket is. The must-have list is your MVP. The nice-to-have list is your next two quarters. The never list is a gift to your future self.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>First-product mistakes founders make<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">The biggest reason MVPs fail is not weak engineering. It is building the wrong thing beautifully. The most common first-product mistakes founders make are scope creep, polishing before validating, and treating launch as the finish line. We see this pattern repeatedly with teams approaching their first growth stage. The fix is boring and it works: cut harder, ship sooner.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>What to ship: the smallest thing real users can use<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">What you ship is the happy path: the single most common journey through your product, working from start to finish. Skip the edge cases for now. Ship to a small group of real users, rather than chasing a flawless launch for an audience of nobody. A narrow thing that works beats a broad thing that breaks.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Build the happy path, not the maze<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A founder preparing to launch a marketplace does not need twelve payment methods on day one. One that works clears the test. Build the route a real user takes most often, end to end, and let the rare paths wait. Every error state you build before launch is a guess you have not earned the right to make.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Choosing the right web stack<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Technology choices should serve speed now and options later. When you are choosing the right web stack, pick proven tools your team already knows, rather than the framework that trended last week. The right stack ships in four weeks and still scales when traction arrives. The wrong stack wins an argument on Twitter and loses you a month.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>How much does it cost to build an MVP in the UK?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A focused four-week MVP in the UK typically costs between \u00a315,000 and \u00a340,000, depending on platform count, integrations, and design depth. Simple single-platform builds sit at the lower end. Price tracks scope, not ambition: the more you cut, the less you spend, which is the strongest argument for cutting in the first place.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>What a four-week MVP actually costs<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Numbers vary by studio and city, so treat any single figure with care. Across UK studios, a simple single-platform build with three to five features and standard integrations commonly lands in the \u00a315,000 to \u00a340,000 band, while multi-platform or regulated products climb well beyond it. For a fuller breakdown of how much an MVP costs to build in the UK, map your feature list to a band before you brief anyone. Scope decides the invoice.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>Who should build it: freelancer, agency, or studio?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The right builder depends on your stage and your appetite for risk. A freelancer fits a tiny, well-proven scope. An agency fits a defined, larger build with fixed requirements. A product studio fits a founder who needs help scoping, building, and a partner who stays after launch, rather than handing over a zip file and disappearing.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Freelancer, agency, or studio<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Each option carries a different trade-off between cost, speed, and risk. The honest framework for choosing between a freelancer, agency, or studio comes down to how proven your scope is and how much partnership you need. Here is how they compare for a first product.<\/span><\/p>\n<p>&nbsp;<\/p>\n<table style=\"width: 100%; border-collapse: collapse; border: 1px solid #ffffff; font-size: 15px;\">\n<tbody>\n<tr>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><b>Option<\/b><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><b>Best for<\/b><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><b>Strength<\/b><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><b>Watch out for<\/b><\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Freelancer<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Small, proven scope<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Low cost, fast start<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Limited capacity, single point of failure<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Agency<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Defined, larger build<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Process and team depth<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Backlog delays, handoff at launch<\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Product studio<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Scoping plus build plus iteration<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Stays after launch, owns outcomes<\/span><\/td>\n<td style=\"border: 1px solid #ffffff; padding: 12px;\"><span style=\"font-weight: 400;\">Higher day rate than a solo freelancer<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<h4><b>How to evaluate a software studio<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">The best partners challenge your assumptions before writing a single line of code. When evaluating a software studio, ask how they scope, who your day-to-day contact is, and what happens after launch. Ask too what what a risk-free first project means in practice: a small, fixed, clearly-defined first build that proves the working relationship before anyone commits to the big one.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><b>Want a scoping partner who stays after launch?<\/b><span style=\"font-weight: 400;\"> If the framework above matches what you need, the next step is a 30-minute scoping call: no pitch deck, no commitment, just a direct conversation about whether your idea is ready to build. <\/span><a href=\"https:\/\/foundry-5.com\/contact\"><b>Book a free discovery call with Foundry 5<\/b><\/a><span style=\"font-weight: 400;\">. It takes two minutes to schedule.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>What happens after you launch an MVP?<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Launch is the start of the real work, not the end of it. After you launch an MVP, you measure how real users behave, learn what the data tells you, and decide what to build next. Foundry 5 treats the first version as infrastructure for learning, rather than a monument to ship and forget.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>The build, measure, learn loop<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">The discipline that turns a launch into a business is a loop. You build the smallest thing, measure how people use it, and learn what to change, then repeat. This <\/span><a href=\"https:\/\/theleanstartup.com\/principles\" target=\"_blank\" rel=\"noopener\"><b>build, measure, learn loop<\/b><\/a><span style=\"font-weight: 400;\"> sits at the heart of the lean method for a reason: it replaces opinion with evidence. Knowing what happens after you launch an MVP is what separates a product from a press release.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>Moving to mobile, and other next steps<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Traction changes the questions you ask. Once the web MVP proves demand, moving to mobile or adding the features you deliberately cut becomes a data-backed decision, rather than a guess. Mobile is not a checkbox. It is a response to where your users actually are. Let the numbers, not the roadmap you drew in month one, decide what comes next.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>Frequently Asked Questions<\/b><\/h3>\n<h4><b>How long does it take to build an MVP?<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A focused MVP typically takes 4 to 12 weeks, and a tightly scoped build can ship in four. Foundry 5 runs a fixed four-week sprint for products with three to five core features. Complexity, integrations, and regulation push the timeline up. The single biggest lever on speed is how ruthlessly you cut scope.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>What is the difference between an MVP and a prototype?<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A prototype tests how a product looks and feels, usually as a clickable mockup with no working backend. An MVP is a real, usable product that tests whether people will adopt and pay for it. A prototype answers a design question. An MVP answers a business question, with real users and real data.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>How many features should an MVP have?<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Most successful MVPs ship with three to five core features, not thirty. The rule is simple: include only what proves your single biggest assumption, and cut the rest. Pendo found that 80% of software features are rarely or never used, so building fewer features at launch is the safer bet, not the riskier one.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>How much does it cost to build an MVP in the UK?<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">A simple single-platform MVP in the UK commonly costs between \u00a315,000 and \u00a340,000, depending on features, integrations, and design depth. Multi-platform or regulated products cost more. Cost tracks scope directly, so the cleanest way to lower the price is to cut features, rather than cutting corners on the build quality.<\/span><\/p>\n<p>&nbsp;<\/p>\n<h4><b>What should you do after you launch an MVP?<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">After you launch an MVP, measure real usage, talk to early users, and decide what to build next from evidence rather than opinion. Run the build, measure, learn loop in short cycles. Resist adding features nobody asked for. The launch is the first experiment, and the data it returns is the whole point of building small.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<h3><b>The right way to build an MVP in 4 weeks<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Speed is not the enemy of quality. Sprawl is. The founders who win their first build are not the ones who ship the most features. They are the ones who scope the one problem, cut the noise, and ship to real users while the runway still allows a second move.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">So treat the four weeks as a discipline, not a stunt. Scope tight. Cut hard. Ship early. Then let real behaviour, not your roadmap, tell you what comes next. That is how you build an MVP in 4 weeks that earns a second version.<\/span><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">If you are a founder, SME, or growth-stage team ready to turn an idea into a launch-ready product, <\/span><a href=\"https:\/\/foundry-5.com\/contact\"><b>book a free 30-minute discovery call with Foundry 5<\/b><\/a><span style=\"font-weight: 400;\">. No pitch deck. No pressure. Just a direct conversation about whether your project is ready. Build small. Learn fast. Ship anyway.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Table of Contents What an MVP actually is, and what it isn&#8217;t How do you build an MVP in 4 weeks? What to scope: the one problem worth solving What to cut: the features that quietly kill MVPs What to ship: the smallest thing real users can use How much does it cost to build [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":637,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-633","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Build an MVP in 4 Weeks: What to Scope and What to Ship<\/title>\n<meta name=\"description\" content=\"The Foundry 5 method for building an MVP in four weeks: how to scope honestly, what to cut without killing the product, and what launch actually looks like.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Build an MVP in 4 Weeks: What to Scope and What to Ship\" \/>\n<meta property=\"og:description\" content=\"The Foundry 5 method for building an MVP in four weeks: how to scope honestly, what to cut without killing the product, and what launch actually looks like.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/\" \/>\n<meta property=\"og:site_name\" content=\"Foundry 5\" \/>\n<meta property=\"article:published_time\" content=\"2026-06-26T10:59:03+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-16T12:40:41+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/foundry-5.com\/resources\/wp-content\/uploads\/2026\/06\/How-to-Build-an-MVP-in-4-Weeks-2.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1920\" \/>\n\t<meta property=\"og:image:height\" content=\"1116\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"foundry-5\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"foundry-5\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/\"},\"author\":{\"name\":\"foundry-5\",\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/#\\\/schema\\\/person\\\/7037e69eb0cd7937acd481a5d2064ff7\"},\"headline\":\"How to Build an MVP in 4 Weeks: What to Scope, What to Cut, and What to Ship\",\"datePublished\":\"2026-06-26T10:59:03+00:00\",\"dateModified\":\"2026-07-16T12:40:41+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/\"},\"wordCount\":2793,\"image\":{\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/How-to-Build-an-MVP-in-4-Weeks-2.png\",\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/\",\"url\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/\",\"name\":\"How to Build an MVP in 4 Weeks: What to Scope and What to Ship\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/How-to-Build-an-MVP-in-4-Weeks-2.png\",\"datePublished\":\"2026-06-26T10:59:03+00:00\",\"dateModified\":\"2026-07-16T12:40:41+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/#\\\/schema\\\/person\\\/7037e69eb0cd7937acd481a5d2064ff7\"},\"description\":\"The Foundry 5 method for building an MVP in four weeks: how to scope honestly, what to cut without killing the product, and what launch actually looks like.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/#primaryimage\",\"url\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/How-to-Build-an-MVP-in-4-Weeks-2.png\",\"contentUrl\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/How-to-Build-an-MVP-in-4-Weeks-2.png\",\"width\":1920,\"height\":1116},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/how-to-build-an-mvp\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Build an MVP in 4 Weeks: What to Scope, What to Cut, and What to Ship\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/#website\",\"url\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/\",\"name\":\"Foundry 5\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/#\\\/schema\\\/person\\\/7037e69eb0cd7937acd481a5d2064ff7\",\"name\":\"foundry-5\",\"sameAs\":[\"https:\\\/\\\/foundry-5.com\\\/resources\"],\"url\":\"https:\\\/\\\/foundry-5.com\\\/resources\\\/author\\\/foundry-5\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Build an MVP in 4 Weeks: What to Scope and What to Ship","description":"The Foundry 5 method for building an MVP in four weeks: how to scope honestly, what to cut without killing the product, and what launch actually looks like.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/","og_locale":"en_US","og_type":"article","og_title":"How to Build an MVP in 4 Weeks: What to Scope and What to Ship","og_description":"The Foundry 5 method for building an MVP in four weeks: how to scope honestly, what to cut without killing the product, and what launch actually looks like.","og_url":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/","og_site_name":"Foundry 5","article_published_time":"2026-06-26T10:59:03+00:00","article_modified_time":"2026-07-16T12:40:41+00:00","og_image":[{"width":1920,"height":1116,"url":"https:\/\/foundry-5.com\/resources\/wp-content\/uploads\/2026\/06\/How-to-Build-an-MVP-in-4-Weeks-2.png","type":"image\/png"}],"author":"foundry-5","twitter_card":"summary_large_image","twitter_misc":{"Written by":"foundry-5","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/#article","isPartOf":{"@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/"},"author":{"name":"foundry-5","@id":"https:\/\/foundry-5.com\/resources\/#\/schema\/person\/7037e69eb0cd7937acd481a5d2064ff7"},"headline":"How to Build an MVP in 4 Weeks: What to Scope, What to Cut, and What to Ship","datePublished":"2026-06-26T10:59:03+00:00","dateModified":"2026-07-16T12:40:41+00:00","mainEntityOfPage":{"@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/"},"wordCount":2793,"image":{"@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/#primaryimage"},"thumbnailUrl":"https:\/\/foundry-5.com\/resources\/wp-content\/uploads\/2026\/06\/How-to-Build-an-MVP-in-4-Weeks-2.png","inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/","url":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/","name":"How to Build an MVP in 4 Weeks: What to Scope and What to Ship","isPartOf":{"@id":"https:\/\/foundry-5.com\/resources\/#website"},"primaryImageOfPage":{"@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/#primaryimage"},"image":{"@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/#primaryimage"},"thumbnailUrl":"https:\/\/foundry-5.com\/resources\/wp-content\/uploads\/2026\/06\/How-to-Build-an-MVP-in-4-Weeks-2.png","datePublished":"2026-06-26T10:59:03+00:00","dateModified":"2026-07-16T12:40:41+00:00","author":{"@id":"https:\/\/foundry-5.com\/resources\/#\/schema\/person\/7037e69eb0cd7937acd481a5d2064ff7"},"description":"The Foundry 5 method for building an MVP in four weeks: how to scope honestly, what to cut without killing the product, and what launch actually looks like.","breadcrumb":{"@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/#primaryimage","url":"https:\/\/foundry-5.com\/resources\/wp-content\/uploads\/2026\/06\/How-to-Build-an-MVP-in-4-Weeks-2.png","contentUrl":"https:\/\/foundry-5.com\/resources\/wp-content\/uploads\/2026\/06\/How-to-Build-an-MVP-in-4-Weeks-2.png","width":1920,"height":1116},{"@type":"BreadcrumbList","@id":"https:\/\/foundry-5.com\/resources\/how-to-build-an-mvp\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/foundry-5.com\/resources\/"},{"@type":"ListItem","position":2,"name":"How to Build an MVP in 4 Weeks: What to Scope, What to Cut, and What to Ship"}]},{"@type":"WebSite","@id":"https:\/\/foundry-5.com\/resources\/#website","url":"https:\/\/foundry-5.com\/resources\/","name":"Foundry 5","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/foundry-5.com\/resources\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/foundry-5.com\/resources\/#\/schema\/person\/7037e69eb0cd7937acd481a5d2064ff7","name":"foundry-5","sameAs":["https:\/\/foundry-5.com\/resources"],"url":"https:\/\/foundry-5.com\/resources\/author\/foundry-5\/"}]}},"_links":{"self":[{"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/posts\/633","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/comments?post=633"}],"version-history":[{"count":4,"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/posts\/633\/revisions"}],"predecessor-version":[{"id":638,"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/posts\/633\/revisions\/638"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/media\/637"}],"wp:attachment":[{"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/media?parent=633"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/categories?post=633"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/foundry-5.com\/resources\/wp-json\/wp\/v2\/tags?post=633"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}