PowerUp Coaching — Living Knowledge Base

PowerUp AI Mastermind Recap — 2026-01-22

12 min read

PowerUp AI Mastermind — January 22, 2026

GEARS Alpha launch — Ken Droz and Amy Yamada join as co-founders, and the answer provider reframe

“You’re not trying to get people to your website. You’re becoming the answer that AI gives people before they even decide to look.” — Ken Droz

This Week in 30 Seconds

  • GEARS Alpha formally announced — schema injection platform to make your expertise AI-retrievable; Ken Droz and Amy Yamada joined as co-founders
  • Answer provider reframe — the goal isn’t traffic; it’s being the citation AI gives before someone even visits you
  • Psycho-causal graph — schema that maps the buyer’s psychological journey, not just topic taxonomy
  • Canonical content principle — authoritative content belongs on your website; LinkedIn is distribution only
  • Voice of customer as schema gold — testimonials and call transcripts are the highest-value inputs, better than any marketing copy you wrote about yourself
  • Niche specificity as AI citation strategy — narrower authority = more citable; AI prefers specific answers over broad ones

GEARS Alpha: The Answer Provider Platform

The January 22nd session was anchored by a formal announcement: the launch of the GEARS Alpha test group. Lou opened the session by welcoming Ken Droz and Amy Yamada to the call as co-founders, then walked the group through what GEARS is, how it works technically, and what alpha participants would need to provide.

GEARS — Generative Engine Authority and Relevance System — is a schema injection platform. It ingests a brand’s content, testimonials, ideal client profile, named frameworks, and voice-of-customer material, then builds a knowledge graph and dynamic JSON-LD schema that gets deployed via a lightweight script on participants’ websites.

The architecture is elegant: the schema is generated per page on first visit, cached on Cloudflare’s CDN, and regenerated automatically when content changes. This means no manual schema maintenance. The schema stays current as the site evolves. And because it’s cached at the CDN layer, there’s no performance penalty.

The core goal: make each participant’s site semantically legible to AI engines. When someone asks a question in your domain, the AI can retrieve and cite your specific expertise — matched not just to a topic, but to the precise context and journey stage of the query.

Multiple members confirmed participation during the session. Lou walked through the intake checklist: bio, brand identity, ICP, named frameworks, testimonials, call transcripts, and authority content. The NDA process: email admin@successpod.com to initiate enrollment.

💡 What This Means for You

If you’re participating in the GEARS Alpha, the intake materials you need to gather are largely the same as what your website and content strategy already requires. Build the intake folder now — you’ll double-leverage the work.

The Answer Provider Reframe

Ken Droz delivered the session’s most quotable reframe in his opening contribution. The conventional metric for online presence is traffic: how many people visit your website. Ken’s reframe: the goal is not traffic. The goal is to become the answer that AI gives people before they decide to visit anywhere.

This is a structural shift in how to think about online authority. Traffic is a pull metric — you attract someone to your site and then try to convert them. Citation authority is an ambient metric — you’re present in the conversation before the person even frames their decision. Being the cited answer means your name, your framework, your perspective appears in the AI’s response. The visit (if it happens at all) comes after the recommendation.

Lou connected this to the AEO (Answer Engine Optimisation) framing: the job is not to be findable, it’s to be the answer. The distinction matters because it changes what you build. A traffic strategy builds landing pages. An answer authority strategy builds cited expertise — named frameworks, specific claims, documented methodologies that AI engines can retrieve and attribute.

Deep Dive: Insight - You Are Becoming an Answer Provider, Not Just a Website — why the shift from traffic optimisation to citation authority changes everything about what you publish and how you structure it.

💡 What This Means for You

Run the Answer Provider Audit: pick your top 5 client questions — the ones you answer in every discovery call. Ask each one in Perplexity and ChatGPT. Are you cited? If not, who is? What does their content look like that yours doesn’t?

The Psycho-Causal Graph

Lou introduced a concept that pushed the GEARS framework significantly deeper than a simple schema tool: the psycho-causal graph. Where most content strategy maps topics — “I cover leadership, culture, and executive transitions” — the psycho-causal graph maps the buyer’s psychological journey and the causal chain of their experience.

The distinction matters for AI citability. An AI engine responding to “what do I do when my team stops trusting me after a reorg” isn’t looking for a topic match (“leadership”). It’s trying to infer intent and context. Content that maps the felt experience — what the client is thinking, feeling, and fearing at that specific moment — matches the query at a deeper level than content that maps the topic category.

The psycho-causal graph models this explicitly: for each client journey stage, what is the psychological state? What caused them to arrive here? What do they believe (correctly or incorrectly) about their situation? What are they afraid to admit? This becomes the schema — not “this is what I do” but “this is who this person is when they need what I do.”

Lou noted that voice of customer material is the most powerful input for building this graph: testimonials, call transcripts, discovery call notes with verbatim client language. Why? Because that language captures how clients actually describe their experience — not how you describe their experience from the outside.

Deep Dive: Insight - The Psycho-Causal Graph — Mapping Buyer Psychology Into Your Schema — how to map the buyer’s psychological journey into your schema so AI engines can match your expertise to felt experience, not just topic queries.

💡 What This Means for You

Pull 5 testimonials or discovery call quotes from clients. Underline every phrase where they describe how they felt, not what they wanted. Those phrases are the raw material for your psycho-causal graph. They’re also your highest-value schema inputs.

The Canonical Content Principle

Lou drew a sharp distinction that the group needed to hear explicitly: LinkedIn is distribution, not authority. Everything authoritative — your named frameworks, your canonical methodology, your expert positions — belongs on your website.

