I already have a 3D-printed MVP. Is it too late to validate?

No. The MVP is a sunk cost; the real question is whether to invest more or stop. A 21-day retroactive validation plan — landing page, €200–€300 in paid ads, then a decision — gives you a clear answer for under €400 and three weeks of calendar time.

I built an MVP on WordPress to validate an idea. What now?

A WordPress MVP is fine for delivering the product, but it doesn't test demand on its own. Strip the offer down to a single landing page (it can live on the same domain), drive paid traffic to it, and measure conversion to a clear CTA. The MVP becomes the fulfillment layer behind the test, not the test itself.

What conversion rate should a retroactive validation hit?

On a free CTA (waitlist, lead form), under 2% means the offer is wrong. On a paid CTA (€10–€50 deposit or first purchase), 0.8–1.5% is murky and 1.5%+ is a real signal. The threshold is slightly lower than for pre-MVP tests because you can show real photos and demos, which lifts conversion.

What should I do with the MVP if I decide to kill the project?

Three options that beat "leave it on a shelf": open-source the code or the CAD files, sell the assets to someone in an adjacent niche on a marketplace like MicroAcquire or Acquire.com, or write a public post-mortem documenting what you learned. All three convert sunk cost into reputation or cash.

How to Validate a Product Idea After You've Already Built the MVP

Q: Is it a good idea to launch a product before validating it?

Generally no, but if you already have, retroactive validation is the recovery move. Build a landing page that promises what the product does, run €200–€300 of paid traffic to it, and read the conversion. Below ~2% on a free CTA, the offer is wrong and more building won't fix it.

"How should I go about validating my product idea? When I already have a 3D-printed MVP." That's a real question, posted by a real founder, sitting on a real prototype that took real weekends to build. The honest answer is: you do it backwards, and you do it fast.

We see this question in three flavors every month. The 3D-printed hardware founder. The "I built an MVP on WordPress to validate an idea" founder. The "is it a good idea to launch a product before validating it?" founder, asked the day after the launch flopped. Same situation, different stack.

The advice everyone gives them is the wrong shape. "You should have validated first" is true and useless. They didn't. The MVP is now a sunk cost; the only question worth answering is whether the next 21 days reveal a path forward, or confirm there isn't one.

The honest framing: sunk cost is real, and that's okay

Most validation advice is written for people who haven't built yet. It tells them to stop, write a press release, run an ad test, then decide. That works pre-MVP. It doesn't map cleanly to a founder who already has a prototype on the kitchen table.

Two things are different once the MVP exists.

First, you have something real to point at. Photos. Demos. A working URL. That lifts landing-page conversion by 30–60% in our tests compared to pure mockup pages, because credibility is no longer hypothetical. Use that.

Second, you're emotionally wired to the build. Pretending you're not won't help. The kill criterion has to be written down before the test runs, ideally shared with someone who'll hold you to it. The murky middle is where founders go to die — see the broader pre-MVP playbook for the same warning, applied earlier in the funnel.

Sunk cost is real. The hours and euros that went into the MVP are gone whether you validate now or not. The next 21 days are the only ones you control.

The 21-day retroactive validation plan

Three weeks. Roughly €250–€350 all-in. The output is a binary decision: invest more, or stop and redirect.

Days 1–3: define the offer crisply

The MVP forces specificity. Use that. You can no longer hide behind "an app for X" or "a tool to help Y." You have to describe what the thing actually does, in one sentence, with no qualifiers.

Write three things on day one:

One sentence describing what the product does, for whom, replacing what alternative.
One paragraph describing the specific moment of pain it removes.
One price. Even if you plan to give it away. Pick a number.

If that takes more than three days, the problem isn't the validation plan — it's that the MVP was built without a clear customer in mind, and three days of forced specificity is the cheapest way to surface that.

Most of the founders we've watched do this exercise discover the offer is two offers in a trench coat. The 3D-printed gadget is "a stand for chefs" AND "a gift for foodies" AND "a kitchen organizer." Pick one. The test only works on a single, sharp offer.

Days 4–7: build a landing page that promises what the MVP does

Not a generic page. A page that promises exactly what your built product delivers. Hero image is a real photo or screenshot. Three benefits, drawn from the offer paragraph. One CTA.

For hardware: "Reserve yours — €25 deposit, refundable." For a WordPress-built service: "Book a 15-minute demo" or "Start your free 14-day trial." For a digital product: "Get early access — €10 first month."

The CTA tier matters more than the page design. A free CTA (waitlist, lead form) gives you a high-volume, low-quality signal. A paid CTA gives you a low-volume, high-quality signal. With an MVP already built, we lean paid — you can deliver if someone pays, and a real transaction is worth 100x a curious email.

Four days is plenty. The page doesn't need to be beautiful. It needs to make the offer clearly and load on mobile.

Days 8–17: paid ads to landing page

Ten days, €200–€300 of paid traffic. Same playbook as pre-MVP validation, just with better creative because you have real product photos.

Channel selection follows the audience, not the founder's preference. Hardware aimed at hobbyists: Reddit and Meta. B2B WordPress tool: LinkedIn or Google search. Consumer digital: Meta and TikTok. If you don't know where your audience lives, run a €50 test on two channels in week one and double down on the winner for week two.

Targeting tight beats targeting broad at this budget. "Home cooks who follow at least one professional chef on Instagram" will give you a cleaner read than "people who like food." Aim for at least 500 unique visitors per channel before drawing conclusions. Below that, you're reading noise.

