Live Editor · Concept
Small Fixes vs. Big Rebuilds: Where the Line Is
Some changes are a two-minute tweak. Some only look like one. Knowing the difference saves you from both waiting weeks for a trivial edit and rushing a real project through the wrong door.
The Small-Fix Side
Self-contained, low-risk, reversible
A genuine small fix has three traits: it's self-contained (it touches one clear thing), it's low-risk (getting it wrong doesn't cascade into everything else), and it's easy to reverse if you change your mind. Fixing a typo, swapping an image, nudging a button's size or position, updating a phone number — these are the everyday asks that otherwise sit in a queue for no good reason. This is exactly the territory a conversational live editor is meant for: describe it, see it, move on.
The Real-Project Side
When it touches structure, flow, or "the whole thing"
Bigger work has a different shape. It touches how pages relate to each other, changes a checkout or a core user flow, affects many pages at once, or is hard to undo cleanly. "Redo the navigation," "rebuild the booking process," "redesign the site" — these aren't quick fixes wearing a bigger label; they're projects that deserve to be scoped, planned, and tested properly. Trying to shortcut them through a quick-edit door is how small mistakes become expensive ones.
There's a common trap here worth naming: "the site feels dated" is not a small fix or a well-scoped project — it's a taste opinion, and taste opinions don't reliably move a number. A real rebuild earns its cost when it has a specific hypothesis attached, not just a wish for a fresh coat of paint.
Finding the Line
Two questions that usually settle it
When you're unsure which side a change sits on, two questions do most of the sorting. What else could this touch? If the honest answer is "just this one thing," it's probably a small fix; if it's "a few things I'm not totally sure about," treat it as bigger. And how hard is it to undo? Easily reversible leans small; hard-to-unwind leans project. The value of a good live editor is partly that it's honest about which side your request landed on — flagging when a "quick" ask is actually reaching into project territory, rather than quietly making the change and letting you find out later.
What Audry Does Here
The "just move the button" that wasn't
An owner asks to "just move the checkout button up a bit" — sounds like a thirty-second tweak. But on this site that button's position is tied into the whole mobile checkout flow, so moving it risks quietly breaking the step that actually makes money. A tool that treated every request as small would make the change and let the owner discover the damage in next week's sales.
The honest move is to flag it: "this one touches your checkout — let's try it in a preview first, or scope it properly." Small asks get made on the spot; the ones that only look small get caught before they cause harm. That judgment — knowing which door a change belongs in — is the point. For the honest expectations behind the concept, see What a Conversational Site Editor Can (and Can't) Do.
Keep Reading
Next in this guide
Set honest expectations for the concept in What a Conversational Site Editor Can (and Can't) Do. Or return to the full Live Editor guide.
Be first to try it when it's real
The live editor is a concept Audry is building toward, not a shipped feature. Join the waitlist and you'll hear the day there's genuinely something to try.
No spam — one email, the day there's something real to try.