Skip to main content
Work with me

Work with me

MVP development

I lead MVP projects as the product manager, with my team of developers, for founders and operators. Together we decide what the first version must do, the team builds it as a working web app and we put it in front of real users to learn what to do next.

01 / Audience

Who it’s for

  • Non-technical founders with a problem worth testing
  • Operators replacing a manual workflow with software
  • Teams that need a first version in front of users

02 / Deliverables

What you get

  • Scope brief: what is in the first version, what waits and why
  • User flows and a short PRD: the paths users take and the decisions behind them
  • Working web app: sign-in, data, email and a payment workflow where the product needs one
  • Analytics on the core funnel: tracking on the steps that tell you whether the product works
  • Launch and iteration plan: how to reach the first users and what to measure after launch

03 / Process

How we work

  1. Discovery

    I learn the problem, the people who have it and how they handle it today. Where I can, I talk to those people directly.

  2. Scope the smallest useful version

    We cut the idea down to the version that tests the riskiest assumption, and write down what is left for later.

  3. Build in increments with demos

    We build the app in working slices and demo each one, so you see progress and can change direction early.

  4. Launch to first users

    The app goes live for a first group of users, with analytics on the core funnel in place from the start.

  5. Measure and iterate

    We read what users actually did, decide what to change and plan the next round of work.

04 / Built with my team

What we built

05 / Related work

Related work

  1. Prodily logo

    Prodily

    I took it from problem to a launched product on my own, then rebuilt the experience after a learner said the old one was boring.

    lessons
    90
    capstones
    9
    users
    400+
    Launched Aug 2026 - Present
  2. RallyVerse logo

    RallyVerse

    It started from conversations with organizers and academies and covers the flow from registration and payment to event-day check-in, with analytics on conversion.

    events hosted
    3+
    community members
    500+
    partner organizations
    12+
    2026 - Present

06 / Questions

Common questions

I do not have a technical co-founder. Can you still help?

Yes. That is a common starting point. I handle the product decisions and lead the build with my team, and I explain the technical trade-offs in plain language so you can make the calls that are yours to make.

I only have an idea. Where do we start?

Start with product strategy. We work out who the problem belongs to and whether it is worth solving before anything is built, and the MVP follows from that.

What happens after I send the form?

I read what you sent and reply by email, usually with a few questions. If it looks like a fit, we set up a call to talk through the problem and the scope.

How much does an MVP cost?

It depends on what the first version has to do. Share your budget in the contact form and I will tell you what can realistically fit inside it.

What stack do you use, and why?

Usually Next.js and TypeScript on the front end with Node.js on the back end. It is a widely used stack, so another developer can pick it up after us, and it covers websites and web apps alike.

Work together

Have a project in mind?

Tell me what you want to build, and share the scope and budget you have in mind.