THE WHOLE IDEA
Not a product. Not a platform. Not a project with a roadmap and a kick-off. Something that was in your way on Tuesday, running on Tuesday afternoon.
saasie
A small web app, built by a code agent because somebody asked for it, that solves one imminent problem.
The app you wish existed — the one nobody was ever going to build for a group of five.
From SaaS, made small. Software as a service, for a service of exactly one.
Make one: every book you own ↗One problem ✦ One app ✦ Live on the web ✦ Yours to change
THE SHAPE OF IT
Not a nice-to-have you will get around to. A thing that is in the way today — the spreadsheet nobody can edit at once, the sign-up sheet on the fridge, the four people asking you the same question every week. Saasies come from irritation, not from strategy.
A Saasie has no settings page, no plans, and nothing in it that somebody else asked for. It is small because small is what makes it finishable — and because the second job is a second Saasie, which costs you another sentence rather than another release.
Every Saasie gets its own address — yourthing.saasie.app — and that address answers from the moment the name is claimed. There is no staging step and no preview to graduate from. What your agent builds is the thing that is running.
You ask for the next version in the same plain language you asked for the first. No tickets, no versions to plan, no release notes. The app changes because you said so, and it is live again a few minutes later.
NONE OF YOUR BUSINESS
Everything below exists, and your Saasie uses all of it. You are simply never the one holding it.
Your Saasie has one. Your agent pushes to it. There is no GitHub to sign up for and nothing to connect, and you never have to look at it.
There is one, and it is created, connected and kept running for you. You do not have to know what that sentence means — only that the app remembers things.
No server to pick, no region to choose, no domain to buy, no certificate to renew. The address works, on the web, over HTTPS, from the first minute.
The pipeline, the deploy, the logs, the email it sends, the numbers it counts. All of it is already there and already connected.
What we ask of you is an email address, and a code from your inbox once. That is the entire list.
AND THEN?
Plenty of Saasies stay one screen forever, and that is a success. But nothing about being small is a ceiling — a Saasie that keeps proving useful gets asked for more, and grows into the thing you actually run on.
You describe the thing that is annoying you. A code agent builds it, deploys it, and gives you the URL. Nothing about this stage is an investment — if it turns out to be wrong, you switch it off, and an afternoon is all it cost you.
Some Saasies are opened once. Others quietly become the way something gets done. You find out by using it, which is faster and more honest than deciding in advance.
The operator — whoever owns the Saasie — asks for changes in plain language, and the agent makes them. Add the bit you realised you needed. Fix the bit that annoys everybody. Each request is another push, not another project.
Enough of those, and the small thing is not small any more. It has users, a shape, and a job in your week. It got there by being useful at every step, which is not how most software is built.
WORTH BEING PLAIN ABOUT
NOW YOU KNOW