← Back to home

How to Choose a Web Developer for an MVP

Choosing a developer for an MVP isn’t about pretty portfolio screenshots. It’s about who will think about your product when uncomfortable questions show up. Below is a practical checklist I’d give to anyone hiring for a digital product for the first time.

What to trust, what to ignore

  • Trust: real case studies with decisions and constraints, not just screenshots.
  • Trust: a clear process — how they run discovery, lock requirements, show weekly progress.
  • Trust: full handover of code, domain and database from day one.
  • Ignore: low price as the main argument — that debt always gets repaid in rework.
  • Ignore: “we’ll ship it in a week” without a single question about your logic.

Freelancer vs agency vs product builder

A freelancer can suit a defined implementation task or a focused product build. Check whether discovery and product decisions are included, and who supplies them if they are not.

An agency can provide several disciplines and continuity across a longer project. Confirm who makes decisions, how progress is reviewed and which management responsibilities remain with you.

A solo product builder can connect scope decisions and implementation with one point of responsibility. Check availability, handover and the plan for work that needs another specialist.

Red flags

  • Doesn’t ask about users or metrics — they’ll build “as specified”, even when the spec is wrong.
  • No weekly visible progress.
  • Won’t push code to your repo.
  • Uses only a no-code tool but calls it “custom development” without naming the limits.
  • Ready to start with no written project frame.

Questions to ask on the first call

  • Which 2–3 of your past projects look like mine in logic, not visuals?
  • How do you capture requirements and prioritise?
  • What’s included and explicitly NOT included in this budget?
  • Are discovery, testing, launch and handover priced against the same scope, and which costs continue after launch?
  • How do you hand over the project — code, access, documentation?
  • What happens if a requirement changes mid-build?
  • How do you handle business logic — own it or wait for me to spec everything?

Why product background beats “can code”

For an MVP, technology is no longer the bottleneck. The bottleneck is product decisions: what to cut, what to keep, which mechanic to simplify, how to model roles. If the developer can’t reason at that level, you’ll have to spec every detail — and the product becomes only as good as your description.

I work as a Product Manager and hands-on builder at the same time: 10+ years in digital products across EdTech, SaaS, AI assistants and CRMs. You get someone who pushes back on shaky requirements and proposes a simpler path, not a task-taker.

Frequently asked questions