Ex-Disney · Ex-Globant · Freelance since 2014
MVP development by a senior engineer who has shipped before.
I take founder ideas from napkin sketch to real product users can pay for. Pragmatic scope, modern stack, honest estimates — you get a working MVP, not a Figma deck.
Validate your ideaScoped to what matters, nothing more
First 90 minutes are free and the deliverable is a written scope: what's in, what's out, what's cheap to add later. Most MVPs get smaller in this call, not bigger.
One engineer, full-stack coverage
Landing, dashboard, backend, mobile and deployment — same hands. Zero "that's the other team's bug" moments. Faster than a squad for anything under 3 months.
Built on tech you can hire for
Next.js, NestJS, PostgreSQL, React Native. Not a cult stack or this month's JS framework. When you need to hire a team later, the market exists.
You own it from day one
Clean repo in your GitHub org, deployed under your account, proper handover document, no hidden dependencies on me. Walk away anytime without damage.
The MVP stack I deploy with
- Next.jsLanding, marketing site and dashboard in one deploy
- NestJSBackend with modular architecture from day one
- React NativeMobile layer when web isn't enough for your users
- TypeScriptTypes across web, mobile and server — catch bugs at compile time
- PostgreSQLBoring, transactional, reliable — your default
- SupabaseAuth + DB + storage when you need to move in days, not weeks
- StripePayments, subscriptions, invoices and tax automation
- VercelDeploy previews, edge functions, zero-config hosting
- DockerContainerized backend when Supabase isn't enough
- Claude APILLM features without reinventing the agent layer
- OpenAIEmbeddings, structured output, fallback provider
- MixpanelActually measure what users do, not just page views
What an MVP actually is (and isn't)
An MVP is not "version 1 with half the features". It's the smallest thing that lets you test the one assumption your business depends on. If your pitch is "users will pay for AI that drafts legal contracts", the MVP tests exactly that — not the brand, not the admin panel, not the dashboard for a team you don't have yet.
The biggest cost in MVP development isn't engineering hours, it's scope drift. Every "while we're at it, can we also..." pushes launch back two weeks. My job during scoping is to push back harder than you expect — because the features you remove now are the ones you'll happily build later with real user feedback, and the ones you insist on now are often the ones users ignore.
Typical MVP shape: a landing page that collects the right signal (not just emails), a login flow, the core feature that tests the bet, a payment path (even if manual), and analytics that answer "is this working?". That's it. Admin panels, social login beyond Google, internationalization, fancy onboarding — later. Most of it never ships because real users want different things than the founder expected.
I've built MVPs for tourism operators (Argenway, which evolved into a full ERP), healthcare scheduling (Maeth, which grew into a multi-specialist platform), and mobile-first hospitality networks (Greether, now in 28 countries). None of them launched with more than 30% of what was originally scoped. All of them found product-market fit faster because of it. If you want a partner who says "let's cut that feature" more often than "let's add one", we'll get along.
FAQs
4 to 10 weeks end-to-end depending on scope. A v1 login + core feature + Stripe flow is usually 4-6 weeks. Add mobile, and it's 8-10. I'll give a fixed timeline after the scoping call — no moving goalposts.
Fixed-scope MVPs start around USD 8K and scale to USD 30-40K for something complex with web + mobile + AI features. I'll quote after scoping. If your budget is lower, I'll tell you what I'd cut to fit it instead of quietly cutting corners.
Yes — this is how most MVPs actually ship. I work directly with whoever owns the product decisions. I've partnered with solo founders, two-person teams, and product owners inside small companies. Figma, Linear, Notion, whatever you're already on.
Two options: a 2-4 week post-launch retainer for the first wave of fixes and feature iteration, or a clean handover to your team. I don't lock you in — the code is structured for whoever comes next to understand it.
Yes, from the first commit. The repo lives in your GitHub organization, not mine. Full IP assignment in the SOW. I don't do work-for-hire with strings attached.
Very rarely, and never instead of cash — only as a small top-up when the project looks exceptional. I've been a freelance engineer since 2014 because cash works. If you can't fund an MVP, you'll struggle to fund its operation.
Ready to get your MVP shipped?
First scoping call is free and comes with a written scope. 24-hour reply time, no sales funnel.
Tell me about your idea