The situation
Last Admin is an IT company. Its own website ran on an aging WordPress installation — and when the server moved to a newer PHP version, the WordPress underneath it couldn't cope. Pages that depended on WordPress started failing outright. The site an IT company sends its clients to was, itself, broken technology.
The traditional route is a freelancer or an agency: get quotes, wait, hand over credentials, hope. Instead, the work was done in-house by an AI operator working with the owner — the same pattern this whole channel documents. Five chapters. Here's what actually happened, including the parts that went wrong.
The five chapters
- Chapter 1 — The day the website died. The call: don't patch the WordPress — retire it. The site was rebuilt as clean static pages: no database, no plugins, nothing left to break. Then the old WordPress was cremated — leftover folders, configuration files, demo junk — and both this site and oahucoins.com were verified healthy afterward. Watch chapter 1 →
- Chapter 2 — The database nobody dared touch. Two databases with near-identical names: one runs the live coin store, one belonged to the dead WordPress. Touch the wrong one and a working business breaks. The operator worked a live support chat with the hosting company's (human) agent to confirm which was which, then completed an approved password rotation — with the live store's database deliberately left untouched. Watch chapter 2 →
- Chapter 3 — The upload that took the site down. Deploying this very section of the site, the new files landed with locked-down permissions — and for a stretch, the homepage itself threw a 403 error. The fix was unglamorous: permissions corrected file by file and folder by folder until every page verified live. The lesson got written into the deployment checklist permanently.
- Chapter 4 — Google couldn't see the site. A live site isn't a findable site. The rescue finished with structured data describing the business properly, a corrected robots file, a clean three-page sitemap, and Search Console verification — Google discovered the pages, including this section.
- Chapter 5 — Then we gave it a voice. The rebuilt site grew this AI Operator wing, and the channel's first video was scripted, voiced, edited, captioned, and published by the operator end to end. The funnel — video to write-up to a real conversation — went live.
What still needs a human. This is the part hype leaves out. The owner still approves what goes live, still performs the uploads, still does the two-factor and identity-verification steps — some of them can only ever be his. A few unrelated work items still go to a freelancer, and an outside developer still owns his section of another site. The operator didn't replace the humans. It replaced the waiting, the quoting, and the hand-offs.
Where it stands
The site you're reading is the result: static, fast, verified in search, and carrying a growing library of real systems work. Season 1 is being published chapter by chapter on the AI Operator channel; each chapter's video links back here, and this page links to each chapter.