§ 04 / Product

Building MVPs for startups — 3–6 weeks to your first user.

We take a product hypothesis and ship it to a state where you can actually measure something. We've helped clients close seed rounds, run first sales, discover their product had no audience — and avoid bankrupting themselves polishing it. All of those are good outcomes.

§ 04.1 What MVP means to us

An MVP is not "a stripped-down version of the full product." It's the minimum that answers one or two key questions: will users use this, and will they pay? Anything that doesn't help answer those questions doesn't belong in the MVP.

So we ruthlessly cut features that "we'll definitely need, but later." A 20-screen admin panel becomes one page where we edit data by hand for the first two weeks. Onboarding becomes a single screencast. Payments — Stripe Checkout or YooKassa Link, no custom cart.

This isn't laziness or cutting corners. It's how you launch while competitors are still negotiating the spec.

§ 04.2 What's included

Pre-discovery: a call to pull the hypotheses and success criteria out of your head.
Flow sketches and key-screen mockups in Figma.
Frontend, backend, database, integrations (payments, email, notifications, analytics).
Launch landing page — with waitlist or direct signup.
Measurement tools: PostHog, Plausible, email alerts on key events.
Production deploy, monitoring, support during the first month.
An honest numbers review 30 days after launch: what's working, what isn't.

§ 04.3 Timeline

Lean MVP

3 weeks

One core flow, auth, payments, minimal admin. For testing whether anyone will pay at all.

Classic MVP

4–5 weeks

Multiple flows, roles, a proper admin panel, email notifications, integrations. Pitch-deck ready and good for first investor conversations.

Seed-ready

6 weeks

A product you can raise seed on: paying users, metrics, infrastructure, ready to grow 10×.

Pricing is always custom — we put a number together on the first call based on flow scope and integration complexity.

§ 04.4 FAQ

Can we pay in equity?

Sometimes — yes, if we like the product and see the point. But it's an exception, not the rule. Usually we work for cash.

We don't have design or a spec. Can you still help?

Yes. MVP is exactly the "no spec yet" phase. We formulate hypotheses together, we sketch, we sign off on the key screens — then we start.

What if the MVP shows the idea doesn't work?

That's a normal outcome. You spent 3–6 weeks and a small budget instead of 9 months building "the full version." It's called "saving money."

Who writes the code after the MVP?

At growth stage — usually your team. We hand over the codebase with documentation and help onboard the developers. Or we can keep going on an hourly model.

§ — Write to us

Tell us
about the idea.

hi@weiss.help ↗

or via Telegram · phone

First 20-minute call — free. Quote within 24 hours.