For founders

Build a SaaS MVP with AI, and put it in front of real users this week

A waitlist is not a product. An MVP is the smallest loop a stranger can finish and pay for, or refuse. Eqlo writes the accounts, the job screen, and a Stripe checkout on your own account. You still decide what stays out. Five projects stay free, with no card.

  • 2 to 5 minFirst draft
  • 1 weekIn front of users
  • $0Free, 1 seat
  • $19Plus, your domain

What an MVP must contain, and what it must not

An MVP must let a new person create an account, do the one job, and come back tomorrow. If money is part of the question you are asking, it must take a card, even a Stripe test card. A dashboard with no action is a slide. The first draft lands in two to five minutes. The week is for cutting screens, not for adding a second persona.

It must not contain a marketplace, a reporting suite, or a second role you cannot name. Those are how MVPs become unpaid roadmaps. Write the job in one sentence. Here is an illustrative scenario, not a named client: an invoicing tool for freelancers, one workspace, one invoice, one pay link. If a screen does not serve that sentence, it waits.

You can say so to a stakeholder: that is version two, after five people have finished version one. Generation can be wrong. Each exchange creates a version you can restore. Read the loop on a Thursday night before you send the URL.

The technical base you no longer write

Eqlo starts from the sentence and proposes accounts, a Postgres schema you can see, the main list, the empty state, and a settings page that is allowed to be thin. You correct the words. You add the rule only you know: who owns a workspace, what happens when a seat is removed.

Organizations and roles

A workspace is a tenant. Reader, editor, and administrator exist from the first version. Invitation goes out by email. You do not share a password. Team at $49 adds ten seats when the squad should not share a login.

Subscriptions and trials

You connect the customer Stripe account, never an Eqlo middle account. Subscription, one-off payment, deposit, or a free trial. European VAT and US sales tax go through Stripe Tax. Automatic invoices and a customer portal for cancellation sit on that same account.

Dashboard

A count of workspaces and a last-seen date. Not a full analytics suite. Enough to know if Thursday happened twice. Google Analytics can be asked for in one sentence when you want visits, not when you want a second product.

Activity log

Who changed a plan, who invited a seat, who exported a CSV. The log is how you answer a support mail without guessing. It is not a compliance programme. It is a trail you can read.

SaaS MVP workspace list with two tenants and a thin settings pane
The workspace list after the first draft: two tenants, a seat count, and a Stripe test plan, not a slide.

Multi-tenant from day one

Two companies must not see each other rows. That is not a later hardening. Eqlo scopes data to a workspace from the first version. A shared demo account is a choice you make for reviewers, not the default. Organizations for multi-tenant sit in the product facts, not in a future ticket.

Roles can start as owner and member. Fine-grained permissions wait until someone has asked for them twice. A first tenant that is only you is still a tenant. Do not build a single-user app and hope to split it in June. Direct read access to Postgres is there for the developer who arrives later.

CSV import and export keep a freelancer list movable. If you already have a sheet of early users, you load it. You do not retype forty rows because the first week was a demo.

Measure whether anyone wants the product

Five people who finished the loop and one who paid, even a small Stripe charge, tell you more than two hundred waitlist mails. Put a price on it early enough that a yes costs something. If nobody will pay, the copy might be wrong, or the job might be. Change one thing at a time.

Talk to the five. Watch where they hesitate. Eqlo is for changing the screen that afternoon, not for booking a sprint to discuss the hesitation. Select the element, write the instruction, restore the version if the change went too far.

A publishable brochure site around the MVP takes one to two hours of back and forth. The product loop is the thing you measure. The marketing page is the door.

Take the code back

When the loop is true and the next constraint is yours: a database you already run, a compliance review, a hire who wants the repository. Export is always available. Automatic GitHub sync sits on Plus. The npx eqlo CLI does pull, push, migrations, and deploy. REST and webhooks are there when another system must hear a payment.

Take it back too early and you will rebuild the empty states by hand. Take it back too late and you will fight a tool that was meant to get you to the first ten customers. The signal is usually a hire, a contract, or a limit you can name. The developers page is the longer version of that handoff.

Related pages

If you are still proving the flow, start with a prototype. If you are writing a waitlist, the founders page is closer. If a developer is about to open the files, that page takes over.

Frequently asked questions

Is this vibe coding?

You describe the product in English and get running screens. It is still your job to say what is out. A prompt is not a specification if you accept every extra screen. The vibe coding page is the longer definition.

Can I use my own design system?

Yes, once you have one. Colors, fonts, and radii apply to every screen at once. For an MVP, a small set you can replace is faster than inventing a brand in the first week.

What about a compliance programme?

An MVP can sit in a region you choose and use email, Google, or Apple sign-in. A compliance programme is a company process. Do not put medical data in a first week build unless you already know the rules.

Will engineers reuse this?

Often the structure, sometimes the screens. They will throw away anything theatrical. That is still cheaper than discovering the loop was wrong after a quarter. The repository is ordinary React and TypeScript.

How much should I charge on day one?

Enough that a yes is a decision. Plus at $19 or Team at $49 tests seriousness on your own tool. Free forever tests curiosity. Stripe stays on your account. Eqlo does not take a cut.

Write the loop. Put it in front of five people this week.

Five free projects, one seat, no card. Plus is $19 when the domain or GitHub sync is the missing piece.