Skip to content
dvnt.io

FOR STARTUPS AND NEW PRODUCTS

MVPs for startups

An MVP you grow after validation instead of rewriting it from scratch. We work with startups that have a specific question for the market. Scope, technology and budget are agreed after a call, based on your business requirements.

Startups and new products in companies · scope and budget after the call · the code is yours from day one

From idea to launch

3–14 wks

WHEN IT'S WORTH IT - 4 SCENARIOS

When an MVP makes sense

  • Signal 01

    Validating a business hypothesis

    Customer interviews confirm the problem, but they do not tell you whether anyone will pay for a solution. An MVP with one key journey (sign-up, core feature, payment) answers that with data, not declarations.

  • Signal 02

    Seed funding secured

    You have a budget and a year or more to show traction. An MVP lets you spend it on testing the product in the market and keep money for marketing and sales, instead of on a large system nobody uses yet.

  • Signal 03

    B2B sales waiting for a demo

    Sales calls end with "show us a working product", and the first companies are ready for a pilot. An MVP gives them something to test and shortens the way to a signed contract.

  • Signal 04

    Demo day or a funding round

    An accelerator or investors want to see a product, not just a deck. We build the MVP to your deadline, with a record of the technical decisions that helps in due diligence.

// 3 TYPES OF MVP - CHOOSE YOUR CONTEXT

What specifically are we building as an MVP

  • Type 01

    SaaS product for businesses

    A tool you sell to companies on subscription: team accounts, payments, the first paying companies.

  • Type 02

    Two-sided platform

    Connects two groups, e.g. clients and contractors: profiles, search, the first transactions.

  • Type 03

    A tool for one client

    A dashboard or system for a specific company, often as a pilot before a bigger contract.

WHAT MAKES THE DIFFERENCE - 4 SPECIFICS

Why our MVPs don't require rewrite after validation

We build an MVP so that after a successful validation you keep developing it instead of starting over. The money spent on the start also works for the next version.

  • Concrete 1

    You grow the product instead of rewriting it

    The MVP is built with the same technology as the full product, so once customers start paying, we add features to what already works. You do not lose months and a second budget on the rewrite that awaits many quickly assembled MVPs.

  • Concrete 2

    Documentation that speeds up investor talks

    We record every important technical decision with its reasons. An investor in due diligence, a new CTO or another team sees at once how the product is built and why.

  • Concrete 3

    The code is yours from day one

    The repository sits in your account and the rights to the code pass to you. You can change the vendor or build your own team at any time, with no exit fees and no dependence on us.

  • Concrete 4

    You know what happens in the product

    From launch you see how customers use the product and where they hit errors. You base the first development decisions on data, and we fix pilot customers' problems before they give up.

// HOW WE BUILD · 3 MVP STAGES

How we build an MVP - from idea to market validation

  1. Stage 01 · 1-2 wks

    Pre-implementation analysis

    What you get

    • System architecture (HLD) and data model
    • Interface specification (API)
    • User scenarios (1-3 audience groups, key tasks)
    • Architectural decision document — why this technology and not another
    • Three pricing variants (Lean / Standard / extended scope)
    • Implementation schedule with milestones

    What happens

    • A 60-90 min consultation and 1-2 further calls
    • The documentation is yours regardless of further cooperation — you can take it to another developer
  2. Stage 02 · 2-12 weeks (Lean 2-4 weeks, Standard 7-12 weeks)

    MVP implementation

    What you get

    • A working product in production
    • Support for multiple customers on a single instance (if B2B SaaS)
    • Payments through a provider chosen for your customers (e.g. Przelewy24, BLIK, cards): subscriptions, one-off payments, invoices
    • Login (passkey, Google or an e-mail link)
    • Administration panel
    • Monitoring and observability from day one (error tracking, user behaviour analytics, uptime checks) — not after the first failure
    • Automated tests of key paths (Standard variant)
    • Your repository (the GitHub account is yours), full technical documentation, deployment instructions

    What happens

    • Work in two-week stages
    • A progress demo after each stage
    • A test version from the first stage
  3. Stage 03 · 4-12 weeks after launch

    Validation and iteration (optional)

    What you get

    • User behaviour data (conversion funnels, retention)
    • Sales data (revenue, conversion, churn)
    • Interviews with the first customers (3-10 pilot companies)
    • A decision on version 2.0 — three paths (scale / change direction / close)

    What happens

    • We decide on data, not assumptions
    • The three paths after the MVP are described in the FAQ

