Monday, 11:30 · Marguerite Fontaine, Writer
The live page, edited safely
Marguerite edits the live pricing page. Visitors still see last week’s until someone publishes the changes.
Publishing →Use case · Startup
The product changes every week. The site keeps up without a developer.
Lumen ships every Tuesday. The pricing page, the model list and the changelog change with it, and the founders rewrite the homepage once a month. Their developers are busy with the product. You built the site so the marketing team never needs them. Here’s a release week.
A week at the startup
Release week
A marketer, a founder, an agent at night, and a release on Tuesday. Pick a day.
Tuesday, 09:00 · Louise Gagnon, Admin
Released on the hour
The new plan and the changelog entry were scheduled for nine. They go live together, and the site rebuilds.
Publishing →Wednesday, 02:15 · Claude, AI agent
An agent drafts the changelog
Claude, working for Marguerite through MCP, drafts the release notes overnight. It can ask for a review, never approve.
Agents →Thursday, 10:20 · Céleste Armand, Reviewer
The founder approves
Céleste reads the words that changed, marked where a machine wrote them, and approves.
Reviews →Friday, 15:45 · Théo Nguyen, Builder
A new field, no migration
Théo adds a field to the plan model for the new token limit. The marketing team fills it in that afternoon.
Modeling →An example week. Every step is something the Studio does today.
History
The Pro plan, four weeks of it
The pricing entry changed every week this month. Drag back through it, and see who changed what.
3e1a9c0Publish plan/pro6 Oct 2026, 10:02- Name
- Pro
- Price line
- $49 a month, 100,000 tokens
Restoring saves it again, as a new version. Nothing is lost.
8b72d41Update plan/pro13 Oct 2026, 16:40- Name
- Pro
- Price line
- $49 a month,
100,000250,000 tokens
Restoring saves it again, as a new version. Nothing is lost.
c05f6e2Update plan/pro20 Oct 2026, 02:15- Name
- Pro
- Price line
- $49 a month, 250,000
tokenstokens, and the new model
Restoring saves it again, as a new version. Nothing is lost.
f9d3b87Publish plan/pro20 Oct 2026, 09:05- Name
- Pro
- Price line
- $49 a month, 250,000
tokens,tokens and the new model
What it takes
The parts that do the work
Offers
Plans and features as entries
A plan, a model, a feature: each an entry the marketing team edits. The site reads them through its channel.
- Fields you choose
- One call for a whole list
Live edits
Edit what’s live, safely
Changes to a live entry wait until someone publishes them.
- The list counts edits not published
- “Publish changes” when ready
Agents
Agents draft, people approve
Claude Code, Codex and any MCP client get every Moteur command as a tool, for the projects you choose.
- What they write stays marked
- Approving is a person’s call
Rebuilds
The site hears about it
Publishing sends a signed webhook. A deploy hook waits half a minute for the rest, then starts one build.
- Signed, and retried
- Vercel, Netlify, Cloudflare Pages
Setup › Webhooks › Rebuild the site
{ "name": "Rebuild the client site", "url": "https://api.netlify.com/build_hooks/…", "kind": "deploy", "batchSeconds": 30 }
Questions agencies ask
A reader asksCan we show prices that change by the minute?
MoteurNot from Moteur. It holds the words and the plans you publish. Live numbers, like a token price, come from your own service at the time the page loads.
A reader asksCan an agent publish?
MoteurNo. An agent can ask for a review, never approve. What it wrote stays marked until a person reads it.
A reader asksWhat if a change goes out wrong?
MoteurEvery save is a commit. Bring last week’s version back as a new save, and publish it.
Build the first one this week.
A free project costs nothing, and its files are yours from the first save.