The plumbing under Stage 3: list, publish, audit and configure schema across hundreds of personal brand sites. The two-credential model, the Elementor trap, and the stale-cache failure that hid 18 live sites.
The Meta Ad Agent — One Skill, Many Clients
A plumber, a roofer, a course creator and a coach get the same agent, parameterized by a client profile. The prime directive, the low-volume design, the money guardrails, and the runnable skill file.
Fleet Uptime Monitor — A Green Result Is Only Trustworthy If the List Was Current
150 sites returned 500 and nothing noticed. Then the monitor built to catch it passed 18/18 while a 111-day-stale roster hid 18 live sites. Both incidents, the probe design, and the runnable skill file.
The Positioning Strategist — Name It Before You Build It
Buy box, passion, and the one sentence only you can sign. Step 1 of the personal-brand method, the swap test that validates it, four worked examples, and the runnable skill file.
The Repurposer — The Daily Channel Watchdog
Someone records on YouTube and their websites never find out. The daily watch loop, the SKIP/LIGHT/MODERATE/STRONG triage, the A− publish bar, and the runnable skill file.
The Publisher — Every Skill Has a Webpage
A skill that exists only as a file is invisible. The rule, the three artifacts, the definitive-article pattern, and the runnable skill file.
The RACI Enforcer — Dennis Is Never R or A
Every project at BlitzMetrics gets a young adult as its owner. Dennis is Consulted or Informed — never Responsible, never Accountable. The skill file that enforces it, plus the repair pass for projects that already drifted.
Riley – Your Daily EOD Check-In Assistant
Most teams waste hours chasing people for End-of-Day reports.We don’t. We built Riley, a custom GPT that handles daily check-ins automatically. Riley checks Basecamp, updates our tracker, and generates a clean summary image. Why We Built Riley Every day, our team members are expected to submit a quick EOD report in Basecamp. Before Riley, someone had to manually: It worked, …
Naming Projects and Threads in Basecamp
One of the easiest ways to create chaos in Basecamp is sloppy naming. If projects, threads, or tasks aren’t named consistently, nobody knows what’s what. That’s why we use a strict naming system for every client and project. It saves us from confusion and makes sure new people can step into any project and instantly understand what they’re looking at. …
Case Study: Subtle Changes, Dramatic Results – A Living Room Reimagined by Showcase Remodels
What happens when clean craftsmanship meets a naturally lit canvas? This recent Showcase Remodels project proves you don’t need to knock down walls or gut everything to create a wow-worthy transformation. Sometimes, it’s the simple shifts, the trim work, the light play, and the precision, that make all the difference. BEFORE: A Room Waiting for its Moment Plastic sheeting covers …
Team Member Do’s and Don’ts
Working with us isn’t complicated, but it does require one thing: professionalism. That means being reliable, responsive, and resourceful without me having to babysit you. If you want to succeed here, here’s exactly what’s expected of you. You should: You should not: This isn’t complicated. Be reliable, be responsive, follow the rules, and use your brain. Do that, and you’ll …
Why You Shouldn’t Use Boosts in Basecamp
Boosts in Basecamp are meant to be quick reactions. But when you boost a comment meant for me, thinking you’re being helpful or showing acknowledgment, you’re actually causing problems. Here’s why this seemingly innocent action breaks our communication system. Boosts Are One-on-One Messages When you boost something, it sends a private alert only to me. No one else on the …