It starts as a plain-language ask
There's no change-request form and no ticket to fill out. It starts with describing what you want in ordinary language, the same way you'd explain it to a person — new wording for a section, a page added to the blog, a line that reads wrong and needs fixing.
The co-founder lines up the build
From there, the co-founder takes that description and lines up the actual work: the copy, the layout, the new page, whatever the change calls for. You don't have to translate the request into anything more technical than how you'd say it out loud.
You see the real result before anyone else does
Once the build is ready, you see the actual result — not a mockup or a description of what it will look like, the real page as it will appear to a visitor. That's the point where you get to look it over.
Nothing goes live without that review
The rule holds every time: nothing publishes to visitors until you've seen it and said yes. If something's off, it gets fixed before it ever reaches the public site, not after.
What this has looked like in practice
This is the same loop behind other changes on this site — a homepage that got its wording corrected more than once, blog posts added one at a time, a phrase fixed after a second look. Each one started the same way: described in plain language first, built next, reviewed and approved before it went out.
Why it works this way
Handing off the actual building is only worth it if you still get the final say. That's the whole arrangement — you describe the change, the co-founder does the work, and you're the one who decides when it's ready for visitors to see.