MVP development: a first version real users can try
The point of a minimum viable product is to learn whether your idea works, as quickly and cheaply as you responsibly can. That means building the smallest version that delivers real value — and building it well enough that you can keep it if the idea takes off, rather than starting again.
I've done this for myself: AlignCV went from an idea to a product in private beta that I designed, built and run on my own. I bring the same approach to founders' products, technical or not.
Is this you?
- You have an idea and want to test it with real users before raising money or spending more
- You're not technical and need someone to turn the idea into working software
- You have a prototype or no-code version that's hitting its limits
- You need to show investors or early customers something that works
What I can build for you
- Scoping the first version
- Working out with you which features prove the idea, and which can wait. This is often the most valuable part.
- A working, deployed product
- A real application on a real domain, ready for users — not a clickable mock-up.
- Foundations that can grow
- Sensible architecture, data model and code structure, so success doesn't mean a rewrite.
- The essentials, done properly
- Sign-in, security, sensible error handling and the admin tools you'll need to support early users.
- Iteration after launch
- Changes based on what you learn from users, if you want to keep working together.
Relevant experience
AlignCV
Founder and sole engineer, independent product
An independent product taken from concept to private beta single-handed: product design, CV parsing, a structured match engine, AI-assisted tailoring with a provenance check, and DOCX and PDF generation.
DHUB Education
Full-stack software developer, sole developer
A first website for an organisation that had none, delivered end to end — from the first build to production.
How it works
Every project follows the same four stages — discover, define, build, and ship and support — scaled to the size of the job. We agree the scope and price in writing before the build starts, you see working progress regularly, and you finish with documented software you own. See how I work.
TechnologiesTypeScript, Next.js, React, Node.js, NestJS, PostgreSQL, Redis, AWS. I choose mainstream, well-supported tools so you can hire for them later.
Common questions
I'm not technical. Is that a problem?
Not at all. I'll explain decisions in plain English and ask about your users and business, not your technology preferences. You need to know what problem you're solving and for whom; I'll handle the rest.
How small should an MVP be?
Small enough to build and launch quickly, big enough that someone would genuinely use it. In practice that usually means one core workflow done well, plus sign-in and the basics. We'll decide together during scoping.
What happens after the MVP?
You'll own the code and have documentation. You can carry on working with me, bring in your own team, or hire developers — the codebase is built to make any of those straightforward.
Can you sign an NDA?
Yes, I'm happy to sign a reasonable NDA before you share the details of your idea.
Related services
Tell me what you're trying to build.
Discuss a project