Don't touch the page during the test. The instinct to optimize the headline on day 12 is strong. Resist it. You're measuring the offer, not the copy.

Days 18–21: read the data, decide

Three days to look at the numbers, write down what you're seeing, and commit to a decision. Not three weeks. Three days.

We've watched founders extend this phase for a month while "analyzing" — what they're really doing is searching the data for a permission slip to keep going. If that's the shape of your week 4, the answer is already no.

Kill criteria for retroactive validation

Pre-MVP, we publish thresholds around 5% for B2C waitlists and 1.5% for B2C pre-payments. With an MVP in hand, the bar moves slightly because your page can do more (real photos, real demos, real social proof if you have any beta users).

Rough zones, not gospel:

Free CTA (waitlist, lead form): 4%+ is strong, 2–4% is murky, sub-2% means the offer is wrong
Paid CTA (€10–€50 deposit or first purchase): 1.5%+ is strong, 0.8–1.5% is murky, sub-0.8% is a no
B2B "book a demo" (assuming WordPress-style MVP): 2%+ is strong, sub-1% is a no

The sub-2% line on a free CTA is the honest threshold. Below that, no amount of additional building helps. The product isn't the problem — the demand isn't there at the price (zero) where conversion should be easy.

Above the strong line, the question becomes "invest more in distribution or in product?" Almost always: distribution. The MVP works enough; the world doesn't know about it yet.

In the murky zone, run one more 7-day test with a different angle on the same audience. If that one's also murky, the answer is no — you're just paying ad-platform learning costs to confirm it.

What to do with the MVP if you kill

Killing well is a skill. Done badly, the MVP sits in a drawer and the founder spends six months feeling guilty. Done well, it converts sunk cost into reputation, cash, or a starting line for the next idea.

Open-source it. If the build has any technical merit — a clever 3D-print toolpath, a Stripe + WordPress integration, a prompt chain that took weeks to tune — put the files on GitHub or Printables with an honest README. We've seen indie founders pick up 2,000 GitHub stars from killed projects, which is worth more than the project ever would have been.

Sell it. A working WordPress site with email automation, even with no customers, sells for €500–€2,000 on MicroAcquire or Acquire.com if there's a niche match. Hardware molds and CAD files sell on Etsy or as Patreon downloads. The buyer is rarely another founder — usually it's someone in an adjacent niche who wants the head start.

Document the learnings. Write a public post-mortem. Specific numbers, what you thought, what happened, what you'd do differently. The audience that reads those posts is precisely the audience that'll trust your next launch. The graveyard of unfinished ideas only stays a graveyard if nobody publishes the maps.

The worst option is the silent shelf. The MVP gathering dust while you tell yourself you'll "come back to it." You won't. Pick one of the three above this week.

A worked example: the 3D-printed kitchen tool

Composite numbers, drawn from two founders we've seen run this exact loop on hardware MVPs in the last six months.

The MVP: a 3D-printed phone holder for chefs, magnetic, mounts to range hoods. €380 in filament and 40 hours of print/iterate time over six weeks. Three working units, one hero photo.

Days 1–3 — the offer: "A magnetic phone mount that clips under your range hood so you can follow recipes hands-free, without splatter on the screen. €29 with free EU shipping."

Days 4–7 — the page: Hero shot of the unit mounted, a 12-second loop video of it being attached, three benefits ("Hands-free recipes", "Splatter-proof", "No drilling"), CTA: "Reserve yours — €5 deposit." Built on Carrd in an afternoon.

Days 8–17 — the ads: €120 on Meta targeting home cooks aged 28–55 who follow at least one cooking creator. €100 on Reddit (r/cooking, r/foodhacks, r/Cooking4Health). 10 days.

The result: 1,840 visitors. 22 €5 deposits. 1.2% conversion on the paid CTA. Right in the murky zone.

The decision: Killed. The pre-set bar was 1.5%, and the founder had committed in writing to walking if it came in below. Refunded the 22 deposits with a thank-you note offering a free unit to anyone who replied. Eight replied, three became friends, two became beta testers for the next idea.

Total cost of the validation: €234 in ads. Total cost of the MVP itself: €380. Total time recovered by killing now instead of grinding on for another quarter: roughly 10 weekends. The CAD files went on Printables and got 4,200 downloads in three months — more reach than the product would have had as a paid SKU.

Why retroactive still beats "keep building"

Founders who skip the retroactive test and keep building usually end up running it anyway, six months later, on a polished v2. The conversion comes back the same. The €380 MVP becomes a €4,000 v2 to confirm what €234 of ads would have told them in three weeks.

The math is brutal but it's consistent. Building doesn't fix demand. Better building doesn't fix demand. Only the offer-audience match fixes demand, and the offer-audience match is what an ad test measures.

If you cleared the bar, you have a green light and a working product. That's a stronger position than most pre-MVP founders ever reach. The next move is distribution, not more product.

If you didn't clear the bar, you saved yourself the v2. That's the win. The MVP becomes the most expensive validation tool you'll ever buy — but it told you the truth, and now you can move.

How LemonPage fits

LemonPage compresses days 4 through 17 of this plan into a single workflow. You describe the offer (the work you did in days 1–3), it generates the landing page with your real product photos, runs the ad test, and reports conversion in one dashboard. Same framework, less plumbing.

The MVP is on the table. The next 21 days decide whether it stays there.