Run 5 September 2026 through Codex CLI 0.153.4 on the ChatGPT subscription, model gpt-6-astra, reasoning effort high. It was handed the same material Claude read: all the SOPs, the call-funnel video transcript, the ICP brief, the three corpus files from the 220 transcripts, and a plain-text dump of every hub page as it stood that afternoon. About 535,000 tokens, delivered over 3 turns of one session. It was not shown Claude's evaluation, so this is an independent read, not an echo. Its full report is below, unedited. Claude's comparison comes first.
These are its line-level corrections I did not apply, because each one trades punch for caution and that is a decision about voice, not a defect. Its wording and reasoning are in Part 5 of its report below; the numbers refer to that list.
| # | Asset | What it wants | Claude's view |
|---|---|---|---|
| 9 | VSL beat 4 | "6 areas we use to assess" instead of "6 signals that decide" | Keep "decide"; it is the framework's promise. Add the source to the claim register. |
| 10 | VSL beat 3 | Drop "why it's green but you are not getting more leads" | Keep. It is the ICP's own sentence. |
| 11 | VSL beat 4b | Replace the "times 12" rent exercise with "bring your spend" | Keep the exercise, it is the beat. Astra is right that agency fees are not all rent; say "ad spend" only. |
| 12 | a22 hook | A question instead of "95 percent more revenue" | Keep the number. Verify "no extra ad spend" with the Case-Mate page before it runs. |
| 13, 14 | a28 | Drop the blended-CAC arithmetic | Half right. The "drops by a third" line is arithmetic on an assumption; say "if 30 percent arrive free, your blended cost falls" without the number. |
| 16 | a39 | Soften "usually it isn't Google" | Keep. It is the diagnosis the ad exists to make. |
| 19, 20 | a47, a48 | Drop "built to look busy" and "half this industry runs on making you feel slow" | a48's line is the ICP's inferred fear said back; keep. a47's "built to look busy" accuses the incumbent; soften to "busy rather than clear". |
| 21 | a49 | Explain the 60-day notice plainly | Right, if 60 days is real. Harry has said no lock-in; whether there is a notice period at all needs one answer. |
| 23 | W34 | Drop "the shortlist is the sale" | Keep, it is the 6sense finding in one line. Attribute it harder. |
| 25 | Confirmation beat 2 | Soften "the size of the result is set by when you start" | Keep. It is the argument of the video, and it is hedged already by "months not weeks". |
| 28 | WH10 | Toolkit after day two, matching the nurture | Harry's call. Early release is the better show-rate lever; if so, the nurture and the confirmation video change instead. |
What follows is GPT-6 Astra's output verbatim. File references are to the bundle it was given: hub/ is the text dump of the hub pages, sops/ the SOP library, corpus/ the transcript extracts.
The strongest offer is a useful, independent assessment with direct specialist access and findings the buyer can keep. The weakest feature is inconsistency: the assets promise different preparation, deliverables, sales conversations and webinar resource timing. They also turn visibility into revenue and prospect anecdotes into market facts. The raw calls show buyers asking who implements, what it costs in total, and how they justify it internally. Fix payment-based enrollment and remove webinar prices from creative first. Then align the offer, substantiate the claims, and build the implementation and business-case material before increasing production or spend. This is an assessment of the supplied assets, not demonstrated funnel performance. Sources: TASK.md; hub/nurture-webinar.txt; hub/ad-formats.txt; corpus/prospect_speech.txt, Midland City, 2026-07-21, [73:28], and Ultra Nature, 2026-08-20, [65:27].
The independent audit and portable findings are worth preserving. “You leave with all of it in writing whether you hire us or not” makes the next step valuable without requiring an agency change. SOP-02 explicitly recommends “Selling The Next Step vs. The End Result”; SOP-21 says the follow-up should provide insights usable “with or without us.” Bstore asks for a “3-month roadmap” and Macro Mike wants a “full brief,” so a practical written handover fits the evidence. Preserve the offer while making its scope deliverable. Sources: hub/call-vsl.txt, beat 4; sops/SOP-02.txt; sops/SOP-21.txt; corpus/prospect_speech.txt, Bstore, 2026-07-17, [123:30], and Macro Mike, 2026-07-21, [36:29].
Direct specialist access, specialization and knowledge transfer fit the ICP. These are stronger differentiators than another claim about winning AI recommendations. SOP-23 values working alongside an existing team and transferring skills; SOP-35 asks for a solution delivered in the way the buyer wants. Bstore wants “nerds of their craft,” while Mizuno asks for explanations without acronyms. Keep the specialist promise and the option to become more capable internally. Sources: ICP_brief.txt, “How we operate” and “Secret desires”; hub/call-vsl.txt, beats 5 and 6; sops/SOP-23.txt; sops/SOP-35.txt; corpus/prospect_speech.txt, Bstore, 2026-07-08, [43:52], and Mizuno, 2026-08-19, [03:41].
The call funnel’s basic qualification is sensible. An established business with previous SEO activity is consistent with the founder’s target, and the current VSL explicitly excludes starting from zero. SOP-03 requires clarity about “Who It's For and Who It's Not For.” Preserve that distinction, while recognizing that revenue alone does not establish implementation capacity or purchasing authority. Sources: ICP_brief.txt, “Targets”; hub/call-vsl.txt, beats 1 and 8; sops/SOP-03.txt; corpus/prospect_speech.txt, Boaters World, 2026-08-13, [61:15] and [74:43].
Inviting collaboration with the incumbent is a good position. The underlying invitation in “Bring them to the call” lowers switching friction and lets a marketer share the offer without attacking a colleague’s decision. SOP-04 recommends explaining how a specialist complements existing teams. Merry People explicitly praises its incumbent’s autonomy and stakeholder management, while Scentia asks that the discussion not become an exercise in putting down its existing agency. Preserve collaboration; remove the adversarial “they knew or they didn't” framing. Sources: hub/call-vsl.txt, beat 7; hub/ads-call-v2.txt, reason 42; sops/SOP-04.txt, affluent objection handling; corpus/prospect_speech.txt, Merry People, 2026-07-27, [71:18]; corpus/full_quotes.txt, Scentia, “Has or had an SEO agency.”
Building complete ads around distinct buying reasons follows the method. Migration risk, unclear reporting, implementation capacity, incumbent collaboration and internal approval are meaningfully different concerns. SOP-31’s useful instruction is to create “entire unique ads around specific reasons people would buy.” Preserve that creative discipline, without treating its prescribed output volume or the hub’s ad-set structure as proven requirements. Sources: hub/ads-call-v2.txt; hub/ads-webinar-v2.txt; sops/SOP-31.txt; corpus/prospect_speech.txt, Mukhair, 2026-07-13, [30:00], and ATF Services, 2026-07-21, [39:18].
Concrete demonstrations belong in both funnels. A real scorecard, an observed search answer and a worked example can make an abstract service understandable. SOP-26’s demonstration framework says that seeing a process helps establish that it is real; SOP-28 requires answers supported by evidence. ATF explicitly asks to see a good example, and Boaters World runs additional prompts during the conversation. Preserve demonstrations, with their date, scope and limitations visible. Sources: hub/ad-formats.txt; hub/hammer-them.txt; sops/SOP-26.txt, Part 8; sops/SOP-28.txt; corpus/prospect_speech.txt, ATF Services, 2026-07-21, [30:54], and Boaters World, 2026-08-13, [44:00].
The paid event has a coherent practical purpose. Grading a site and leaving with a useful toolkit fits SOP-30’s “complete, valuable fraction” principle. The scheduled sessions, calendar invitations and preparation guidance also follow its attendance recommendations. Preserve the practical learning outcome, the stated dates and the no-replay offer; align exactly what is taught and delivered on each day. Sources: TASK.md; hub/confirmation-vsl.txt; hub/hammer-them-webinar.txt, WH2 and WH8; sops/SOP-30.txt, Sections 4, 9 and 13.
Personal contact and lifecycle segmentation are the right foundations. The call-runner reply, role and migration branches, separate no-show handling and follow-up after attendance reflect SOP-13’s instruction to tailor communication to context and SOP-32’s focus on gathering information to customize the experience. Preserve these structures. The distinction between paid, unpaid, attended, missed and transferred needs to become consistent throughout the workflow specification. Sources: hub/nurture-call.txt; hub/nurture-webinar.txt; sops/SOP-13.txt; sops/SOP-32.txt.
The payment safeguard and US SMS block should remain. The detailed checkout section correctly recognizes that reaching a confirmation page is different from paying, and it explicitly leaves the chase switched off pending verification. TASK.md and SOP-09 require the US SMS restriction. These are useful controls, even though contradictory enrollment instructions elsewhere still need correcting. Sources: TASK.md; hub/nurture-webinar.txt, Segment F; hub/nurture-call.txt, Segment A; sops/SOP-09.txt; sops/SOP-30.txt, registration and payment processing.
Effort labels below are planning judgments, not measured delivery times. Small means primarily copy and production-reference changes. Medium requires coordination across copy, operations and automation. Large requires substantial evidence reconstruction or integration work.
What to change: Rewrite the webinar workflow specification around a verified payment for the relevant cohort. Form submission should not lock a paid seat. A confirmation-page visit should not prove payment. Unknown payment status should trigger reconciliation, not an accusation of abandonment. Check suppression again before each chase, and include refunds, transfers and completed bookings in the lifecycle.
The detailed Segment F approach is stronger than its summary table, but “has the contact ever submitted Checkout completed” is too broad for repeat events: a payment for an earlier cohort does not settle a later checkout. Match the customer and payment to the relevant order and cohort. Retain the requirement to verify successful payment notification and CRM receipt before enabling the chase.
Why: SOP-30 calls for “Purchase tracking and attribution” and a smooth registration process. The hub itself identifies paths where someone pays without loading /confirmed, yet Segment A still enrolls on the main form and the final table still uses seen:confirmed. That directly threatens the trust identified in the ICP.
Effort: Large.
Assets touched: hub/nurture-webinar.txt, hub/confirmation-vsl.txt, and the workflow dependencies they describe.
Completion criterion: A documented test matrix covers paid without redirect, unpaid form submission, delayed or repeated payment notification, repeat buyers, transfers and refunds. No attendee receives an unpaid chase for a settled order.
Sources: sops/SOP-30.txt, Sections 6 and 18; ICP_brief.txt, “Not sure who to trust”; hub/nurture-webinar.txt, Segments A, E, F and “Wiring.”
What to change: Remove price-bearing spoken alternatives, primary text, headlines, reels, statics, carousel cards and reserve hooks. Delete the price-led S7 concept or replace it with a practical-outcome concept. An internal split-test configuration can retain prices; creative should not name them.
Use the same event name, September 23 and 24 dates, 12pm Eastern start, 90 minutes each day and no-replay wording. Replace “two mornings” with “2 live sessions,” and remove relative claims such as “2 days from now” from ads running before the event.
Agree one agenda and resource-release schedule. State the optional strategy-call invitation consistently. Resolve whether a colleague needs a separate ticket before telling every buyer to bring another person.
Why: TASK.md explicitly forbids naming prices in webinar creative. SOP-35 says the ads, funnel and sales conversation must be congruent. The confirmation video, WH10 and nurture currently disagree about when the toolkit is available, and WH1 acknowledges an offer that the confirmation video appears to deny.
Effort: Medium.
Assets touched: hub/ads-webinar-v2.txt, hub/ad-formats.txt, hub/confirmation-vsl.txt, hub/hammer-them-webinar.txt, hub/nurture-webinar.txt.
Completion criterion: Every production-ready event asset uses the same price-neutral promise and matches the delivery schedule.
Sources: TASK.md; sops/SOP-35.txt; sops/SOP-30.txt, expectation setting; the 5 hub files above.
What to change: Establish one specification for the assessment, pre-call work, written handover and optional commercial discussion. Distinguish an initial assessment from a complete migration diagnosis, exhaustive crawl or exact revenue attribution.
Retain a SOURCE scorecard, documented answer observations and prioritized next steps where deliverable. Make the 90-day plan identify dependencies and open questions. Stop promising that a short audit will establish exactly why an AI selected a competitor or exactly what a migration cost without the necessary data.
Choose one preparation instruction. Make relevant reports, search questions and the marketing contact helpful rather than mandatory. Use a short confirmation video as the introduction and make the longer material optional and clearly labeled. Explicitly distinguish application received, application approved and appointment booked.
Why: SOP-02 requires realistic expectations; SOP-28 asks “What's required of me?” The short confirmation says “nothing to prepare,” while the long version assigns preparation and implies a poor call if it is skipped. The raw calls demonstrate that scope and implementation questions are material, not incidental.
Effort: Medium.
Assets touched: hub/call-vsl.txt, both call confirmation files, hub/ads-call-v2.txt, hub/hammer-them.txt, hub/nurture-call.txt.
Completion criterion: A reader can identify the same deliverables, preparation and next step in every asset.
Sources: sops/SOP-02.txt, Expectations; sops/SOP-28.txt; corpus/prospect_speech.txt, The Property Inspectors, 2026-07-15, [90:54] and [92:53]; the call assets above.
What to change: Separate prospect speech from staff speech and unrelated conversation before rebuilding prevalence claims. Define each theme, preserve the supporting passage and identify the unit being counted: utterance, call, company or opportunity. Keep prompted and volunteered remarks separate where determinable. Normalize company aliases without assuming that similarly named records are identical.
Withdraw claims that migration is the highest-converting angle, that AI wins the click but migration wins the deal, and that silence proves concealed dissatisfaction. Keep migration, internal approval and implementation as supported qualitative themes pending validated counts and outcome data.
Why: SOP-35 requires a sound understanding of circumstances. SOP-23 says to operate on data. The supplied “prospect speech” includes a StudioHawk employee introducing himself and explaining his role. The coded quotes include migration-law discussion under website migration and a calendar problem under unexplained traffic loss. The persona acknowledges missing closed-won data but still makes predictive claims.
Effort: Large.
Assets touched: hub/persona.txt, both ad banks, hub/call-vsl.txt, hub/call-confirmation-long.txt, hub/hammer-them.txt.
Completion criterion: Every published prevalence statement has a definition, denominator and traceable supporting records; otherwise it is removed or labeled a hypothesis.
Sources: sops/SOP-35.txt; sops/SOP-23.txt; corpus/prospect_speech.txt, Bstore, 2026-07-08, [06:45] and [07:17]; corpus/full_quotes.txt, Pace Migration and Shopping smart; corpus/full_themes.json; hub/persona.txt.
What to change: Present SOURCE as StudioHawk’s assessment framework, not an exhaustive account of the engines’ decision rules. Separate brand mentions, citations, referral sessions, qualified leads and revenue. Keep each case-study result attached to its original metric, period and intervention.
Remove the inference that a referral-format ratio proves a citation ratio or that an organic revenue result proves AI-generated growth. Replace the blended-CAC example with a model including total acquisition costs and attributable customers. Remove automatic improvement and permanent-position language.
Create a claim register covering the exact wording, original source, supported interpretation, limitations and approval status. The study and case-study pages themselves must be obtained before relying on their detailed findings.
Why: SOP-03 asks for believable specifics; SOP-28 asks for realistic outcomes. Ultra Nature repeatedly rejects impressive metrics without sales. Cocksox explains that a decline in one organic category coincided with growth in another, and Boori says it deliberately removed irrelevant keywords. Those are direct warnings against converting a visibility chart into a revenue diagnosis.
Effort: Medium.
Assets touched: All advertising, VSL and Hammer Them files; both nurture files.
Completion criterion: No asset changes a metric’s meaning or asserts an unsupported cause.
Sources: sops/SOP-03.txt; sops/SOP-28.txt; corpus/prospect_speech.txt, Ultra Nature, 2026-08-20, [65:27], Cocksox, 2026-07-01, [16:22] and [17:49], and Boori, 2026-07-28, [16:42]; hub/ads-call-v2.txt, reasons 22, 28 and 38.
What to change: Add a breakout and matching email explaining what StudioHawk assesses, specifies, writes, implements and verifies; what the client does; and what may require separately scoped development or content support. Show an illustrative responsibility table with dependencies, not invented service inclusions.
Explain the starting retainer alongside scope, notice requirements and likely additional resources. Reconcile “month to month” with the 60-day notice language before filming. Explain how the workload can change after initial remediation without promising a price reduction that has not been agreed.
Why: SOP-02 explicitly requires the client’s effort and milestones to be explained. SOP-32 recommends detailed process information for interested buyers. Midland City asks for the tasks belonging to each team; Ooshman wants an implementation option to avoid coordination; Celebrity Speakers challenges the meaning of month-to-month with 2 months’ notice. These are concrete buying obstacles.
Effort: Medium.
Assets touched: hub/call-vsl.txt, hub/call-confirmation-long.txt, hub/hammer-them.txt, hub/nurture-call.txt; selected call ads.
Completion criterion: A prospective client can explain who does the work, what is included and what remains to be scoped.
Sources: sops/SOP-02.txt; sops/SOP-32.txt; ICP_brief.txt; corpus/prospect_speech.txt, Midland City, [73:28], Ooshman, [85:19], and Celebrity Speakers, [81:31]; hub/ads-call-v2.txt, reason 49.
What to change: Build a concise, forwardable business-case document from the assessment. Include the commercial objective, observed problem, proposed work, owner of each action, total cost categories, dependencies, expected review points and unresolved measurement questions. Separate actual results from forecasts.
Offer an executive summary and optional deeper evidence. Do not require every approver to attend the first call. Ask when the internal decision meeting is and follow up around that date. For B2B and distributor businesses, define success beyond website purchases where appropriate.
Why: SOP-13 requires communication tailored to the recipient’s situation; SOP-21 requires a “Clear Process to Revenue.” ATF asks for selected pages to explain the case to its CEO and COO. Knightcorp requests a comparison document for its decision log. Dermapenworld’s managing director wants consumers directed to partners rather than competing with the distribution network.
Effort: Medium.
Assets touched: hub/nurture-call.txt, hub/hammer-them.txt, hub/call-vsl.txt, hub/ads-call-v2.txt, hub/persona.txt; the webinar’s promised scorecard handover.
Completion criterion: The advocate can present the recommendation without reconstructing a long sales call or defending unsupported projections.
Sources: sops/SOP-13.txt; sops/SOP-21.txt; ICP_brief.txt, Marketing Manager/CMO; corpus/prospect_speech.txt, ATF Services, [39:18] and [75:11], Knightcorp, [65:24], and Dermapenworld, [60:53].
What to change: Make nurture-call.txt the authoritative lifecycle and use the Hammer Them email material as a content library. Add substantive answers about scope, evidence and timing to the booked-call sequence. Avoid adopting either “6 emails a day” or “more than 4 erodes trust” as an established rule for this audience.
Schedule relative to the actual appointment, with late-booking logic and suppression after replies, rescheduling, cancellation or completed calls. For early webinar registrants, bridge the gap with relevant material rather than leaving the initial messages and final reminders disconnected. Distinguish day-1-only, day-2-only, both-day and absent registrants.
Use email for US contacts throughout this launch. Remove unsupported Friday releases, guilt-based unfinished-action language and generic claims that the sender has already found something interesting.
Why: SOP-13 says “send less, but send better,” while the supplied video recommends starting below its maximum cadence. Boaters World describes being flooded after badge scans and deciding to avoid future scans. Olga Berg’s approval delay is caused by the owner’s travel, not insufficient interest.
Effort: Medium.
Assets touched: Both nurture files, both Hammer Them files, both call confirmation files and hub/confirmation-vsl.txt.
Completion criterion: Each contact has one relevant next message, a clear suppression state and no US text dependency.
Sources: sops/SOP-13.txt; jeremy_call_funnel_video_transcript.txt; TASK.md; corpus/prospect_speech.txt, Boaters World, [00:22] and [00:49], and Olga Berg, [62:33].
What to change: Do not present the smaller-budget retargeting version as a workaround for an audience below the method’s stated minimum. SOP-06 also requires at least 100 people. Until an eligible audience exists, deliver the useful content through confirmation pages and email.
Separate unregistered prospects, applicants without bookings, booked prospects, held calls awaiting decisions, webinar registrants and event no-shows. Each needs content appropriate to its state. Remove booking CTAs from booked-prospect education. Create new standalone long-form material if necessary rather than assuming the no-replay event can supply recordings for public distribution.
Treat exposure frequency as a delivery measure, not evidence of comprehension. Judge the program by qualified attendance, buyer feedback and commercial outcomes.
Why: SOP-02 specifies a tight, relevant audience and “no call to actions in content.” The hub combines states and introduces sales CTAs into its purportedly non-CTA library. Its proposed small-audience fallback does not satisfy SOP-06’s own threshold.
Effort: Medium.
Assets touched: hub/hammer-them.txt, hub/hammer-them-webinar.txt, hub/ad-formats.txt, both ad-bank deployment sections.
Completion criterion: Every audience has defined entry and exit conditions, matching creative and a viable distribution channel.
Sources: sops/SOP-02.txt; sops/SOP-06.txt; TASK.md; ICP_brief.txt, trust and time constraints; the hub files above.
What to change: Prioritize distinct, evidenced conditions: implementation capacity, commercial reporting, migration planning, complementary specialist help and AI-answer accuracy. Include a business that is growing and wants to expand, not only a business presumed to be failing.
Use a manageable launch selection rather than treating the full bank as a requirement to activate immediately. SOP-31’s one-reason-per-ad principle does not require one ad set per reason. Preserve creative identifiers when an angle changes; do not replace the old “ripped off” meaning inside the same reporting tag.
Judge the call funnel through qualified bookings, attendance, decisions and collected revenue, with delivery costs. Judge the webinar split through paid registration, attendance by day, qualified calls, customer acquisition and contribution after costs. Do not apply a free-registration benchmark to paid checkout.
Why: SOP-06 starts with finding the bottleneck; SOP-33 requires profitable campaigns and capacity before scaling. The video emphasizes event volume per ad set. Domus describes growth rather than distress, and Boaters World demonstrates that commercial readiness can lag strong interest. No supplied performance export establishes a winning US angle.
Effort: Medium.
Assets touched: Both ad banks, hub/ad-formats.txt, hub/persona.txt, and funnel measurement specifications.
Completion criterion: Results can be compared by original creative, price-test cohort and commercial outcome without conflating engagement with qualification.
Sources: sops/SOP-06.txt; sops/SOP-31.txt; sops/SOP-33.txt; jeremy_call_funnel_video_transcript.txt; corpus/full_quotes.txt, Domus Lighting, “A competitor is overtaking them”; corpus/prospect_speech.txt, Boaters World, [74:43] and [76:08].
hub/ad-formats.txt. Reusable production specifications, real-screen demonstrations and the instruction not to fabricate testimonials are useful. The ranking and budget split are hypotheses, however, and excluding testimonials from all cold advertising conflicts with SOP-26’s case-study framework. The page also breaches TASK.md through numerous event prices, contradicts its own text limits, introduces unsupported “most sites fail four” wording, and treats public publication as sufficient paid-media clearance. The “same exclusion logic” description also confuses prospects who have not booked with Hammer Them’s booked audience. Preserve the format options; rebuild the deployment and claim rules. Sources: sops/SOP-26.txt; sops/SOP-28.txt; TASK.md; corpus/prospect_speech.txt, ATF Services, [30:54].
hub/ads-call-v2.txt. The bank contains useful conditions, especially incumbent collaboration, migration planning and the need for a presentable answer. Its main weaknesses are unsupported diagnoses, repeated recommendation language presented as diversification, revenue claims attributed to AI without supplied evidence, and the claim that a free assessment can establish exact causes and costs. Reason 39 retains “More than half” despite other contradictory prevalence figures. The campaign section overstates what SOP-31 requires and reuses historical tags for different concepts. Prioritize implementation and commercial relevance over additional variants of being named. Sources: sops/SOP-31.txt; sops/SOP-35.txt; corpus/prospect_speech.txt, Midland City, [73:28], and Cocksox, [17:49].
hub/ads-webinar-v2.txt. The agenda-derived approach and newer role-specific ads are sound applications of SOP-30. However, the file still contains explicit price variants and price-bearing primary text, contrary to TASK.md. It promises personal live work more broadly than “categories from the room,” confuses aggregate evidence with a diagnosis of the viewer, and overstates shortlist selection as a completed sale. It also uses free-webinar opt-in benchmarks for a paid event and claims a date change is effectively a creative refresh. Replace unsupported certainty with a concrete learning outcome and keep the manager-specific angle. Sources: TASK.md; sops/SOP-30.txt; sops/SOP-31.txt; corpus/prospect_speech.txt, Knightcorp, [65:24], and Les Mills, [38:15].
hub/call-vsl.txt. The portable assessment, specialist access, prior-SEO qualification and in-house learning option closely match the ICP. The header still describes approximately 3 minutes while the script is labeled 7:06; length itself is within SOP-03’s affluent range, but the extended opening stacks several assumed problems before delivering the offer. The credibility wall is broader than necessary, the SOURCE description becomes a claim about engine causation, and the rent argument wrongly includes all agency spend. It promises revenue measurement while primarily describing visibility outputs. Shorten the opening and use relevant proof, scope clarity and optional chapters. Sources: ICP_brief.txt; sops/SOP-03.txt; jeremy_call_funnel_video_transcript.txt; corpus/prospect_speech.txt, Ultra Nature, [17:27], and Boori, [25:12].
hub/call-confirmation-long.txt. This is the strongest attempt at honest due diligence, with a rescheduling option, an upfront retainer and a written handover. It is weakened by unsupported prevalence counts, a causal compounding story, generalized result timelines and the suggestion that starting earlier determines result size. The Trustpilot statement is based on a described AI answer rather than supplied review evidence. Its preparation burden conflicts with the short video. Keep the due-diligence material as optional modules, replace assumed averages with verified cases, and avoid assigning responsibility for a poor call to the prospect’s preparation. Sources: sops/SOP-28.txt; sops/SOP-02.txt, Expectations; corpus/prospect_speech.txt, Mukhair, [30:00], and Boaters World, [74:43].
hub/call-confirmation-vsl.txt. The brief format, reply request and easy rescheduling are useful applications of SOP-32. The opening cannot truthfully confirm a booking for someone who has only applied, despite the placement note allowing both. “Nothing to prepare” conflicts with other assets, and “not a pitch” creates an unnecessary discrepancy with an optional service discussion. Preserve its concise shape, but make it state-aware, use optional preparation and explain the commercial purpose plainly. Sources: sops/SOP-28.txt; sops/SOP-32.txt; hub/call-confirmation-long.txt; hub/nurture-call.txt; ICP_brief.txt, trust.
hub/confirmation-vsl.txt. Calendar action, computer preparation and a practical learning outcome give the registrant something useful to do. The price-neutral trust beat is unfinished, beginning with an editorial fragment. It contradicts WH1’s offer disclosure, contains unused price and premium variants, and promises a toolkit installation whose requirements are not supplied. Its resource schedule differs from WH10 and the nurture. Keep the calendar and preparation structure, state both dates, disclose the optional next step, and verify toolkit access before promising that a free account supports the full session. Sources: TASK.md; sops/SOP-30.txt, Sections 6, 9 and 13; hub/hammer-them-webinar.txt; hub/nurture-webinar.txt.
hub/hammer-them.txt. Mapping questions, follow-up questions, objections and expectations is faithful to SOP-02. The file’s library counts do not reconcile, many listed scripts are external references rather than included scripts, and several new pieces contain promotional closes despite the no-CTA rule. Its Sylvane explanation contradicts the migration and ranking improvements described elsewhere. The small-audience workaround repeats a threshold problem, while the long-form cost comparison turns Jeremy’s anecdote into an unsupported diagnostic. The 18-email schedule also competes with the separate nurture file. Retain the topic map and make it one content library governed by the actual lifecycle. Sources: sops/SOP-02.txt; sops/SOP-06.txt; hub/ads-call-v2.txt, reason 52; hub/nurture-call.txt.
hub/hammer-them-webinar.txt. The distinction between preregistration, registered, day-2 and no-show needs is useful. WH1’s direct disclosure of the offer is a strong trust choice. However, the file’s no-CTA label is inaccurate, WH10 promises resources in the confirmation email that the nurture does not provide, and WH13 uses “yesterday” and “today” while also being scheduled for the evening of day 1. WH14 promises supervised live fixes, while WH15 flags an unapproved transfer already promised elsewhere. Define each state, correct the timing and avoid guaranteeing a fix from an AI-generated explanation. Sources: sops/SOP-02.txt; sops/SOP-30.txt; hub/nurture-webinar.txt; corpus/prospect_speech.txt, Bstore, 2026-07-17, [48:47].
hub/nurture-call.txt. This file has a useful lifecycle, human task creation and sensible role-based branches. Its booked sequence delivers much less substantive education than the audit promise warrants, while the abandonment copy introduces guilt and unverified Friday scarcity. The personalized note says interesting findings already exist without requiring the sender to name one. The post-call email offers a proposal automatically despite other copy suggesting the buyer must request it first. Reconcile notice terms, preparation, handover attachments and commercial permission, then use useful answers to scope and ROI concerns. Sources: sops/SOP-13.txt; sops/SOP-32.txt; corpus/prospect_speech.txt, Olga Berg, [62:33], and Ultra Nature, 2026-08-20, [66:17].
hub/nurture-webinar.txt. Both-day calendar links, last-mile email alternatives, early value messages and waiting for attendance import are strengths. The principal risk is enrollment on form submission instead of verified payment. The detailed checkout safeguard conflicts with the summary wiring, and its all-time completion test ignores order and cohort context. The resource timing, number of sends and token checklist are also inconsistent with the body. Several messages treat a lead-cost statistic as a customer-cost statistic. Consolidate the state logic, distinguish partial attendance, confirm transfer and refund policy, and rewrite reminders around actual learning rather than escalating fear. Sources: sops/SOP-13.txt; sops/SOP-30.txt; TASK.md; corpus/prospect_speech.txt, Les Mills, [52:24].
hub/persona.txt. The CPO structure, acknowledgment of sample bias and explicit absence of closed-won data are useful. However, the page mixes full-corpus claims with conclusions from earlier small samples, moves between incompatible denominators, and contradicts its own corrections. “Migration wins the deal,” “mostly not the owner” and the prediction language exceed the evidence provided. The raw speech also contains staff passages, so “prospect-only” has not been established. Keep verified qualitative examples and the owner/marketer distinction; remove prevalence and conversion claims until the extraction and outcome join are validated. Sources: sops/SOP-35.txt; sops/SOP-23.txt; corpus/full_quotes.txt; corpus/full_themes.json; corpus/prospect_speech.txt, Bstore, 2026-07-08, [06:45].
The quoted wording below is current hub wording. Prices appear only where identifying existing copy that must be removed; none is proposed for replacement webinar creative.
hub/ad-formats.txt, R4 final card
Current: “$7. September 23 and 24. Live only, no replay.”
Replace: “September 23 and 24. Live only, no replay. Save your seat.”
Why: This preserves the event’s genuine scheduling information while complying with TASK.md’s prohibition on prices in webinar creative.
hub/ad-formats.txt, event date bar
Current: “Sep 23 + 24 · 12:00 PM ET · $7 · live only”
Replace: “Sep 23 + 24 · 12pm ET · 90 minutes daily · no replay”
Why: TASK.md supplies these logistics and explicitly excludes the ticket price from creative.
hub/ads-webinar-v2.txt, W39 reserve hook
Current: “Why am I doing a seven dollar event at all? I'll answer it before you have to ask.”
Replace: “Why are we teaching this live? So you can assess your search strategy and decide what help you need.”
Why: The replacement removes the prohibited price reference and aligns the motive with practical education under SOP-30.
hub/ads-webinar-v2.txt, W43 body
Current: “Two mornings from now you'll know which of the six signals your site is failing and which of them your agency has actually touched.”
Replace: “During the 2 sessions, use the SOURCE scorecard to identify gaps and questions to review with your team or agency.”
Why: A fixed future event is not always 2 mornings away, and the collaborative wording fits SOP-35 and Scentia’s objection to incumbent criticism in corpus/full_quotes.txt.
hub/confirmation-vsl.txt, beat 5
Current: “(same line, ending) ...it's not a stealth sales pitch: you paid to be here, and you're getting the work, not a webinar that turns into an offer at minute forty.”
Replace: “These sessions teach the SOURCE method and how to apply it. At the end of day 2, we'll invite you to a strategy call if you want help implementing it. The toolkit is yours either way.”
Why: This completes the broken script and agrees with WH1’s offer disclosure, as required by SOP-35’s congruence principle.
hub/call-confirmation-vsl.txt, opening
Current: “You're in, and booking that call was the right move.”
Replace: “Your audit call is booked.”
Why: This should run only after an actual booking, with a separate application-received message for applicants, consistent with SOP-28’s instruction to acknowledge the action taken.
hub/call-confirmation-vsl.txt, beat 2
Current: “Camera optional, nothing to prepare.”
Replace: “Camera optional. If handy, bring your latest search report and the business question you want answered.”
Why: This removes the contradiction with the longer confirmation and supports the ICP’s need for clarity without making preparation a barrier.
hub/call-confirmation-vsl.txt, beat 4
Current: “it's a conversation, not a pitch.”
Replace: “We'll review the findings first, then ask whether you'd like to discuss implementation support.”
Why: This states the sales boundary honestly and aligns with the optional proposal in hub/nurture-call.txt and SOP-28.
hub/call-vsl.txt, beat 4
Current: “the 6 signals that decide whether a search engine or an AI recommends you”
Replace: “the 6 areas we use to assess your search foundations and AI visibility”
Why: The supplied bundle establishes SOURCE as an agency framework, not a verified exhaustive decision model, and SOP-03 requires believable claims.
hub/call-vsl.txt, beat 3
Current: “Most SEO is still behind, so none of these show up in the report you're being sent, which is exactly why it's green but you are not getting more leads.”
Replace: “We'll check which of these areas your current work covers, which need attention, and how they relate to your commercial goals.”
Why: This avoids inventing a diagnosis and respects the competent incumbent and internal teams described by Merry People and Boori in corpus/prospect_speech.txt.
hub/call-vsl.txt, beat 4b
Current: “in a calculator, write down your ad spend and agency spend last month and multiply it by 12x.”
Replace: “Bring your recent media spend, agency fees and search results so we can compare the full cost and contribution of each channel.”
Why: Agency work is not uniformly rented traffic, and Cocksox’s channel-mix explanation shows why the business comparison needs more than a single annualized bill.
hub/ads-call-v2.txt, reason 22 opening
Current: “95 percent more revenue. A US retail brand. No extra ad spend.”
Replace: “What changed in Case-Mate's search campaign, and which results were measured?”
Why: The replacement creates a case-study opening without repeating an unverified spend claim or attributing the reported result to AI, consistent with SOP-03.
hub/ads-call-v2.txt, reason 28 headline
Current: “What 30% Organic Does To Your Blended CAC”
Replace: “What Search Contributes To Your Acquisition Costs”
Why: A traffic or customer mix alone cannot establish the advertised cost reduction without the missing cost inputs, which Ultra Nature asks to understand in corpus/prospect_speech.txt.
hub/ads-call-v2.txt, reason 28 body
Current: “Blended CAC drops by roughly a third, and next quarter it drops again, because recommendations compound and auctions don't.”
Replace: “Compare total acquisition costs, including search delivery and development, with the customers attributed to each channel; then assess whether the mix is improving.”
Why: This replaces an unsupported cost and future-performance promise with the commercial measurement the ICP requests.
hub/ads-call-v2.txt, reason 39 primary text
Current: “More than half the businesses we get on a call with have just rebuilt, migrated or re-themed their site.”
Replace: “A recent rebuild or migration is a recurring situation in our sales conversations.”
Why: The hub gives conflicting prevalence figures and the supplied coding has false positives, while genuine migration examples remain in corpus/prospect_speech.txt.
hub/ads-call-v2.txt, reason 39 body
Current: “Everyone told you it was Google. Usually it isn't.”
Replace: “A rebuild is worth investigating alongside other possible causes of the change.”
Why: Dimple Contacts and Cocksox describe alternative explanations, so SOP-35’s circumstance matching does not justify diagnosing the viewer in advance.
hub/ads-call-v2.txt, reason 44 body
Current: “Nobody hires a developer to protect their organic traffic, so nobody does.”
Replace: “A build needs clear ownership of search requirements as well as design and functionality; we'll check what was included.”
Why: corpus/full_quotes.txt includes Cabots reporting that a migration SEO agency was involved, disproving the universal framing.
hub/ads-call-v2.txt, reason 46 demonstration
Current: “Point the address at the closest thing you do still sell, and you keep them.”
Replace: “Check the page's demand, links and relevant alternatives before deciding whether to keep it, redirect it or remove it.”
Why: This removes a guaranteed preservation claim and reflects the different discontinued-product and unique-stock situations described by Bstore and Midland City.
hub/ads-call-v2.txt, reason 47 body
Current: “the reports you get are built to look busy rather than to answer it.”
Replace: “a report can show activity without making the commercial result clear.”
Why: Ultra Nature’s account supports a measurement problem, but neither it nor SOP-35 supports assigning deceptive intent to every incumbent.
hub/ads-call-v2.txt, reason 48 body
Current: “Half this industry runs on making you feel slow.”
Replace: “You should be able to ask for a plain-language explanation of any recommendation.”
Why: This delivers the ICP’s reassurance without inventing industry prevalence or insulting the buyer’s existing relationships.
hub/ads-call-v2.txt, reason 49 terms
Current: “No lock-in contract, ever, month to month with 60 days notice.”
Replace: “The service is month to month with 60 days' notice to end it; we'll explain the notice period before you agree.”
Why: If this is the applicable term, it must be explained plainly because Celebrity Speakers challenges this exact ambiguity in corpus/prospect_speech.txt, [81:31].
hub/ads-webinar-v2.txt, W23 body
Current: “Same position, half the traffic, and nothing in your rankings report changed to warn you.”
Replace: “That comparison is a reason to examine clicks alongside rankings, not a prediction of what happened to your site.”
Why: The cited aggregate comparison does not establish a constant-position causal result for the viewer, and Cocksox’s raw account shows why channel context matters.
hub/ads-webinar-v2.txt, W34 body
Current: “Put those together and the shortlist is the sale. Everything after it is paperwork.”
Replace: “Early consideration matters, and buyers still need to assess fit, evidence, implementation and cost.”
Why: Knightcorp’s decision log and Precise Services’ finance-board comparison directly contradict the dismissal of later evaluation.
hub/ads-webinar-v2.txt, W36 primary text
Current: “Measure after you have built something to measure, not before.”
Replace: “Establish a useful baseline, then choose measurement tools that answer a business question.”
Why: SOP-06’s bottleneck diagnosis and the ICP’s concern about knowing whether work succeeds require a baseline.
hub/call-confirmation-long.txt, beat 2
Current: “Which means the size of the result isn't set by how hard you push once you start. It's set by when you start.”
Replace: “Starting sooner gives the work more time, but results also depend on the diagnosis, implementation and conditions in your market.”
Why: Mukhair’s coordination needs and Bstore’s implementation constraints show that start date is not the sole driver of outcomes.
hub/hammer-them.txt, Sylvane explanation
Current: “Nothing about their rankings.”
Replace: “The case study reports changes in search rankings and AI visibility; those are separate measures.”
Why: hub/ads-call-v2.txt, reason 52, explicitly reports ranking improvements, so the present sentence contradicts the hub’s own case-study account.
hub/hammer-them.txt, platform explanation
Current: “Nothing in the plan requires rebuilding your site.”
Replace: “We'll distinguish fixes your current site supports from changes that need development or a larger rebuild.”
Why: Bstore explicitly discusses a possible rebuild in corpus/prospect_speech.txt, and SOP-02 requires realistic effort expectations.
hub/hammer-them-webinar.txt, WH10
Current: “They are in the confirmation email.”
Replace: “Your resource links will arrive after day 2, as described in the event emails.”
Why: This matches the current delivery promise in hub/nurture-webinar.txt; if the release policy changes, every related asset must change together under SOP-35.
hub/hammer-them-webinar.txt, WH11
Current: “That is your starting position, and on day two you will fix the exact gap it just described to you.”
Replace: “Save the answers as observations; during the sessions, we'll show you how to investigate them and prioritize possible improvements.”
Why: An assistant’s explanation is not supplied evidence of the exact cause, and SOP-30 requires achievable event outcomes.
hub/hammer-them-webinar.txt, WH13
Current: “Yesterday you found out which of the 6 signals your site is failing.”
Replace: “In day 1, you used the SOURCE scorecard to identify areas to investigate.”
Why: This works both after day 1 and before day 2, unlike the current wording scheduled for both windows.
hub/nurture-call.txt, booking-abandon Email 2
Current: “If it mattered enough to apply, it matters enough to pick a time.”
Replace: “If timing or a question is holding this up, reply and the strategist can help.”
Why: SOP-32 recommends useful, consultative contact, and Olga Berg’s approval delay demonstrates a legitimate reason for waiting.
hub/nurture-call.txt, booking-abandon Email 3 subject
Current: “holding your qualified spot until Friday”
Replace: “finding a time for your audit”
Why: The supplied files do not establish a real Friday expiry, while SOP-04 requires genuine scarcity.
hub/nurture-call.txt, personal day-before email
Current: “There's already some cool stuff worth showing you, looking forward to running through it with you on the call.”
Replace: “One thing I'd like to check with you is [specific observation and why it matters to the goal you gave us].”
Why: SOP-32 calls for tailored value, and the placeholder requires the human sender to provide it rather than imply unexplained progress.
hub/nurture-webinar.txt, Email 2 subject
Current: “you're paying 72% more for the same customer”
Replace: “what rising lead costs mean for your plan”
Why: The hub attributes the figure to average cost per lead, not this recipient’s customer-acquisition cost, and the ICP asks for understandable measurement.
hub/nurture-webinar.txt, checkout-abandon Email 1
Current: “If it mattered enough to get that far, it matters enough to finish.”
Replace: “If you had a payment problem or want to check something before registering, reply and we'll help.”
Why: This follows SOP-32’s value-first approach and the file’s own acknowledgment that checkout failures can interrupt a willing buyer.
hub/persona.txt, principal finding
Current: “The finding: AI search wins the click, migration wins the deal.”
Replace: “Working hypothesis: AI-search and migration discussions may differ by sales stage; conversion effects are not established.”
Why: The persona explicitly lacks closed-won data, and the supplied extracts do not link ad exposure, stage progression and purchase.
hub/persona.txt, conditions introduction
Current: “These are the conditions that actually predict a deal in this dataset.”
Replace: “These conditions appear in the supplied conversations and are candidates for testing against deal outcomes.”
Why: SOP-23’s data principle requires outcome evidence before descriptive conditions become predictors.
SOP-02 prescribes “15-20+” exposures and 6 daily emails, while also treating higher frequency as inherently desirable. I would not adopt that as a launch target for this ICP. Boaters World describes being overwhelmed by follow-up and deciding to avoid future badge scans. That is evidence of relationship damage from excessive contact, not simply an unopened message. The supplied video’s recommendation to begin with fewer emails, and SOP-13’s “send less, but send better,” are more suitable starting principles. Test incremental communication against qualified attendance and useful replies rather than filling a quota. Sources: sops/SOP-02.txt; sops/SOP-13.txt; jeremy_call_funnel_video_transcript.txt; corpus/prospect_speech.txt, Boaters World, [00:22] and [00:49].
The video says to deter skeptics, and SOP-35 treats executives as people who prefer vision over technical detail. The raw calls do not support using those traits as qualification shortcuts. Dimple’s founder asks sophisticated questions about implementation and business relevance. Celebrity Speakers challenges a diagram’s validity. Boori identifies recommendations for work it already completed. These are legitimate attempts to assess a supplier. Provide a concise executive view with accessible evidence and detail; do not interpret scrutiny as poverty, low intent or an undesirable mindset. Sources: jeremy_call_funnel_video_transcript.txt; sops/SOP-35.txt; corpus/prospect_speech.txt, Dimple Contacts, [54:33] and [84:42], Celebrity Speakers, [36:09], and Boori, [30:34].
SOP-02 and SOP-11 describe making salespeople into cashiers. Education before the call is valuable, but it should prepare a decision, not presume one. Dermapenworld wants partner referrals rather than maximizing direct online sales. Boori wants specialist link support rather than a generic full-service program. Sigma Planters explicitly rejects a proposal that departed from its original request. A good strategist must investigate scope and sometimes recommend a smaller engagement or no engagement. That remains skilled consultative work after excellent nurture. Sources: sops/SOP-02.txt; sops/SOP-11.txt; corpus/prospect_speech.txt, Dermapenworld, [55:22] and [60:53], and Boori, [76:50]; corpus/full_quotes.txt, Sigma Planters, “Has or had an SEO agency.”
SOP-04 recommends revealing enough method to establish trust but not enough for independent replication. SOP-30 similarly alternates between complete value and reserving implementation details. This ICP explicitly wants to become more capable and may eventually bring the work in-house. The paid event should deliver the promised usable portion completely. StudioHawk can sell diagnosis, judgment, execution capacity and ongoing accountability without creating an artificial knowledge gap. Bstore describes knowing what needs doing but needing guidance on the best way to do it, which is a credible service opportunity after teaching. Sources: sops/SOP-04.txt; sops/SOP-30.txt; ICP_brief.txt, “Secret desires”; corpus/prospect_speech.txt, Bstore, 2026-07-17, [52:39].
SOP-30 makes categorical claims that sub-$50 events are poorly valued, yet includes examples of commercially successful events with much lower ticket prices. The hub makes the opposite shortcut by calling payment itself the qualification. Neither establishes whether this buyer has an appropriate business, authority, implementation resources or a suitable problem. Keep the authorized split test, keep prices out of creative, and evaluate the entire cohort journey. Do not declare a price winner from attendance or ticket revenue alone. Sources: sops/SOP-30.txt, Sections 5 and 12; hub/ads-webinar-v2.txt; TASK.md; corpus/prospect_speech.txt, Boaters World, [61:15] and [74:43].
SOP-33’s emphasis on commercial outcomes over vanity metrics is useful, but “ROAS trumps everything” is insufficient for a service agency. Its own minimum-ROAS example excludes ad spend from the expense total and then calculates the revenue requirement without adding that spend back before applying the desired margin. Its budget categories also sometimes exceed a complete allocation when added together. I would rebuild the financial model from collected revenue, delivery costs, sales costs, acquisition costs and payment timing. A cancelable monthly retainer should not be valued as guaranteed future collections. Sources: sops/SOP-33.txt, “Minimum ROAS Calculations” and budget allocation sections; TASK.md, retainer terms; sops/SOP-30.txt, total-cost components.
SOP-02’s 3-second viewer exclusion can rotate content, but it does not establish that someone understood the answer or completed a long video. Likewise, Jeremy’s low-cost full-view anecdote does not prove that a more expensive StudioHawk video has poor value density. I would retain a browsable library and assess actual consumption, questions and commercial outcomes. I also reject the hub’s interpretation that SOP-06 supplies a below-minimum audience workaround: SOP-06 states the same 100-person prerequisite. Sources: sops/SOP-02.txt; sops/SOP-06.txt; hub/hammer-them.txt; ICP_brief.txt, measurement concerns.
SOP-31’s distinct-message principle is useful. Its output quotas, SOP-35’s prohibition on red and the hub’s rigid format hierarchy should be treated as hypotheses rather than universal causes of performance. The call-funnel video also warns that spreading conversion volume across ad sets can undermine learning. I would preserve coherent ads, use a manageable account structure and test format suitability against actual outcomes. The sources themselves support authentic demonstrations and case-study advertising, so there is no basis here for forbidding all cold testimonials. Sources: sops/SOP-31.txt; sops/SOP-35.txt; sops/SOP-26.txt, Part 8; jeremy_call_funnel_video_transcript.txt; hub/ad-formats.txt.
SOP-32’s “red flags” follow-up and SOP-36’s simulated “Sent from my iPhone” tactic attempt to create pressure or an impression of individual attention. This ICP’s central problem is knowing whom to trust. Use an actual personal reply that contains a specific observation, and ask about the real approval timetable. Bstore needs an internal recommendation and budget approval; Olga Berg’s owner is away. Neither situation is resolved by suggesting that delay reflects poor character or insufficient commitment. Sources: sops/SOP-32.txt; sops/SOP-36.txt; ICP_brief.txt; corpus/prospect_speech.txt, Bstore, 2026-07-17, [126:57] and [127:42], and Olga Berg, [62:33].
The stated no-replay event can remain. I disagree with the suggestion that people who need asynchronous access are less serious or that missing a session means rejecting the offer. The raw calls repeatedly show legitimate schedule conflicts and requests for recordings or notes to inform other decision-makers. Within the existing no-replay constraint, provide the promised written resources and clear transfer terms. Do not quietly distribute event recordings as retargeting content after selling attendance on “no recording.” Sources: TASK.md; sops/SOP-30.txt, attendance and replay options; hub/hammer-them-webinar.txt, WH6; hub/hammer-them.txt, long-form inventory; corpus/prospect_speech.txt, Boori, [01:29], and Midland City, [04:48].
I reject SOP-34’s manufactured reviews, purchased conversations and suppression tactics, as TASK.md expressly requires. Its useful portion is the recognition that prospects research the agency and may encounter inaccurate or outdated information. Apply that through factual corrections, current service information, authentic customer evidence and direct responses to genuine complaints. Diamond Brands’ account of an earlier StudioHawk relationship losing continuity is a reason to demonstrate stronger delivery controls, not merely stronger reputation framing. Sources: TASK.md; sops/SOP-34.txt; sops/SOP-28.txt; corpus/prospect_speech.txt, Diamond Brands, [63:25] and [75:50].
The claimed completeness of the bundle. I evaluated all text supplied in the conversation. However, TASK.md describes 33 SOP documents, while 31 distinct SOP files are supplied. SOP-05, SOP-07, SOP-08 and SOP-10 are not present; SOP-22 is expressly excluded. The video transcript ends mid-sentence and contains an explicit truncation notice. The raw speech consists of timestamped extracts and does not supply the complete underlying 222-call collection, call index or recordings described by the persona. Therefore, I cannot certify a full read of material that the source inventory describes but does not include. Sources: TASK.md; supplied sops/ file headings; jeremy_call_funnel_video_transcript.txt; hub/persona.txt; corpus/prospect_speech.txt.
The prevalence counts and stage comparisons. The files variously describe 220 speech-bearing transcripts, 222 transcript files, 175 companies and 246 calls. The JSON contains company-name lists rather than call-level theme counts, stage assignments or a coding specification. The quoted evidence includes false positives, negations and staff speech. These issues prevent validation of the percentages used in the persona, migration ads and confirmation video. They also prevent concluding that a theme was raised unprompted merely because it appears in a selected passage. Sources: hub/persona.txt; hub/call-confirmation-long.txt; hub/ads-call-v2.txt; corpus/full_themes.json; corpus/full_quotes.txt; corpus/prospect_speech.txt.
Which themes, ads or prospects produce revenue. There is no supplied ad-platform export, booking report, attendance report, closed-won join, collected-revenue report or retention cohort. Claims that migration is the highest-converting angle, that specific concepts are majority hooks, that the US in-market audience is unexhausted, or that a particular amount of spend was wasted cannot be independently established. The persona itself acknowledges missing outcome data. Sources: hub/persona.txt; hub/ads-call-v2.txt; hub/ads-webinar-v2.txt; hub/hammer-them.txt.
The complete production inventory. The ad banks and Hammer Them file refer to earlier film-day pages and scripts that are not included. The text alternates between different counts of reasons, scripted cuts and library pieces. The claimed 30-second and 60-second versions are not both supplied for every entry, and the credibility section announces 6 new pieces but labels C1 through C5. I cannot verify the number of filmed, edited, approved or deployable assets. Sources: hub/ad-formats.txt; hub/ads-call-v2.txt; hub/ads-webinar-v2.txt; hub/hammer-them.txt.
The underlying case-study results and their attribution. The bundle repeats Case-Mate, Clarks, Tapt, First Fence of Georgia, Sylvane and The Motor Enclave results, but does not include the original case-study pages, measurement definitions or account evidence. Repetition across hub pages is not independent verification. In particular, I cannot establish Case-Mate’s “no extra ad spend,” attribution of its reported revenue growth to AI recommendations, the baseline behind Sylvane’s percentage changes, or whether the cited framework was used in each named historical campaign. Sources: hub/call-vsl.txt; hub/ads-call-v2.txt; hub/hammer-them.txt; hub/ad-formats.txt.
The Format Leverage study. The study is described but not supplied. Its sampling frame, page classification, normalization, channel definitions and limitations are unavailable. The hub moves between AI referral traffic and what AI “actually cites,” and between a format’s share of sampled pages and its “share of the internet.” I cannot verify those transitions, the “largest published study” claim, or the claim that tools beat blogs by the stated multiple. Sources: hub/ads-call-v2.txt, reason 38; hub/ad-formats.txt, R3, S9 and C2; hub/hammer-them.txt, B4.
The external research interpretations. Original reports from WordStream/LocaliQ, Seer Interactive, Pew, Similarweb, seoClarity, G2 and 6sense are not provided. The hub’s source labels do not establish whether quoted periods, populations, metrics and comparisons match the original findings. I cannot verify the combined “same searches” claim, the shift from cost per lead to cost per customer, the assertion that a shortlist is now written by a machine, or the assumption that aggregate AI-tool visits represent relevant commercial search demand. Sources: hub/ads-call-v2.txt; hub/ads-webinar-v2.txt; hub/call-vsl.txt; hub/nurture-webinar.txt.
The AI-selection and timing claims. No supplied experimental evidence establishes that every answer contains a fixed number of businesses, that SOURCE’s 6 areas determine selection, that the agency can identify the exact reason a model names a competitor, or that being named creates a reliably self-reinforcing position. The supplied material also does not establish uniform months-to-results, predictable erosion after stopping, guaranteed preservation through redirects or an automatic reduction in acquisition cost. Sources: hub/call-vsl.txt; hub/call-confirmation-long.txt; both ad banks; hub/hammer-them.txt.
Samsung’s complete acquisition journey and other authority claims. The hub repeatedly says Samsung arrived through ChatGPT without advertising, referrals or prior familiarity, but no corresponding original record is supplied. The prospect extracts do support other businesses describing AI-assisted discovery, sometimes alongside search, content and referrals. Those examples do not establish Samsung’s history or an exclusive acquisition channel. The founding priority, award counts, individual awards, rating-work history, foreword history and current named-client relationships likewise lack primary supporting material in this bundle. Sources: hub/call-vsl.txt; hub/ads-call-v2.txt; hub/hammer-them.txt; corpus/prospect_speech.txt, Bstore, 2026-07-08, [08:54]; corpus/full_quotes.txt, Knightcorp and Cosh Living.
Testimonial and media-use permissions. The hub identifies Ryan Dobrin and Ashlie McKinnon quotes and calls them cleared because they were published. The bundle does not contain the relevant permissions or their scope. Nor does it establish permission to use client dashboards, prospect screenshots, third-party podcast footage or event recordings in paid media. Publicly described results should not be treated as proof that every proposed presentation is approved. Sources: hub/ad-formats.txt, T1 and verification flags; hub/ads-call-v2.txt, reason 52; hub/hammer-them.txt, credibility inserts and long-form inventory.
The Trustpilot statement and typical results. The long confirmation describes an AI answer reporting a small Trustpilot profile and a negative review. The actual profile, review and response are not supplied. Its proposed typical month-by-month outcome is explicitly generalized from selected case studies and marked for confirmation. I cannot endorse either as a verified spoken statement. Sources: hub/call-confirmation-long.txt, beat 7b; hub/hammer-them.txt, “How long does it take, honestly.”
Delivery capacity and commercial terms. No operational evidence confirms that every eligible applicant receives the promised crawl, extensive query review, scored assessment and custom plan before a 30-minute call. The bundle also lacks an authoritative current US scope and agreement confirming implementation inclusions, notice terms, capacity limits, quote-validity periods and the claimed Friday releases. The retainer starts from $2,000 according to TASK.md; that alone does not define what the starting scope includes. Sources: TASK.md; hub/call-vsl.txt; hub/ads-call-v2.txt, reason 49; hub/nurture-call.txt; hub/hammer-them.txt.
Event materials, access and future cohorts. The complete deck, SOURCE whitepaper, toolkit, setup guide and skills are not supplied. I cannot verify that a free Claude account supports the promised installation, that every attendee can receive supervised work on their own site, that resources are available at registration, or that access lasts indefinitely. The following cohort’s dates, transfer entitlement, refund policy and colleague admission terms are also not established consistently. Sources: hub/confirmation-vsl.txt; hub/hammer-them-webinar.txt; hub/nurture-webinar.txt; hub/call-vsl.txt, whitepaper production note.
The actual live funnel and automation state. The text describes deployed forms, a payment webhook, CRM events and draft workflows, but no code, delivery logs or completed purchase test is supplied. The signed payment notification is explicitly not yet proven in the hub. I therefore cannot confirm functioning payment suppression, local-time sending, attendance segmentation, cross-funnel exits or event tracking. For US SMS, the launch assumption remains the explicit block in TASK.md; none of the proposed nurture should depend on sending US texts. Sources: TASK.md; hub/nurture-webinar.txt, Segment F; hub/nurture-call.txt, “Wiring”; hub/hammer-them.txt, verification flags.