MVP and SaaS development for startups

An MVP is the smallest version of your product that real people can use and pay for, so you learn whether the idea works before spending on everything else. I design, build and launch MVPs and small SaaS products for founders in India and abroad.

Ships
Sign-up, the core feature, payments and an admin view
Built with
React, Next.js and cloud hosting
Shipped
Mailwright, inventory software and a dozen experiments
You own
The code, the accounts and the product

Updated . Rushan Haque.

01

What goes into a first version

  • One core job

    The single thing your product promises, done well, from first click to result.

  • Accounts

    Sign-up and sign-in, so you know who your first users are.

  • Payments

    Subscriptions or one-off payments through Stripe or Razorpay, if you are testing whether people will pay.

  • An admin view

    Where you see users, activity and payments without asking a developer.

  • A way to learn

    Simple analytics and feedback, so the next version is decided by evidence.

02

What stays out

Everything that does not test the idea: extra settings, every edge case, a mobile app when the web will do, and features that one early user asked for once. They come later, if the first version earns them.

03

Products I have shipped

Mailwright, a mail merge and bulk email tool; an inventory and quotation system for product businesses; and public experiments such as Quorum, where four people answer privately about you, and Superlatives, anonymous nominations for groups. Each went from idea to something people could use.

04

How it runs

  1. 01
    Write down the one promise

    Who the product is for and the job it does for them, in one sentence.

  2. 02
    Design the key screens

    A clickable prototype you can show to potential users before the build.

  3. 03
    Build in short rounds

    Working software on a live link after each round, so you can test it as it grows.

  4. 04
    Launch and learn

    Released to your first users, then improved from what they actually do.

Websites I’ve built recently.

05

What clients ask

How long does it take to build an MVP?

Weeks rather than months when the scope is kept to one core job. The timeline and the feature list are agreed in writing before work starts.

Do you work with non-technical founders?

Yes. You bring the idea and the customers; I turn it into a product, explain the decisions in plain language, and keep the technical choices simple to hand over later.

Who owns the code and the product?

You do. The code lives in a repository in your name and every account is registered to you.

Can the MVP grow into a full product?

Yes. It is built on the same tools a larger product would use, so growing it means adding to it, not starting again.

Can you help design the product too?

Yes. User flows, screens and the visual design are part of the work, not an extra.

Got something worth building?

Tell me the one thing your product has to do, and you will get a written plan for a first version people can use.

Explore