Athlete Spotlight turns a $30 per month sign-up into a real personal brand website on the athlete’s own domain, built from everything findable about them, delivered with an honest audit, and improved every week after that. This article is the full map of that journey: what the athlete does, what our agents do, and where a human has to step in, from the checkout screen to the change request they send us six months later.
We are writing this down for two reasons. First, so every athlete knows exactly what they are buying and what happens next, with no two-month silence and no surprise reveal. Second, so our own team and our agents follow one standard. Each time we onboard an athlete, that run gets documented as its own case study with real numbers attached (sales, traffic, rankings, and the weekly report). This is the standard those case studies point back to.
The Athlete Spotlight Journey
Checkout to live site to ongoing improvements. Green is live today; amber is being wired in.
What the Athlete Spotlight journey is
The journey is the end-to-end path an athlete travels with us: they find the site, pay through our Keap checkout, buy their own domain, hand us their content and story, and our system builds their WordPress site from that plus everything already published about them online. We deliver the site alongside an audit, then keep improving it through a change-request loop and a weekly AI report.
It is one journey, but it has honest edges. Some steps run today with no human babysitting. Others are drafted and being wired in. We name both, because a standard that pretends everything is automated would be a standard nobody could trust. The gaps below are the build order, not a disclaimer.
The whole thing sits inside the Content Factory methodology (Produce, Process, Post, Promote, with Perform as the measurement loop). The site is the entity home; the weekly report is the Perform stage made systematic for one athlete.
Step 1: Discover and decide
The athlete lands on theathletespotlight.com. They see the roster (real athletes, including the lighthouse example, camhazzard.com), the What’s Included breakdown, and the price: $30 per month, no contract. Many arrive through a figurehead’s referral code, which applies 20% off (for example, code CAM), with a 50/50 revenue split behind the scenes.
The one thing this step still needs is the promo video. A short clip from an athlete explaining what Athlete Spotlight does is committed and not yet recorded. Until it exists, the page leans on the roster and the written What’s Included section to make the case.
State: LIVE (page and roster), with the promo video still to record.
Step 2: Checkout
Checkout runs through Keap today. The athlete clicks Get Started, lands on the Keap checkout for the Athlete Spotlight product ($30 per month), and if they came through a figurehead code, the 20% discount applies. Keap generates the order and the receipt, and the order lands in a queue. Parents are welcome to check out on an athlete’s behalf, which matters because a large share of our audience is 14 to 18 years old and their guardians decide and pay.
Here is the first honest gap. Today, nothing automated fires the moment payment clears. The athlete pays, and the next move is manual. The fix is a post-payment thank-you page or email that routes the athlete straight into intake (step 3). We are reusing an existing Keap campaign pattern for this rather than building a parallel automation, so the work is coordination, not net-new plumbing.
State: LIVE (checkout), WIRING (the automatic hand-off to intake).
Step 3: Intake
Right after checkout we collect what the site is built from: name, sport, position or class year, location (sport plus location feed the network-linking strategy), social handles, five to ten best clips as links, photos, the athlete’s story in their own words, and proof (stats, awards, camps, coaches, press, sponsorships). We also capture the goal persona, because a recruit and a sponsorship-seeker get a different site emphasis. The canonical field set lives in the intake schema the site factory reads from.
The story fields are collected in the athlete’s own first-person voice and rendered close to verbatim. We do not rewrite a 16-year-old’s story into corporate copy. The open question here is the surface: a form, an email reply, or a DM-style capture. Dennis’s guidance is blunt and correct: young adults will not email. A form is the near-term answer; a DM-style surface comes later.
State: WIRING (spec is done: 43 fields, required set, and hand-off format; it drops into the post-payment Keap flow).
Step 4: Domain
The athlete buys their own domain, roughly $12 a year at any registrar. Owning the domain matters: the SEO value and the entity home live on an asset the athlete controls, not on a subdomain we lease to them. We reply with the four nameservers to paste into their registrar’s DNS settings, the same process the team has run hundreds of times.
The draft nameserver email is written (registrar steps, a generic fallback, placeholder nameserver values, and a short how-to video link). Two things stay open: who sends it, and the actual per-athlete nameserver values, which come from provisioning once a hosted zone exists for that athlete.
State: LIVE (the process is proven), WIRING (the email template’s sender and the per-athlete values).
Step 5: Build and audit
This is the machine. The order, the intake, and the domain come together into a provisioning decision, and the site gets built on the company platform (WordPress, provisioned through BlitzAdmin, the company’s site builder). The system builds from the intake AND from everything findable about the athlete online, and it runs an audit at the same time. This is the Dunk Camp pattern: deliver the site and the authority audit together, not weeks apart.
Our tooling plugs in here. The site factory template kit supplies the nine-section homepage and the full page set. Entity schema (a Person record and per-page schema types) tells Google and AI engines who the athlete is. A QA gate blocks the build on real problems (banned words, unresolved template tokens, missing alt text, broken internal links, stale hand-coded blog cards). The Rank Math loop lifts every page toward the green score. The positive-mentions feed supplies the proof section. The site standard behind this step is its own article: how we build an athlete personal brand website documents the nine-section homepage, the page set, the schema, and the QA gate in full.
The open seam is the exact hand-off between BlitzAdmin provisioning and our site-factory content pipeline. Cam now has a BlitzAdmin login and the mapping of that seam is the next investigation.
State: LIVE (the site factory tooling, the audit pattern, the QA gate, the Rank Math loop), WIRING (the BlitzAdmin provisioning hand-off).
Step 6: Delivery
We send a delivery message: congratulations, here is your site, here is your audit, and here is what to know. Crucially, this message sets the expectation that the athlete will want changes, and shows them exactly how to ask. It also carries the fix-at-the-source coaching, because the site reflects the internet: if a bio or a photo is wrong on a source platform, it should be corrected there too, not just on the site.
The delivery email draft is done (site link, audit, fix-at-the-source coaching, the change-request path, and the referral hook). One wording decision stays open: the athlete-level referral split. The 20% off with figurehead codes is confirmed; the percentage a regular athlete earns for a referral is not, so the copy stays vague on that until Cam and Dennis lock it.
State: WIRING (draft done; referral-split wording pending).
Step 7: Changes and ongoing value
This is the retention loop, and it is what makes $30 a month worth paying past month one.
Change requests. The athlete logs into theathletespotlight.com with a username and password and types what they want changed; an agent monitors the queue and executes on their site. This login does not exist yet. Dennis calls it easy to build, and it is a pattern people already understand. The v1 fallback that works today is simple: the athlete replies to the delivery email, and we make the change. The spec for the real login (a WordPress-native login, a request form, a queue, and an agent monitor) is written and estimated at under half a day to build.
The weekly AI report. This one is built. Every week the athlete gets one branded email covering both halves of their presence: what people said about them (new mentions, the best ad-ready quote, a game plan) and how their site is doing (uptime, speed, Core Web Vitals, SSL health, and search basics, with week-over-week movement and up to three concrete actions). Where we have a live connection, it shows real numbers; where we do not, it says “not yet connected” instead of inventing one. The report standard is its own article: the athlete weekly AI report documents its scope.
Positive mentions keep flowing. New praise about the athlete keeps landing on the What People Are Saying page as it is found and approved. This runs on the Positive Mentions System, built by Cam Hazzard and developed with Dennis Yu.
Define the conversion. For an athlete, the sale is fuzzy: a sponsor inquiry, a training-program sale, a recruiting contact. Part of ongoing value is defining that conversion up front so the weekly report measures a real business result, not vanity follower counts.
State: LIVE (weekly report and mentions loop), WIRING (the change-request login; email reply works today).
The gaps list, as a build order
Being honest about the journey means publishing the gaps, in the order we are closing them:
- Post-payment intake routing (Keap thank-you page or email routes to the intake form).
- The nameserver-instructions email template (sender assigned, per-athlete values wired).
- The BlitzAdmin hand-off (how our content pipeline feeds the provisioned WordPress site).
- The customer login and change-request queue on theathletespotlight.com, with an agent monitoring it.
- A DM-style feedback surface (later; email-first v1 is acceptable).
- The athlete conversion definition for the weekly report’s MAA section.
None of these blocks the core promise. An athlete can buy today, get a site, get an audit, get a weekly report, and get changes made by email reply. The gaps are what turn a good manual delivery into a hands-off one.
Who this journey is for
- Young athletes (14 to 18) chasing college offers with little or no online presence. Their parents usually decide and pay, which is why checkout allows a guardian and why the domain is the athlete’s own asset.
- Athletes and athletic creators chasing sponsorships who already have content but no real web home. An Instagram page with a few hundred followers is not authority; an ownable, indexable site is the link you send a sponsor.
The lighthouse example is camhazzard.com, which ranks number one for “Cam Hazzard.” It is the proof that this journey ends somewhere real.
Related frameworks
- How We Launched Athlete Spotlight, the platform-launch story and the repeatable vertical checklist this journey sits inside.
- The Content Factory, the four-stage methodology (with Perform) that the build and the weekly report follow.
- The Positive Mentions System, the engine behind the proof page and the mentions half of the weekly report. Built by Cam Hazzard, developed with Dennis Yu.
- Own Your Name on Google, why the entity home on the athlete’s own domain is the point of the whole exercise.
Get started
The full breakdown of what is included lives on the Athlete Spotlight package page. When you are ready, get started for $30 per month and the journey above begins at step one. Parents are welcome to check out on an athlete’s behalf.
Third-party validation
Athlete Spotlight is built on the same personal-brand methodology that Dennis Yu and BlitzMetrics use for their clients, adapted for the athlete vertical. The lighthouse site, camhazzard.com, ranks number one for its owner’s name and is the primary case study. Dylan Haugen (dylan-haugen.com) is a second live athlete build on the same standard. As each athlete is onboarded, that execution is documented as a meta article with real analytics (traffic, rankings, and the weekly report), so the proof accumulates in public rather than sitting in a testimonial.