AI MVP development: a first product version you can put in front of users
An MVP is the smallest version of a product that tells you whether anyone needs it. I help decide what goes into the first version and I build it myself: mobile, web, or both, with AI inside when it makes sense.
Who it is for
- Founders with an idea who want to test it without building a big platform first.
- Companies testing a new product next to their main business.
- People who validated the problem in interviews and need something users can actually try.
What I can do
- A scoping session: what is the core and what waits.
- UX flows and architecture that do not block later versions.
- A web app (Next.js) or mobile app (React Native) with auth, database, and payments if needed.
- An AI feature as part of the product, not a landing-page add-on.
- A landing page and basic analytics to see what early users do.
How I work
01
Workshop and hypothesis
We write down what should be proven: who, what problem, and which user behavior counts as success.
02
Scope
We cut features down to the minimum that tests the hypothesis.
03
Two-week sprints
After each sprint I show a working product and we decide together what goes into the next one.
04
Clickable version
The goal is a version your first users can click through, as early as possible.
05
Iterations
We look at data from the first users and decide what comes next: grow, pivot, or stop.
- I do not give fixed timelines, because they depend on the size of the app. After every sprint you see what is done and what is left.
- I bill hourly and invoice as a B2B contractor.
- I design the UX and UI myself, alongside the code.
- I reply to messages within 24 hours.
Projects that back it up
CarSense
A mobile AI MVP: from an empty repo to most key screens and flows in 25 hours of work.
See project: CarSenseTableID
A complete solo SaaS: backend, frontend, auth, payments, docs, a Make module, and a landing page.
See project: TableIDMemeMatch
From discovery to a released app: 5k+ downloads and about 6,000 leads around launch.
See project: MemeMatchTechnologies
FAQ
What should go into an MVP?
Only what tests the main hypothesis. If you can still see whether people want the product without a feature, that feature waits for the next version.
How long does an MVP take?
It depends on the size of the app, so I do not give a fixed timeline. After the workshop and the written scope I work in two-week sprints, and the goal is a version you can click through as early as possible. I built the first CarSense MVP in 25 hours, and around 90% of the app was already working at that point.
How do you bill for an MVP?
Hourly, on a B2B invoice. After every two-week sprint you see what was built, and we can change priorities for the next one.
Web or mobile first?
Web ships faster and is easier to change. I pick mobile when the product needs the camera, notifications, location, or has to live on the user’s phone.
Will the MVP need a rewrite?
Not necessarily. I build on a stack the product can grow on and leave code that can be extended.
Read next
Tell me what you want to build
A few sentences are enough: what problem you solve, for whom, and what you already have. I reply within 24 hours with questions or a workshop proposal.