Skip to main content
Back to Home

MVP to production · from ~€20,000

Full builds, led by the person writing the code.

Web applications, marketplaces and platforms: designed, built and operated. I lead every engagement personally and bring in specialists when a project needs them, so there is never a question of who is accountable for a decision.

Book a 30-minute call →

Price

from ~€20,000

Scoped after a Sprint, or after enough conversation that the number means something. I do not quote a build I have not thought about.

What is included

Architecture and stack decisions

Made explicitly, with the tradeoff written down, so you can hold me to them later.

Production build

Next.js, TypeScript, Postgres or MongoDB, AWS or Vercel. Chosen to fit your team's ability to operate it, not my preferences.

Infrastructure and deployment

GDPR-compliant data handling, monitoring, and a deployment process you can run without me.

Specialists when needed

Designers and additional developers, briefed and managed by me. You always know who is writing the code.

Handover that works

Documentation and a working local setup, because a build you cannot maintain is a liability, not an asset.

How a build gets scoped

Most builds start with a Sprint, because a fixed-price two days is a cheaper way to find out what a project really is than three weeks of proposal writing.

If you already know what you need, because you have a spec or have done this before, we can skip it. What I will not do is quote a six-figure build from a first conversation. That number would be fiction, and both of us would find out in month eight.

MVP first, when money is finite

For a bootstrapped or self-funded project I will almost always argue for shipping something small that can start earning, then extending it while it pays for itself.

That is how Fisherman's Lodge got built. A self-funded founder now runs the largest fishing tourism platform in Finland, because the platform funded most of its own development over two years rather than needing the whole budget up front.

What I will tell you before you commit

Which parts are routine and which are genuinely hard. Which parts you should buy rather than build. And, when it applies, that the idea does not hold up yet.

A medical client needed a browser-based DICOM viewer. Building one: roughly six figures and a year, to arrive at a solved problem. I integrated two proven open-source components instead and put the budget into the training platform, which is where the value actually was.

Not sure this is the right one?

Two days and a fixed price is usually the cheapest way to find out what you actually need.