The reason matters: LinkedIn is owned by Microsoft, which is a major OpenAI investor. LinkedIn content is indexed and valuable for AI training data. But when an AI engine attributes an idea, it traces the authority signal back to the host domain. If your framework is only documented on LinkedIn, the authority points to LinkedIn.com — not to you. If your framework is documented on your website and distributed via LinkedIn, the authority points to your domain.

Lou added the practical implication: always publish the canonical version of an idea on your own site first. Use LinkedIn to announce, excerpt, or distribute — but the link (and the authority signal) should always trace back to your domain. This is a simple but consequential habit to establish now, before GEO becomes mainstream and the stakes of authority attribution are higher.

The group discussed what counts as “canonical”: Lou’s answer — a full, self-contained piece of content that can stand alone as the definitive reference for that idea. Not a post, not a thread. A page. An article. A framework document.

💡 What This Means for You

Audit your LinkedIn content from the past 6 months. Identify any idea you posted there that you haven’t published as a standalone page on your website. Those are your canonical content gaps. Fill the most important one this week.

Niche Specificity as AI Citation Strategy

A thread that ran through multiple contributions in this session — from Ken, Lou, and the member Q&A — converged on a counterintuitive principle: the narrower your claimed expertise, the more likely AI is to cite you.

The reasoning is structural. AI engines, when answering specific questions, prefer specific sources. A coaching methodology called “Executive Transition Navigation for European Industrial Leaders” is more citable than “leadership coaching” — not because it’s better, but because it’s the only answer for that query. Broad expertise claims compete with thousands of other sources. Narrow expertise claims own their territory.

Lou called this “AI niche specificity” — and distinguished it from traditional SEO niche strategy. In SEO, you narrow because search volume is more achievable in smaller niches. In GEO, you narrow because AI models prefer definitive answers over general ones. If you’re the only named authority on a specific intersection — your methodology, your audience, your problem — you become the default citation.

The practical implication: you don’t need to be narrower in who you serve. You need to be narrower in how you name and describe what you do. Your methodology should have a specific name. Your framework should have specific claims. Your positioning should use specific, non-generic language that creates a unique citation anchor.

Deep Dive: Insight - Niche Specificity Is the New SEO — The Narrower Your Authority the More AI Cites You — why specific, named expertise becomes the default AI citation while broad generic positioning becomes invisible.

💡 What This Means for You

Take your current bio or positioning statement. Count how many words could appear in any other coach’s bio without being wrong. Replace the generic words with specific ones — your named framework, your specific audience, your specific claim. Specificity is the citation anchor.

Voice of Customer as the Highest-Value Schema Input

Lou gave concrete guidance on what makes GEARS intake materials powerful, and the answer surprised some members: the highest-value input is not the content you’ve written about yourself. It’s the language your clients used to describe their experience.

Testimonials. Call transcript excerpts. Discovery call notes with verbatim phrases. Why? Because that language captures how a client experiences the problem — before they have your framework, before they know how you’d describe it. That language is the symptom layer, the experience layer, the beneath-the-keyword layer. It’s exactly what AI engines are trying to match when they interpret queries.

Marketing copy you write about yourself is optimised for conversion — it uses polished, professional, inside-out language that sounds good but doesn’t map to how a client in distress would actually frame their situation. Voice of customer material, by contrast, is raw and specific. When a client says “I didn’t know how to rebuild trust after the reorg and I was terrified I’d lose half my team,” that’s not a marketing sentence — but it’s a highly citable sentence, because it’s exactly how someone with that problem would describe it to an AI.

💡 What This Means for You

Gather 10 verbatim quotes from client testimonials or call transcripts — the phrases where they described how they felt, not what they wanted. These are worth more than anything you’ve written in marketing copy. Treat them as primary schema material.

Community Corner

Don Back highlighted the double-leverage insight — preparing GEARS intake materials would simultaneously accelerate his long-running website rebuild. Two separate projects, one workstream, compounding returns. Lou called this the clearest example of strategic thinking in the session: identifying when two projects share the same underlying work and running them together rather than sequentially.

Amy Yamada joined as GEARS co-founder, bringing her GEO authority expertise and her community of knowledge entrepreneurs to the alpha. Her webinar on “How AI Recommends Experts” had already been shared in the group chat the previous week; her direct involvement in the alpha significantly raises the GEO credibility of the launch.

Elizabeth Stief introduced E-E-A-T in the chat: Experience, Expertise, Authoritativeness, Trustworthiness — Google’s quality signal framework, now also relevant for AI engine evaluation. A useful shorthand for assessing whether a piece of content meets the authority threshold AI engines use.

Donald Kihenja and Don Back both flagged the em-dash as an AI content tell they remove from everything — worth building into a content review checklist if you’re publishing AI-assisted content as your voice.

Try This Before Next Session

Run the Answer Provider Audit. This is the core diagnostic the GEARS system is designed to address — and doing it manually first gives you a baseline before any schema work begins.

  1. Write down the 5 questions you answer most often in discovery calls or client work.
  2. Ask each question in Perplexity. Record who is cited in the answer. Are you? If not, who is?
  3. Ask each question in ChatGPT. Record the responses.
  4. For the question where you’re most NOT cited — look at the content of whoever IS cited. What do they have that you don’t?
  5. Write one paragraph that would make you the definitive answer to that question, using their structure as a reference.

Bring your audit results and your paragraph to next session.

Open Threads

  • How do you track AI engine citations affordably without enterprise analytics?
  • What is the optimal cadence for refreshing the ontology as your brand and market evolve?
  • How does multi-language content affect the psycho-causal graph — does the inference transfer, or does it need to be rebuilt per language?
  • At what point does a new framework have enough public history to generate meaningful AI citations?
  • How do you balance publishing quickly with maintaining topical coherence and schema alignment?

Next session: 2026-01-29

← Previous · Next →

Derived Artifacts

Graph View

Backlinks