Moduluz

MVP & product builds

From idea to a launched first version that real users can sign up for, use and pay for, with the scope cut to what proves the idea.

What you get

  • A live product with sign-up, the core workflow and, where it makes sense, payments.
  • A written v1 scope, with the reasoning behind every cut.
  • A team ready to keep building once you learn what users actually do.

Good fit if

  • You have an idea, early customers or a waiting list, and no technical team yet.
  • You need something real to show investors or pilot customers, not a slide.
  • You've had a build quote that tries to do everything at once.

Probably not a fit if

  • You want every feature from the pitch deck in version one.
  • You need a clickable prototype only. We build working software.

The first release, drawn out

Every engagement starts by breaking the work into parts and deciding what the first release needs. This drawing is an example to show the thinking. Yours will be drawn from your own users and goals.

12345678

Example: a booking app for independent physiotherapists

In v1Later

  1. Sign-up for therapistsNo therapists, no bookings. The whole idea starts here.
  2. Availability calendarThe core job. If this is clumsy, nothing else matters.
  3. Patient booking pageOne shareable link per therapist. No patient accounts needed yet.
  4. Email remindersMissed appointments are likely the pain therapists feel most. We'd test that first.
  5. Online paymentsTherapists already take payment at the clinic. Add it when they ask.
  6. Patient recordsBrings privacy rules and weeks of work. Prove the booking habit first.
  7. Directory and searchA marketplace only works once there are therapists to list.
  8. Video sessionsA different product. Revisit if users pull you there.

How it runs

  1. Pressure-test the idea

    We ask who the first hundred users are, what they do today, and what would make them switch.

  2. Cut to v1

    We write the smallest version that proves the idea, and a list of everything we're deliberately leaving out.

  3. Build and show weekly

    You click through real software every week and decide with us what changes.

  4. Launch to real users

    We launch, watch how people use it, and plan the next version from evidence rather than guesses.

What we won’t do

  • Build the whole roadmap as version one.
  • Pick technology because it's fashionable rather than right for your stage.
  • Disappear after launch. That's when the real learning starts.

Tell us what you’re building.

A few lines is enough to start. We’ll reply with questions, not a sales deck.

Start a conversation

Or write to

Useful to include

  • What you want to build, in your own words
  • Who will use it, and what they do today instead
  • Where you are: idea, prototype, or live product
  • Any date that matters, like a launch or a pitch