How an AI agent builds a website, member portal and admin portal

This is the process behind the Front-to-Back 3-Layer Infrastructure: a website, a member portal and an admin portal built by an AI agent on the business's own accounts. My role is to set up the agent and build the infrastructure. Then it is handed over.

Step 1: The brief

Everything starts with a written brief from the business: goals and offers, brand, copy and images, who buys and who signs in, and the old site if there is one. The agent works from this as its plan. A clear brief is the biggest single factor in a good result, which is why it gets real time and attention.

Step 2: The build loop

The agent works in a loop:

1. Plan the next piece of work from the brief.
2. Code it, writing every file.
3. Test it, including opening its own pages in a browser on phone and desktop sizes.
4. Deploy it to a private preview.

When a check fails, it fixes the problem and runs the checks again, until they all pass. Nobody sees a half-finished result.

Step 3: Every change saved

Each change is saved to the business's own code repository as a version, with a note on what changed and why. If something needs to be undone, any earlier version can be restored. This is also what makes the handover real: the full history goes with the code.

Step 4: A private preview, then your approval

A private preview is built for every version. The business reviews it like a real site, because it is one. Nothing goes live without the business's OK.

What gets built

Three layers on one foundation, all on the business's own hosting account:

• Website for visitors: pages, blog, offers and forms, built on the foundations search engines read.
• Member portal for customers: they sign in with an email link and get what they paid for.
• Admin portal for the team: contacts, sales, buyer progress and email results in one place.

Underneath, one database, file storage, email from the business's own address, payments through its own payment account, and sign-in. A sale on the website opens the member portal and shows in the admin portal at the same moment.

AI on both sides

The admin portal can also offer an MCP connection, the open standard that lets AI assistants use tools. That means the team's own AI assistant can look up contacts, check sales or read email results, with only the access the business allows, and the business can turn it off.

Step 5: The handover

At the end, everything is handed over: the code in the business's own repository, the hosting on its own account, the data in its database, the keys and passwords, and written documentation in plain language. There is no lock-in. Any developer, or an AI agent, can keep building on it.