Week 40 — A government site went live, and a funeral order that never arrived
A state agency site went live, every client site now watched every 5 minutes, and the shop bug that quietly refused funeral orders after 4pm.
Someone tried to order funeral flowers from us one night in September. The order never came through. This week I finally found out why.
Every Sunday I post my week here: what got built, what broke, and what you can take from it. Pictures first. Two minutes. Scroll.
Retainer pulse: +2 care plans set up this week, for two finished websites.
Wins
A state agency's new site went live
Live Wednesday. All 24 pages, every old link still works, and the client shared it the next day. Case study →
Every launch, on one honest page
15 sites so far, five of them my own. Each one gets a date and one line about what was hard. See the log →
Try the AI receptionist yourself
Three made-up businesses, a florist, a clinic and a dentist. Chat with them in English or Malay. Try a demo →
Restarted my review tool
Repeat buyers now get asked again, the right way. I also took the "leave a review and get a gift" lines off my own florists' pages. Google doesn't allow it. GoReview →
Built this week — and what it does
Two things went live this week. One is for a client. The other one watches over every client.
1 · A government website that didn’t break a single old link
Tap to open the live site.
Other government sites, news articles and old brochures all link to pages on the old site. Move house carelessly and every one of them lands on "page not found".
For you: redoing your website? Make a list of your old page addresses first, and point every one somewhere. Planning a new site? WhatsApp me →
2 · If a client’s site goes down, I know within 5 minutes
The real status page. Tap to open it.
A free robot visits each site every five minutes. If one doesn't answer, I get told. Nobody has to phone me first.
For you: this costs nothing. If your site makes you money, someone should be watching it. Want yours watched? WhatsApp me →
What broke, and how I fixed it
Where my week went
Still working on
No new client signed. Met two leads, sent three quotes. Still waiting.
My newsletter app. The app still isn't delivering. Support ticket open.
Tools I used this week
ClaudeFound the funeral-order bug, built most of the week
Upptime (GitHub)Free uptime checks and a status page
Publer21 SabahGuide posts scheduled in one go
FeedBossLinkedIn posts, written and scheduled
GoMarblePulls ad and Search Console numbers for reports
ScrepySite health checks for the new audit report
MoreGoodReviewsReview requests behind GoReview
BillplzMalaysian payment links
LetterlyVoice notes turned into tidy text
Nano Banana (Gemini)Images for posts and case studies
My own Claude skills this week
Instructions I wrote once, so Claude does the job my way every time.
Show the full weekEverything else from the week, in six lines.
- For clients: handed over two finished websites, built a big new one for another, and kept an event site updated.
- For new business: met two people who might become clients and sent three plans with prices.
- For Bingo's own website: every past project now shows the real site, and I took down reviews I couldn't prove were real.
- For SabahGuide: the weekly newsletter went out on time, and the KK nightlife list was checked venue by venue.
- For my florists: customers outside our delivery list can now still order, and my wife's shop stopped crashing.
- For the long game: wrote my first newsletter and lined up five YouTube videos.
Other tools this week: WooCommerce, SiteGround, Cloudflare, Google Analytics, Google Search Console, MainWP, Zoho Books, Swipe One.
If you do one thing this week
Ask your web person one question: "If my site went down tonight, who finds out first?"
If the answer is "a customer", that's the gap. Mine used to be that too.
That’s my week. How was yours? Tell me on LinkedIn or in the comments on Substack. Next one lands next Sunday.