Forty public projects you can open, fork and reshape with a few sentences.
Browse templatesSeparate client workspaces, white label, and the Git repo handed over at the end of the engagement.
See the programmePaste a URL. In thirty seconds you see exactly what Google receives before any JavaScript runs.
Check a URLA committee that has not clicked will argue about a slide. A committee that has typed an email into a waitlist has a fact. Eqlo is for the launch page, the list, the thin demo, and a data space you can open. Five projects stay free, with no card.
Pitch week is a sequence of rooms that each want a different object: a page a stranger can find, a list that proves someone cared, a demo a partner can click without you narrating, and a place where the first rows live. Most founders arrive with one deck and a promise to have something by Monday. Name the three frictions before you open the editor, or you will generate a fourth object nobody asked for.
The sentence is ready. The page is a toggle list that looks like notes. A stranger will not scroll a pile of headings. You need one promise, one form, one count. A brand system invented at 1am is not the trade-off. The trade-off is a URL the committee can open on a train.
An investment committee will not wait for your call. They will open the link and tap the wrong thing. If the only happy path is the one you click, you do not have a demo. You have a tour. A clickable flow with an empty state and a back button survives a room you are not in.
Folders of frames age in a day. A partner asks whether the invite works and you send a new PNG. Every hour exporting pictures is an hour you do not spend on the five people who already asked. A live project with a visible Postgres schema is a better appendix than a ZIP.
You do not need a hire to get these four objects into a stakeholder hand. You need a sentence, an afternoon, and the discipline to leave the rest out. The full tenant loop lives on the SaaS MVP guide. Here you are collecting proof that the room should fund the next cycle.
You describe the offer in one line. Eqlo writes the page, the navigation, the copy, and the form. The first draft lands in two to five minutes. The rest of the hour is for cutting the second product you did not earn, putting in the date the list closes, and reading the empty state. Do not add a pricing table you cannot defend.
One field, a count you can read on Monday, a rule that the mail must be a work address if that is the pitch. Each chat exchange creates a version you can restore. You compare the long form you almost shipped with the short one. Forty people who typed a work mail are a fact. Two hundred scraped badges are not.
The three screens the committee will argue about: sign up, the job, the empty state. Not a marketplace. You can start from a screenshot of a tool you already hate, or from a PDF of the deck. Share a link. Sit on your hands while someone who is not you tries to finish the loop. Pinned comments land on the step that failed.
A visible Postgres schema for the first sign-ups, the invites, and the notes you will write after the room. CSV import if you already have a list. Roles so a reader cannot edit. Direct read access when the first developer arrives. This is not the product. This is the room where the first rows live so you stop mailing screenshots.
This is a worked example, not a named company. Take a founder who is preparing a seed conversation for a clinic roster. The committee has seen a twelve-slide deck and asked for something they can click before the next room. There is no engineer on payroll. The budget is already a trade-off against two more months of runway.
On Monday the founder types a sentence: launch page for a clinic roster, waitlist of practice managers, write to them on Friday, United States only. The first draft lands in a few minutes. A pricing table that was never earned gets cut. The page is live that evening. By the next week the list holds a few dozen work mails. Twelve get a short note. One practice agrees a six-week paid pilot.
For the room, three links go out: the page, the demo (sign in, this week roster, an empty Thursday), and a one-page note on what is out. Two partners open the demo on their phones before anyone sits down. They argue about the empty Thursday, not the market slide. That is the sign-off. The SaaS MVP page is for the week after, when the question becomes tenants and a card.
Keep the deck if it still opens the room. Keep the investor sheet, the mail tool, and the note that is only for you. Eqlo does not want to be your customer file or your cap table. It wants to be the live objects those tools keep pointing at.
If you already have a designer or a Friday developer, keep them for taste and for the join you cannot describe. Stripe stays the customer Stripe account when a pilot takes money. Google Sheets can stay the place you dump a CSV export. Notion can stay the private note. The first version is cheap. Judgement is not.
Stop when the next constraint is a system you do not run: a clinic identity provider, a roster you do not own, a review that wants the repository in their pipeline, a hire who will live in the files. Export is available at any time. GitHub sync is automatic from Plus.
Take the code back too early and you will rebuild the empty Thursday by hand. Stay too long and you will ask Eqlo to become the product you described to the committee. The signal is a paid pilot that needs a real join, or a legal review that names a repository. Until then, cut the extra screen and put the link in front of the next five people.
Acceptance is a stranger finishing the loop. Release is you deciding the loop is true enough to fund. A very specific trade or a regulated health file will need a developer. Generation can be wrong. Read it before the room.
When the question is the smallest loop a stranger can pay for, use the SaaS MVP guide. When you are still proving a flow for a team, the prototyping page is closer. This hub is the role view.
No. A waitlist is a fact about curiosity. An MVP is a loop a stranger can finish and refuse. Use this page to get the list and the demo into the room. Use the SaaS MVP page when you are ready to ask for money or a weekly return.
Three links and a one-page note on what is out. The launch page, the clickable demo, the count. If they cannot click, they will invent objections. A ZIP of screenshots is how a room stays on the slide.
Free is $0 for five projects and one seat. Plus is $19 a month and three seats when you want a custom domain later or store builds. The real cost is the week. Spend it on ten conversations and one pilot that costs the buyer something, not on a second persona.
Yes. The project is yours. A full export is available at any time. Some founders keep the waitlist as the public face. Some hand the repository to the first hire. Both are a release.
You still have the list, or a demo that died in five minutes. That is cheaper than a quarter of build. Write, change one sentence, or stop. A clean no is a kind of sign-off.
Five free projects, one seat, no card. The repository is yours when you hire.