by /
Per the BlitzMetrics definitive article guide, this is a meta-article: a case study that branches off a single definitive article, documenting real applications of it rather than re-teaching the method. The parent is Dennis Yu’s definitive article, Building an Evergreen Personal Brand with AI Systems and Human Insight, that piece explains the why, the systems-over-custom approach, and the MAA and LDT frameworks. This piece is the branch: it documents the work across three real builds, what we did, what differed by archetype, and what it cost.
We took three social-media rockstars, people with real audiences but no entity home Google could resolve and turned that raw reach into durable authority by building each a personal brand site wired into its own online entity graph. Three structurally different starting points: an operator who lives on camera, an executive with an existing media surface, and a practitioner inside our own ecosystem who built his with AI using the very systems we teach. Same methodology, three different applications. This documents how the builds actually went.
On this page
Task Summary
Assignment: Build personal brand entity homes for three social-media rockstars using AI agents, following the framework in the Evergreen Personal Brand definitive article, and capture what differed across the archetypes so the next builds go faster.
Source material: Each client’s existing footprint (YouTube, podcasts, news, social), the BlitzMetrics site generator, and Dennis Yu’s Own Your Name on Google as the methodology reference.
Goal: A controlled entity home for each client that Google can resolve as a distinct entity, without overstating progress that hasn’t landed yet.
The three archetypes:
- Nick Dossa (Vegas Auto Gallery) — operator without an entity home. On camera constantly, but his only public bio lived on a company About page.
- Jeremy Barker (Murphy Door CEO, host of 90 Proof Wisdom) — executive with an existing media surface that didn’t resolve to a personal entity.
- Dylan Haugen (pro dunker, host of the Dunk Talk podcast, co-founder of Local Service Spotlight) — practitioner inside our own ecosystem. 100M+ social views but no entity home. Inspired by what we build for clients, he built his own with AI using the systems we teach in the Local Service Spotlight ecosystem, proof that we don’t just do this for clients, we practice what we preach, exactly the practitioner ethos Dennis Yu champions in his 9 Triangles ideology.
Step-by-step: how we built each personal brand site
We followed the build taught in the definitive article — foundation, fact-first homepage, entity graph, then Knowledge Panel. The method itself lives there; here’s what the work looked like, and where the three archetypes forced different choices.
Step 1 — Stood up the foundation
We provisioned the technical foundation each site needs before anything else. The full pillar list lives in the Digital Plumbing definitive article.
- Nick: clean install. New standalone WordPress instance under his domain via the site generator, separate credentials, self-contained.
- Jeremy: layered. We kept his existing 90 Proof Wisdom media brand intact and built the personal entity layer as a sibling, not a replacement.
- Dylan: self-serve. He stood up his own site with AI agents following our playbook, a standalone instance in his name that we then reviewed and wired into the entity graph, the practitioner path rather than a done-for-you build.
Step 2 — Populated the homepages with verifiable facts
We inventoried each client’s real footprint, YouTube videos, podcast appearances, news mentions, books and built fact-first homepages. Nothing fabricated; every claim points to a verifiable source. This is the content stage. Here’s the standard we held each homepage to, in Dennis’s words:
“Most people’s personal brand sites read like advertisements. ‘So-and-so is an incredible entrepreneur who…’ That’s an opinion. Google doesn’t care about opinions. Google cares about facts that can be verified across multiple sources.”
— Dennis Yu, Own Your Name on Google
What differed: Nick had abundant video to mine but no written facts anywhere; Jeremy already had a media catalog we could cite directly; Dylan had a massive but scattered footprint, 100M+ views, 70+ podcast episodes, six dunk-contest wins — that he himself inventoried and structured into fact-first copy with AI. So the slow step for Nick was building facts from scratch, for Jeremy it was selecting from what existed, and for Dylan it was teaching the agent which of his many credentials Google could verify.
Step 3 — Built the entity graph
We wired each entity into the knowledge graph, entity links out to every company, partner, and podcast, plus a Wikidata entity with sameAs pointing back to the new site.
This is where the archetypes diverged most, and where honest status matters:
- Jeremy reached a live Wikidata entity — Q136632241 — and Murphy Door has its own live entity, Q138296559. Those are claimed and verifiable today.
- Nick is earlier in the build — his Wikidata entity isn’t live yet. We’re not claiming a knowledge panel or entity that doesn’t exist. That work is in progress.
- Dylan reached a live entity too — his site links out to the Dunk Talk podcast, the Minnesota Dunk Squad, and Local Service Spotlight, with a Wikidata entity and sameAs wiring pointing back. Because he executed the build himself on our system, he’s the cleanest proof the method transfers to a practitioner, not just a done-for-you client.
Step 4 — Set up for the Knowledge Panel
With an entity home and a live Wikidata entity, a Knowledge Panel becomes claimable. Dylan is living proof: he now has his own Google Knowledge Panel — a verified entity Google surfaces when you search his name — earned through this exact process, built by him on our system. Jeremy is close behind because his entity is live; for Nick this step is queued behind Step 3, and we don’t claim panels that aren’t there. If you want the same outcome Dylan got, that’s what our Knowledge Panel Package delivers the entity home, the graph wiring, and the panel claim, done the way we just described.
Critical decisions that differed by archetype
The reusable lesson :
- Operator (Nick): the bottleneck is written facts. He has endless video but nothing Google can read as factual text. Decision: transcribe and structure his on-camera claims into verifiable homepage facts before touching the entity graph.
- Executive-with-media (Jeremy): the risk is cannibalizing the existing brand. 90 Proof Wisdom already ranks. Decision: build the personal entity as a sibling that links to the media brand, never a replacement — which is exactly why his Wikidata entity landed first (the media surface gave Google corroborating signals).
- Practitioner (Dylan): the question is whether the system transfers to someone learning it, not just an agency executing it. Decision: hand him the playbook and let him build it himself with AI, then review and wire the entity graph — the Learn-Do-Teach loop in action, and the clearest evidence that the method, not the operator, is what produces the result. It’s the practitioner discipline Dennis Yu builds into the 9 Triangles: you earn authority by doing the work you teach.
Effort and cost
Estimates, agent time vs. the human-only alternative at $35/hr. Figures are illustrative of the pattern, not billed exact.
| Stage | Agent time | Human-only time | Notes |
|---|---|---|---|
| Foundation (per site) | ~10 min | 2–3 hrs | site generator does the heavy lift |
| Homepage facts (per site) | ~30 min | 3–5 hrs | inventory + structuring is the slow part for a human |
| Entity graph (per site) | ~40 min | 2–4 hrs | Wikidata + sameAs wiring |
| Per-site subtotal | ~80 min | 7–12 hrs | |
| Three sites | ~4 hrs | 21–36 hrs | archetype differences add judgment, not time |
The agent doesn’t make the archetype decisions faster, those are human judgment calls. It makes the execution of each decision roughly an order of magnitude faster.
What the agent handled vs. what needed a human
Agent handled: site provisioning, footprint inventory, homepage fact structuring, Wikidata entity drafting, sameAs wiring, internal link mapping.
Required a human: the archetype call itself (is this an operator, an executive-with-media, or a company-founder, and what does that imply?), deciding which facts belong on the person vs. the company, and confirming that we never claim a panel or entity that isn’t actually live.
Compliance scorecard
| Guideline | Status | Notes |
|---|---|---|
| Documents specific work (meta-article, not framework re-explanation) | PASS | Branches off the Evergreen Personal Brand definitive article; documents work rather than re-teaching it |
| Title documents work, not “applies a framework” | PASS | “How We Transformed 3 Rockstars…” |
| Links each definitive concept to its canonical article | PASS | evergreen-personal-brand (parent), digital-plumbing, content-factory, entity-linking, knowledge-panel, 9-triangles, knowledge-panel-package |
| Verbatim quote attributed | PASS | One Dennis quote, sourced |
| No fabricated proof | PASS | Live entities for Jeremy, Murphy Door, and Dylan (who has a live Google Knowledge Panel) cited; Nick honestly marked in-progress |
| Agent-vs-human cost comparison | PASS | Table above, marked illustrative |
| No AI fluff phrases | PASS | |
| Honest about what isn’t done yet | PASS | Nick’s entity not yet live, stated plainly |
SEO metadata
- Primary keyword: personal brand website build
- Meta description: How we transformed three social-media rockstars into authority powerhouses — building each a personal brand site wired into its entity graph, including the build a practitioner did himself on our system to earn a live Google Knowledge Panel.
- Suggested slug: /three-rockstars-personal-brand-builds/
- Categories: AI Tools, Content Factory
- Tags: Personal Brand, AI Agents, Meta-Article, Entity Graph, Knowledge Panel, Wikidata
Field examples from three builds, two BlitzMetrics client engagements (Nick, Jeremy) and one practitioner who built his own on our system (Dylan). Parent definitive article: Building an Evergreen Personal Brand with AI Systems and Human Insight. Documentation standard: the Meta-Article Prompt.