• Applications & Products · Next.js and TypeScript

MVP: Not a small product, but a way to find out if someone needs it

MVP development fails not when the product turned out to be simple, but when after launch there is nothing to know whether it worked or not. Therefore, we start not with a list of functions, but with one sentence: what hypothesis are we testing and what numbers will we consider the answer. Then the idea is divided in half - "without this, the hypothesis cannot be tested" and "it will wait until the demand is confirmed." Analytics is set on day one, not after launch.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Format
the first version with a fixed list of scenarios
after a free audit
Price
30
Guarantee

days after project sign-off

the first version with a fixed list of scenarios
Format
30-60
Term

working days depending on the number of scripts

estimate after a free analysis of the design
Cost
30
Guarantee

days after signing the act

are transferred to you without binding to us
Code and accesses
What's included

Complete list of work and what you get as a result

  • Analysis of the idea before the start of work: a hypothesis in one sentence, a list of scenarios, the "now / then" limit.
  • A working product with exactly the scenarios needed for testing, nothing more and nothing less.
  • Analytics from day one: you can see not only how many people came, but where they came from and what they did. Without it, an MVP is indistinguishable from a failed MVP.
  • Registration and login - if the hypothesis is not tested without them.
  • Acceptance of payment - if it is the willingness to pay, not the interest, that is checked.
  • Deployment on the working domain: certificate, backups, availability monitoring.
  • Transferring the code and all access to you. You can continue with another contractor at any time.
When this service isn't right

What's not included — so there are no surprises at delivery

  • Admin for all occasions: in the first version, we manage only what really needs to be managed every day.
  • Mobile applications for the App Store and Google Play — a separate cycle with store checks, which extends the term twice.
  • A complex system of roles and rights before the request is confirmed.
  • Design system: we make it neat and uniform, but we do not build a library of components.
Who it's for

Situations where this service delivers results

Scenario 1 of 4

There is an idea, but there is no certainty

You see a problem and figure out how to close it, but you don't know if people are willing to pay for it. The MVP here isn't buying the product, it's the answer—and the cheaper the better, including the answer "no."

We'll review your situation in a free audit

Instead of a price fork, there is a free design analysis

The price of the MVP is determined by the list of scenarios, not the complexity of the idea. Therefore, first we find out what exactly is checked and without which the check cannot be carried out.

What we measure

  • What hypothesis is being testedone sentence like "X people are willing to pay for Y" - if it is not formulated, the MVP has nothing to measure
  • What is included in the first versionwe divide the idea into "without this, the hypothesis cannot be tested" and "it will wait until the demand is confirmed"
  • How to understand what workedwhich numbers will be considered the answer: registration, payment, return, time in the service
  • Where will the first people come from?without an answer to this, even a working MVP will remain empty and show nothing
  • What to do if it doesn't workwhich piece of work will remain useful and which will have to be thrown away is decided before the beginning

What you get

  • A hypothesis formulated in one sentence and suitable for measurement
  • List of scenarios of the first version, divided into "now" and "then"
  • The estimate is for the first version, not for the entire idea

Timeline: 3-5 working days

Why is it free

Because most conversations about MVP end with the fact that the idea turns out not to be an MVP, but a full-fledged product. It's easier for us to spend a few days and show it on the list of scripts than to take it and stick to the budget in the middle of the job.

What's next

If the hypothesis can be tested without development - with a landing page, a manual service, a table - let's say it directly. The list of scenarios remains with you in any case.

Short form: your contact and site URL

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • European clients

    Among our work — projects for Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

What affects the price

Why two seemingly identical tasks are priced differently

  • Number of scriptsOne script "registered - made - paid" and five parallel branches - different jobs. This is where an MVP most often seamlessly turns into a product.
  • Do you need money inside?You can show interest without payment. Check readiness to pay - no. Accepting payment adds work, but it is often the hypothesis itself.
  • The presence of other people's systemsIf the MVP has to take data from the outside, the term is not determined by your product, but by someone else's interface and how well it is documented.
  • Who fillsThe service, where the user enters the data, and the service, which must be filled in advance, are different in terms of preparation. The second sometimes takes longer than the development itself.
  • User rolesOne type of user and three with different rights — the difference in each screen. In the first version, one should be left, if the hypothesis allows.
  • The state of what has already been doneIf there is work done by the previous contractor, they either save time or eat it up for analysis. What exactly - you can see on a free analysis.
Cases

Tasks and results in numbers — all metrics measured by us

own free service — activity code directory for entrepreneurs

Task
Check whether there is a demand for a convenient KVED directory, and whether a search will find it without any advertising budget.
Solution
Launched the first version with one script - find your code and understand compliance - and delivered analytics immediately, not after launch.
Result
Measured for 01.07–02.08.2026: 349 active users, 346 of them new, 2.3 thousand events, average interaction time 1 min 45 s. Sources of sessions: Google search — 217, direct measures — 196, ChatGPT — 62, Bing — 30. There was not a single hryvnia of advertising. The site gives the first response in 244 ms and has 1,366 pages.

own data processing service with payment by subscription

