OMG!!! This has to be one of the best ways to use Codex + a personal agent!!!! We can use this workflow to redesign local business websites and turn it into a paid service. I honestly think this could be one of the biggest opportunities for everyday people to make money with AI. I could see a company paying $10,000 for what I just built.
I’m so tired of badly designed websites—especially Marco’s Pizza’s ordering site. So I gave Codex + Sai one prompt to give it a complete makeover.
I connected Codex to Sai and asked it to walk through the actual ordering process, investigate what customers were complaining about, and build a clickable English prototype. Separate older complaints from issues still observable today, keep the official branding and pizza photos, and gather plenty of specific negative feedback.
With Codex + Sai, I effectively have two agents working for me. I don’t even have to watch Sai’s screen—it keeps clicking through the task on its own. In my experience, it moves through clicks much faster than Codex’s native computer use. I barely need to touch the mouse.
Codex delegates the task to Sai through MCP. Sai opens a browser on a cloud computer, finds a store, and explores the ordering flow, while Codex researches historical complaints and builds the page and interactions. I can watch Sai through a live view, then open the finished prototype right in my workflow.
Sai also keeps a step-by-step execution log: what it’s trying to do, what the page returns, and which screenshots it captures. Explore the deals, customize a pizza, inspect the cart—each action has a corresponding result.
I don’t have to watch constantly to understand what it did or how it worked around an obstacle. Those records also give me something concrete to show a client when explaining the redesign.
I gave Sai a task to investigate, and it broke that task down into individual actions. I didn’t have to tell it which button to click next. When the ZIP search returned no results, it tried other ZIP codes and cities, then switched to the store directory.
It also spotted a confusing cart state: zero items, yet $4.95 displayed at the top!!!!
When it finished, it sent Codex a report covering the pages it visited, the steps it took, the issues it found, and what it hadn’t tested. Codex could then use those findings to inform the redesign.
While Sai was exploring the live site, Codex was already researching and building the prototype. That division of work is incredibly valuable. It makes a 100× productivity boost feel within reach.
The finished prototype lets you choose a store, change pickup times, customize a pizza, select toppings for each half, edit the cart, and understand why a promo code does or doesn’t apply.
More importantly, the page looks better and the flow makes more sense. With a visible process, I can ask follow-up questions, correct mistakes, and check the result. I also have concrete execution records to explain the changes to a client.
I’m starting to see real potential in offering this as a service: walk through an existing website, find the friction, and turn those findings into a clickable redesign proposal.
Sai gives my Codex workflow an extra pair of hands on a real computer. For me, that’s becoming essential. It makes me want to see how far I could take this—even toward recreating the core experience of almost any SaaS product.