MVP PRICE LIST - 3 VARIANTS

How much does an MVP cost at dvnt

The prices below are a starting point. On a call we advise what really has to go into the first version and look for the solution that gets you an answer from the market at the lowest cost. You get the final quote once the scope is agreed.

  • Variant 01 - Price: from PLN 10,000 net - Time: 3-6 weeks

    Lean MVP

    For whom: Hypothesis verification, demo day at an accelerator, B2B sales unlocked

  • Variant 02 - Price: from PLN 30,000 net - Time: 8-14 weeks

    MVP standard

    For whom: B2B SaaS with pilot customers, two-sided platform, startups with funding to start

  • Variant 03 - Price: individual quote - Time: continuous.

    Scaling up after the MVP

    For whom: Startups with market fit, ready to scale (pitch for A round or self-funding)

FAQ - 6 QUESTIONS ABOUT MVP

Questions we get before the MVP begins

What is the difference between a Lean MVP and a Standard MVP?

Lean MVP (from PLN 10,000) = 1 audience, 1 key user journey, ready-made components, minimal integrations - the smallest working product that verifies the hypothesis. Before finding market fit. 3-6 weeks. Goal: will someone pay for X.

Standard MVP (from PLN 30,000) = a full first version: accounts with roles for 2-3 audience groups, 3-5 functions, payments and integrations, admin panel, pilot client readiness. Foundation for scaling after validation. 8-14 weeks. Target: first 3-10 paying customers + foundation for version 2.0.

Both amounts are net "from" prices. Every MVP is quoted individually after the preliminary analysis.

What do we do if the MVP doesn't find a market fit?

Fair decision after Stage 3 validation (4-12 weeks after launch). Three options:

  • Change of function - data suggest that a match exists, but for a different application. Iteration of features, same technologies.
  • Product change - Different market, audience, value proposition. Partial rewrite (interface + business logic, base stays).
  • Closing - Data clear, no match, financial reserve low. Fair recommendation: close MVP, save money, return to hypothesis stage. Cost: PLN 0 (dvnt does not sell further"maybe something will be found".).
How long does an MVP take from idea to launch?

Lean MVP: 3-6 weeks in total (preliminary analysis 1-2 weeks + implementation 2-4 weeks).MVP standard: 8-14 weeks in total (preliminary analysis 1-2 weeks + implementation 7-12 weeks).

Validation 4-12 weeks in addition (after launch, on a continuous basis). Version 2.0 decision based on data, not assumptions.

Who owns the code and what happens if we change agencies?

Your repository (GitHub yours, not ours). MIT or proprietary license - whatever you want. Zero vendor dependency. Architectural and technical documentation allows any competent developer to take over the project in ~1-2 weeks of implementation.

What's next after MVP - who is building version 2.0?

After validation, three options:

  • Long-term cooperation with dvnt - we continue as an external implementation partner
  • Own team - We implement your technical director and team in ~1 week, we hand over the project
  • Other supplier - You have a repository, architectural and technical documentation. Any senior developer will take over the project in 1-2 weeks.
Wouldn't a no-code tool be enough for the MVP?

Sometimes it is. If you only want to check whether people join a waitlist or click "buy", a no-code tool will be faster and cheaper, and we will tell you so.

We write code when the MVP has to take payments from day one, connect to other systems or become the foundation of the product. We choose the technology after a call, to fit your business requirements.

RESOURCES · BEFORE WE TALK

Before we talk

// Next step

Describe your project. We reply within 24 h.

A few sentences are enough: what should work, what it connects to and by when. No brief, no commitment.

What happens next

  1. We read your message and reply within one working day.
  2. We set up a short call about the scope, with no sales pitch.
  3. You get proposed stages and a price range.
Meeting date (optional)

Time

CET

Checking free times…

Budget (net)

By sending this form, you accept the Privacy Policy.