From John

Why we built My Site Buddy

A 2 minute, 46 second story about the work that was getting buried and what changed when Web Moves built My Site Buddy.

Read the full story and transcript
Back to the journal
Agency Operations 5 min read

Great Ideas. Done Right.

How My Site Buddy turns a website request into prepared work, a visible preview, and a reviewable release decision.

Written by John Wieber
Illustration of a website change moving through review to approval

My Site Buddy helps businesses and agencies turn a website request into prepared work, a visible preview, and a release decision that stays with the people responsible for the website.

A good website idea is easy to say.

“Can we make this page clearer?” “Can we add a form?” “Can we fix the tracking?” “Can we build a better landing page for this campaign?”

The hard part comes after the idea. Someone needs to understand the website, the tools connected to it, the information behind the request, and what has already been tried. Someone needs to prepare the work. Someone needs to check it. And someone needs to decide whether it should go live.

That is why I built My Site Buddy.

It is not another place to ask an AI a question. It is a practical way to take a website request from the first conversation to a change that the right person can review.

A request needs more than an answer

An answer can be useful. A draft can be useful. A suggestion can be useful. But none of those things is the finished job when the work affects a real website, a live form, an ad account, or customer information.

The request needs to stay connected to the website and the people responsible for it. The work needs a clear scope. The result needs to be visible before anything changes on the live site.

My Site Buddy keeps the request, the useful information, the work, the preview, and the approval together. You can explain what you need in normal words. The work can be prepared using the website, connected tools, and project information. Then you can see the result, ask for changes, and decide whether it should go live.

Illustration of connected project notes, website pages, and source material
The request and the useful context stay with the work.

The work happens in the real client environment

Website work is rarely just writing. A useful request might lead to a clearer service page, a landing page, a form connected to a CRM, a tracking repair, a product-feed fix, a campaign change, a report, or a custom feature.

Those jobs need more than a chat history. They may need access to the website code, analytics, ads, forms, files, data, and the rules that apply to that client.

Each client has their own project. Their work stays separate from another client’s work. The team can use the tools that fit the job without rebuilding the story from separate chats, folders, and accounts every time. See how My Site Buddy works for agency teams.

That makes it easier to do useful work. It also makes it easier to understand what happened later.

Illustration of connected analytics, search, content, advertising, and code signals
Connected tools can inform the next useful change.

Review is part of delivery

A preview is not the same as a release.

My Site Buddy is designed to make that distinction clear. Work can be prepared in development, checked, and shown to the people responsible for the result. Important changes can wait for review and approval before they reach production.

The project record can show the request, the work, the preview, the checks, and the final decision. That is not extra ceremony. It is how an agency or business keeps control when a website is important to the business.

The goal is not to remove people from the process. The goal is to give good people more help while keeping the final decision where it belongs.

Illustration of a website page moving through review to approval
Important website changes can be reviewed before release.

Security means clear boundaries

Clients should not have to hand over control just to get help with their website.

My Site Buddy is built around clear client projects, approved connections, and a release process that can be reviewed. The website, accounts, and final decision remain with the client and the people responsible for the work.

Development and production are separate. Changes are kept in Git. The result can be reviewed before release. That means a useful idea can move forward without becoming an unexplained change on a live site.

Show the work

The best proof is not a promise on a marketing page. It is a project record.

My Site Buddy includes documented project replays that show the request, the work that was done, and the review before anything went live. Our case studies show the same discipline across real website projects.

We built My Site Buddy for businesses and agencies that want to move faster without losing the details, the review, or the responsibility. See the Business view, or tell us what needs to change.

Questions people ask

Is My Site Buddy a chatbot?

No. Conversation is the starting point, but the purpose is to prepare, review, and release real website work with the right client context and a clear record.

Can My Site Buddy change a live website without approval?

Important changes can be prepared and reviewed before they reach production. The person responsible for the website keeps the release decision.

Can an agency use its existing website and marketing tools?

Yes. A client project can bring together the website, connected tools, data, and project information needed for the work.

How can I see what My Site Buddy does?

Start with the documented project replays, then use the contact page to talk about a website or client project.

Great ideas deserve more than a quick answer. They deserve to be done right.

Written by

John Wieber

Founder & Managing Partner, Web Moves

View author profile →