Stage 2 of 7

Proof of concept checklist: 28 milestones to validate demand before you build for real

You’ve validated the problem. Now simulate the solution, manually if needed, and prove that people actually want it.

4 min read26 milestones3 critical

A PoC is not a product. It is a test. The uglier it is, the more honest the signal. If you are spending time on design at this stage, you are optimizing for the wrong thing.

The best PoCs at this stage are often manual: a spreadsheet, a Notion doc, a series of emails doing what the product will automate. The goal is not to build technology. The goal is to test demand.

If 5 people go through your manual process and 0 come back, that is a signal. If 1 says "tell me when it is ready", that is traction. You do not need code to find out.

This is the stage where vibe coders have an unfair advantage: you can build a quick simulation faster than most. Use that speed to test, not to polish.

The key question at this stage: “Can I simulate value, even manually?”

Common trap: The perfection trap: spending weeks polishing a prototype when a manual process or no-code flow would prove the same thing faster.

The checklist: 26 milestones

Product5
  • Main flow simulated (even manually)Critical
  • Value proposition tested with a manual or no-code process
  • Main feature works (even hacked together)
  • User journey documented end-to-end
  • Product hypotheses listed and prioritized
Tech3
  • First code / no-code works
  • Simple architecture chosen (monolith > microservices)
  • No over-engineering (no CI/CD, no tests, that's OK)
Marketing & Distribution4
  • Landing page with clear value propositionCritical
  • Waitlist or contact form active
  • First public post about the project (LinkedIn, Reddit, Twitter)
  • Elevator pitch refined and tested
Users & Validation5
  • 5+ people have tested the process / flow manuallyCritical
  • Design partners identified (2-3 motivated early adopters)
  • Structured feedback collected (not just 'cool')
  • Problem confirmed as recurring (not one-shot)
  • At least 1 person said 'let me know when it's ready'
Business & Revenue3
  • Tentative pricing defined
  • Competitive analysis started (5+ competitors listed)
  • Hypothetical primary acquisition channel identified
Legal & Admin2
  • Terms / conditions draft if handling user data
  • GDPR: collected data identified
Data & Analytics1
  • PoC success metrics defined (which signals validate?)
Founder Mindset3
  • Ready to pivot if signals are bad
  • Has shared the project publicly (not just privately)
  • Has defined a kill criterion: 'I stop if X'

Category distribution

ProductTechMarketing & DistributionUsers & ValidationBusiness & RevenueLegal & AdminData & AnalyticsFounder Mindset
Stage 2: Proof of Concept

Think you’ve nailed Stage 2?

Most founders confuse building with validating. Banast analyzes your project across all 7 stages and flags exactly what is missing.

Frequently asked questions

What is the difference between a PoC and a prototype?

A PoC proves the concept works (even manually). A prototype is a functional product people can use independently. A PoC tests the idea; a prototype tests the execution.

Do I need a landing page at the PoC stage?

Yes. A simple page with your value proposition and a waitlist or contact form. It forces you to articulate what you are building and starts collecting interest.

How do I test a business idea without code?

Use no-code tools, manual processes, or concierge MVPs. The goal is testing demand, not building technology. If you can simulate the value by hand, do that first.

Where does your project really stand?

Paste your URL. Answer 5 questions. Get a scored audit across all 7 stages in under 3 minutes. Free.