Task
Launch the first version so that it can be displayed and accepted without building a full product.
Solution
We limited the first version to a minimum of pages required for registration, payment and the main action, and immediately made the markup for search.
Result
Measured on 07/31/2026: 8 public pages instead of dozens — main, login, registration, offer, terms, privacy, cookie, desktop. First server response 220.6ms, full load 329.8ms, the fastest of the 16 sites we measured. JSON-LD markup describes the service and the tariff, that is, the first version is immediately suitable for indexing.

Did not find your case?

Describe how it works on your side — we will tell you whether “MVP for a startup” fits and what it means in your situation. No brief and no call: one question, one answer.

Process steps

Transparent stages with approval at every step

Total duration:30–60 days

  1. Analysis of the plan

    3–5 days

    We formulate a hypothesis, divide the scenarios into "now" and "then", agree on which numbers we will consider the answer.

  2. Framework and data

    7–12 days

    Data schema, login, main screen. At this stage, it is already clear whether the idea has blown up.

  3. The main scenario

    10–20 days

    The same path for which everything is done: from the first discovery to the targeted action. The rest is after him.

  4. Analytics and payment

    3–6 days

    We set the measurement so that the sources and steps are visible, and connect the payment, if it is in the hypothesis.

  5. Launching

    2–4 days

    Domain, certificate, backups, monitoring. We transfer the code and access.

  6. Two weeks of observation

    14 days

    We look at what people actually do and compile a list of things that should be changed. Often, this is where the hypothesis is refined.

Technologies & integrations

What we build on and what it connects to

Stack

  • Next.js and TypeScript — one framework per server and interface, less room for error
  • PostgreSQL and Prisma: the data schema is described in the code, so changes to the first version do not break the database
  • Docker is the same environment in development and production, without "it worked for me"
  • GA4 from day one: See conversion sources and steps, not just number of visits
  • Deploy from an out-of-the-box image—upgrades take seconds, not minutes of downtime

Integrations

  • LiqPay and monobank — payment acceptance when willingness to pay is checked
  • Telegram — notification to the owner of each target action, while there are few and each one is important
  • Resend — letters to users: confirmation, restoration of access
  • GA4 - sources of transitions and behavior, the basis for the conclusion "it worked or not"
MVP or an immediately complete product

How this option differs from the alternative

When the first user appearsin 30-60 working days
The price of the answer "no demand"one first version
What to do with feedbackis taken into account in the next version
The risk is to do the wrong thingvisible early and cheap
What we need from you

We can't start without this — best to prepare in advance

  1. Description of the idea in an arbitrary form - we will structure it ourselves, you do not need a separate technical task
  2. Who is your first user and where is he now: without this, the MVP can't be shown to anyone
  3. What exactly will you consider confirmation of demand - registration, payment or return
  4. The deadline by which the answer is required: it determines how many scripts will fit
  5. Domain, if it already exists, and access to it

If something is missing — let us know, we'll help you gather it or do it as a separate task.

FAQ

Most frequently asked questions — with concrete answers

How long does an MVP take?

From 30 to 60 working days. The difference is not in the complexity of the idea, but in the number of scenarios of the first version. Most often, the deadline increases not because of development, but because the idea imperceptibly expands already during work - that is why the limit "now / then" is fixed before the beginning.

How is an MVP different from just a cheap site?

the purpose A cheap site is made to be. MVPs are made to get a response. Hence the other solutions: the analytics are applied on day one, not sometime later, and each scenario has an explanation of how exactly it helps to test the hypothesis.

And if it turns out that the idea does not work?

This is a normal result, and it is cheaper than the opposite option - to find out the same after a year of development. At a free analysis, we separately agree on what to do in this case: which piece of work will remain useful for the next attempt, and which will have to be thrown away.

Can the MVP then grow into a full product?

Yes, and that's why we don't make it "out of the box": the data schema, deployment, and analytics are done as a product. But honestly, let's say something else - if the hypothesis is confirmed that is not the one that was tested, the part will have to be rewritten. This is not a flaw of MVP, but its meaning.

Do you give away the code?

Yes, the code and all accesses are transferred to you. You can continue with another contractor at any time, you don't need to negotiate anything with us for this.

Do you need a technical assignment from us?

No. It is enough to describe the idea in an arbitrary form - structuring is our part of the work. If you already have a TOR, we'll read it, but we'll probably suggest shortening it: TORs usually describe a product, not a hypothesis test.

What if we have already started doing something?

Let's see what is suitable from what is available. Sometimes a framework saves weeks, sometimes parsing someone else's code is more expensive than writing it from scratch. Let's say directly what your case is - it can be seen during a free analysis.

Will there be a mobile app?

Not in the first version. The web works on the phone immediately, and the app adds an in-store checkout cycle that doubles the time. If the hypothesis concerns the application itself, we will say so in the analysis and calculate it separately.

Let's start with a hypothesis, not a list of functions

Describe the idea in any form - in 3-5 working days we will return with a one-sentence hypothesis, a list of scenarios of the first version and a "now / then" boundary. If it is possible to check without development, let's say so in the first email.

From measured casesMeasured on 07/31/2026: 8 public pages instead of dozens

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.