I build the first version of your product myself: product design, development, security, deployment and SEO basics. In 4 to 8 weeks at a fixed price, without assembling a team before you have customers.
The final scope, price and timing are confirmed before work starts.
An MVP is the essential. The rest is built from data.
One screen that does the main thing, sign-in and data. Roles, payments and integrations come once the first users show what is actually used. That saves money and months.
- 01the idea: one thing the product must do better
- 02only the essential: sign-in, overview, three features
- 03first users: measurement and feedback
- 04the next step: based on what gets used
The demo shows i-eduko.cz, the digital platform for a publisher I built. The code on the plate is a demo, not the project source. More work is in the portfolio.
Diagram of an MVP in four steps: the idea, only the essential, first users, the next step built from data.
Related work in practice
A concrete project with desktop and mobile previews. No illustrative mockup, just a real website, e-shop or digital product.
I-Eduko
Digital platform for a publisher, Digital platform for the EDUKO publishing house: it manages its digital content and delivers it to students via QR codes in printed textbooks, interactive exercises, 3D models and learning videos.
What you actually get
No fog: what you get, who it fits and where a larger scope begins.
Clear deliverables
- narrowing the idea down to one feature that can actually be validated
- design of the screens needed for a user to get through it
- a working application deployed on your own domain
- sign-in, payments or a waitlist depending on what you are validating
- tracking that shows whether people really use it
Best fit
- you need to validate an idea with real users, not in a deck
- you have a deadline: investor, accelerator, conference
- you are willing to cut from the first version to make it
Not a fit
- you want a finished product with everything, just labelled MVP
- there is nobody who can decide on the product
- you are looking for a technical co-founder for equity, not a supplier
Scope boundaries
from€3,200
A fixed-price MVP from €3,200 is one main feature and four to eight weeks of work. Incremental development at €40/hour makes sense while the scope is still moving. Technical partner from €600/month is ongoing capacity for a startup already running. Domains, hosting and third-party services are paid directly to the provider.
Three ways to work together
I work for money, not equity. We define the MVP scope in a discovery workshop (90 minutes, free), then you get a fixed price and a deadline.
Fixed-price MVP
For: a startup with a clear idea that needs the first version live
from€3,200
Delivery in 4 to 8 weeks
- Landing page + sign-in + main screen
- Max 3 core features (one key process)
- PostgreSQL + auth (Supabase)
- Basic admin and e-mails
- Cloud deployment, domain, measurement
Everything included (+4)Everything included (+2)Show less
- Basic admin and e-mails
- Cloud deployment, domain, measurement
- Security: roles, permissions, backups
- 90 days of support after launch
Ongoing development
For: a startup with its own product owner and a changing scope
€40/h
- Work in sprints, you control the scope
- Weekly overview of hours
- Same stack and standards as the MVP
- Also for taking over an unfinished product
- No minimum commitment
Everything included (+2)Show less
- Also for taking over an unfinished product
- No minimum commitment
Technical partner
For: a launched product that needs someone to look after it
from€600/mo
- Fast response to bugs and outages
- Development based on user feedback
- Updates, security, backups
- Technical support in investor conversations
- Handover to your team when you have one
Everything included (+2)Show less
- Technical support in investor conversations
- Handover to your team when you have one
A startup needs a product, not an org chart
Before you find a technical co-founder, before you assemble a designer, a frontend and backend developer and DevOps, the first version can already be live and collecting answers from real users. That is what I do: I handle the whole process from brief to deployment myself, because web, apps, design, SEO and security are my everyday work, not four separate professions.
An MVP is the smallest version someone will pay for or start using. Not a half-finished product, but a sharp cut: one core process, sign-in, basic admin, measurement. Everything else waits until you know people want the product.
I build on a proven stack any other developer can pick up: Next.js, React, TypeScript, PostgreSQL via Supabase, Stripe and cloud deployment. The code, accounts and domain are yours from day one. When your team arrives later, nothing needs a rewrite.
Everything I take care of
What you concretely get out of the collaboration.
- 01
Brief and product design
We turn the idea into a brief: who the user is, which single process must work, what can wait. Wireframe and visuals in your brand's language, not a template.
- 02
Development and data
Frontend and backend, database, sign-in, roles, Stripe payments, e-mails, an API for future integrations. One stack another developer can take over.
- 03
Security and operations
Verified sign-in, row-level data permissions, abuse limits, backups, secrets outside the repository, GDPR. Error monitoring from day one, no "we'll fix it later".
- 04
Launch and growth
Deployment, domain, measurement (GA4), SEO basics and a landing page that sells the product. After launch I stay on as your technical partner.
How it works
No unnecessary bureaucracy. Every step has a clear output and deadline, you always see exactly where we are.
- Typically
- 4-8 weeks
- Steps
- 4
Brief
48 hWhat the first version must and must not do. Within 48 h you get scope, price and timing, no team to assemble.
Design
1 weekScreens, data model, payments and sign-in. You approve a clickable preview.
Build by milestones
3-6 weeksEvery milestone is deployed to staging, so the first users can come in before everything is finished.
Launch and handover
after launchDeployment, tracking, documentation. The code is yours and any team can take it over.
Common questions
The ones asked most. Missing something? Write to me, I reply within a few hours.
An MVP (minimum viable product) is the smallest version of a product someone will actually use or pay for. It includes one key process, sign-in, basic admin and measurement. It does not include ten "just in case" features. We agree the scope in a workshop and write it down so the fixed price holds.
Describe the idea, get an estimate within 24 hours.
Three sentences about what the first version should do and for whom. Within 24 hours you get an estimate of scope, timeline and price plus an invitation to a discovery workshop (90 minutes, free).