Five sites in production for a joke, in under a day.

With agents, a disposable idea becomes a real product in a few hours. To learn anything from it, you still have to launch it.

1h30of my time for six projects, from idea to going online

Translated from French in October 2026, with AI assistance. Read the original

Contents 6
  1. Six jokes, six products
  2. Two requests, not one line of code
  3. Three hours, minute by minute
  4. A product, not a mockup
  5. Testing products, not just concepts
  6. The test starts at launch

On September 29, the White House signed an executive order requiring federal agencies to say “Super Intelligence” instead of “AI”. A topical joke lives a few days. Right away, I asked an agent for puns in .si, Slovenia’s extension. An agent is an AI you hand a whole task to, which searches, codes and checks on its own before coming back.

Two hours and ten minutes after that request, six first versions of sites were ready. Seven minutes later, the first one was online, on a temporary Cloudflare address. Less than twenty hours later, five sites were running on their own domains.

What I take from it: with agents, when you have both product curiosity and technical know-how, you can test real products rather than concepts, because those products are disposable. And where I fell short: a product you don’t launch tests nothing.

Six jokes, six products

The names are French puns built on the .si ending.

Two requests, not one line of code

My first request fit in two sentences:

“Can you find me easy-to-remember puns for a future SaaS in .si (in French?), since everything is blowing up with Trump signing an order to rename AI as SI (super intelligence)? I can already see that simaman.si (the song) is available.”

Si maman si is an old French pop song. The agent checked which names were free and gave me its favorites. I kept six: simaman.si, which I had found, idio.si, to make fun of the order, and four of its own, turning down two of its favorites. Twenty-three minutes after the first request, the six names were in my cart, and I sent the second one:

“Create a GitHub repository for each new domain name […], then launch one agent per domain name to find ideas for what the site will do (favor the small experiment, the small satire, rather than a BIG SaaS that will eat all my time).”

Six agents searched in parallel for seven minutes: 89 web searches, 44 ideas, one recommendation per name. I kept them all as they were. An agent wrote one brief per repository, then I launched six Claude Code sessions, one per site, with the same instruction:

“Read BRIEF.md and AGENTS.md, then take the first step. Deliver the MVP up to a green pnpm build and a passing wrangler deploy --dry-run. Ask me before any real deployment.”

The agents came up with the uses, wrote the briefs and the code. I chose the moment, the names and the size of the projects: small enough to be willing to throw them away.

Three hours, minute by minute

Timeline of the first three hours: six lanes, one dot per commit, in time elapsed since the first request, and a triangle when a site goes online
One lane per site, in time elapsed since my first request (labels in French). Each dot is code saved by an agent (a commit); in green, guardrails and fixes.
Time elapsed What happens
0 I ask for puns in .si.
23 min Six names in the cart. I ask for one repository and one agent per name.
27 to 37 min Six agents search in parallel and each recommends a concept. I keep them all and ask for the briefs.
1h23 I launch six Claude Code sessions, one per site, within 48 seconds.
1h31 to 2h10 The six first versions. At 2h01, I ask for guardrails against a surprise bill.
2h17 First site online. The second follows four minutes later, the third at 2h58.

My own time: about 1h30 for the six projects, from the first request to going online, interface redesign included. On the first afternoon, I sent 33 messages, almost all of them one line long after the launch: “2$”, “commit”, “je t’autorise !” (“you have my OK!”). The agents, meanwhile, put in more than six hours of work that afternoon, and nearly fourteen hours over five days.

Over five days, polishing included: 190 commits, all co-written by an agent, and about $410 of tokens valued at public API prices, excluding domains and hosting, $120 of which for the first afternoon of the six coding sessions. No Claude Code session needed to be interrupted.

A product, not a mockup

Going fast wasn’t enough: I wanted sites you can open to the public and leave running without thinking about them. Take idio.si: it fetches any address a stranger gives it. Done badly, that means a nasty bill, or a door into its host’s network.

Part of the guardrails were in the brief, before the first line of code: read only public web pages, never an internal address (the anti-SSRF defense), with a limited timeout and size, and at most one visit every six hours to the same site. The brief also set the rules for the satire (translated from French):

Companies still at 100% “AI” are “Still Artificially Intelligent ✓”: we congratulate them, we don’t accuse them. […] We never attribute intent to anyone: only the numbers speak.

The other part came at the end. I asked the six sessions a single question: “are you putting guardrails in place to avoid a surprise bill […] or is there no need?”. Meanwhile, other agents were reviewing every change, looking for flaws. The result: quotas you can’t get around by switching IP addresses, a daily cap on the AI budget, share links that never store the original text.

Two years ago, the question was: “can I code it?”. It has become: “do I know what to ask for?”. I wrote neither the code nor the briefs. My technical experience helped me pick a stack I know how to run, and ask about costs at the right time.

Testing products, not just concepts

In November 2024, my first app built with an AI had to be constantly steered back. Today, I only step in for costs and permissions.

I would never have coded these six sites by hand: by the time they shipped, the joke would have been dead. At two hours and about $120, they become a reasonable bet, and above all a disposable one. When building costs so little, I dare to try ideas I would have dropped before writing a line of code. A mockup shows an intention. A product online lets real people use it, and you throw it away if it doesn’t catch on.

It takes two things: product curiosity, which spots an angle in the news and is willing to aim small, and technical know-how, which knows what a service in production demands. Here, both lived in one person. In a company, it can be a developer curious about the product, or a developer and product owner pair: that’s what I call an intrapreneurial mindset.

On a team product, with old code and customers, the same speed needs a harness: continuous integration, tests, review. That’s another subject. Here, I’m talking about the ideas we would never have built.

The test starts at launch

The test, as it happens, I barely ran. The brief said so from the start: “Launch (done by Tristan, not by you)”. Five of the six repositories contain a launch kit prepared by the agents: copy, images, threads for X, Reddit and Hacker News. I used only a piece of it: one X thread for idio.si, two days later, whose first post got 131 impressions. For that site alone, communication took me about 3 hours, including an X bot to promote it: twice the time spent building all six. Six days later, the five sites had fewer than twenty visitor actions between them, my own tests included. With so little use, I can’t say whether these ideas interested their audience.

The most concrete feedback came by chance, at a restaurant. My best friend wanted to see simaman.si, which I didn’t even think was online. He sent it to his mother, who took the test and replied: “I’m so good at this”. The site was designed to travel exactly like that, from a child to their mother on WhatsApp. Five days between the idea and a real user’s reaction: it’s possible, but only if someone sends the link.

In this experiment, the bottleneck was no longer production, it was decisions. Two sites waited for my go-ahead until the next day, pasdesou.si for a week: the agent isn’t allowed to deploy without my consent. Its spending cap in dollars, set by hand, is still waiting; a limit on calls stands in for it. What still costs is deciding to launch and owning the act of showing something funny in public. Running six sessions at once also scatters attention; I measure what that costs in The apple tree and the basket.

For the next experiment:

  • The launch becomes part of the definition of “done”. A project isn’t shipped until its link has gone out to its first users.
  • I prepare distribution before coding: who I send the link to, where, and when.
  • One bet at a time when it has to be distributed. Six sites in parallel means six launches to do, and I did one.

My agents gave me six products in two hours. I still have to learn how to put them in people’s hands.

Written with the help of AI, from my notes, my ideas and the data from my agent journal.