From the Campfire — Kalyn Wright
“The work should leave the business stronger than we found it.”
What are we actually building for our clients? Last month we talked about what we are building: cleaner entities, stronger systems, better diagnostics, and tools that help agencies know what to do next. This month I want to answer the more important question: why does any of that matter long term? A client should not be paying us month after month just to keep a fragile collection of tactics alive. The work should leave the business stronger than we found it. Their website should be clearer. Their business information should agree across the web. Their supporting assets should be organized and owned. Their claims should be easier to verify. And the systems we build should continue creating value after the original task is complete.
That is the shift we keep coming back to inside Team Human. We are not trying to make AI sound certain about a business. We want AI systems to have better reasons to be certain. Make the truth easy to verify. That principle connects almost everything we are working on right now — from Entity Veracity Hub and Surge V3 to the cleanup work happening for clients in the real world.
This month’s core idea: “One website is a claim. Multiple independent websites agreeing is validation.” — Daryl Osborne, creator of Surge V3
One website is a claim. Multiple websites agreeing is validation.
Here is something most business owners get wrong about AI search: they think the job is convincing Google, ChatGPT, or Perplexity. So they rewrite the homepage, add some schema, and wait. But your own website is still first-party evidence. It matters, but it is also you talking about you. Independent corroboration gives an AI system more evidence to resolve what is true about the entity.
The practical reframe: your website is the anchor. The wider web is where the facts about your business are confirmed — or contradicted.
- Write the facts once — business name, address, phone, website, services, positioning.
- Search your own entity — review the first results and compare every important fact.
- Fix contradictions first — old numbers, old addresses, dropped services, inconsistent naming.
- Add better corroboration — prioritize authoritative sources over sheer mention volume.
Two accurate corroborating sources can be more useful than twenty sloppy ones. Daryl uses an Axis Corroboration Map to think about how close supporting sources sit to the trusted core of the web. The lesson is simple: quality and proximity to trusted sources matter more than chasing raw volume. Nobody can promise an AI citation. What we can do is remove contradictions, strengthen independent evidence, and make it easier for machines — and people — to understand the same business the same way.
Client work in action: entity cleanup before amplification
P&S Plumbing joined us in July. Surge V3 surfaced website areas where content was missing, while the broader entity review revealed the kind of cleanup work that needs to happen before an entity is amplified: missing content, asset organization, supporting-site verification, and nomenclature discrepancies. The team is adding missing pages, organizing the business’s digital assets, verifying supporting sites, and reconciling naming inconsistencies so the entity presents a cleaner, more coherent set of facts across the web.
Our operating principle: diagnose first. Repair what is broken. Amplify only after the foundation is trustworthy.
And a community win: the new Texas Defensive Driving School site went live at the end of June, and through July we continued to see visibility move upward and — just as importantly — remain stable. It is still early, so we are watching the trend rather than declaring a finish line. But stable improvement is exactly what we want to see after rebuilding the underlying foundation.
What we’re building
SIAI Secure Intake is live. Dekker built it to give client information, documents, and entity evidence one organized home instead of scattering the working record across inboxes and message threads. Before asking a client for something again, the team can check what has already been supplied. Steve with Big Dawg Dumpsters is the first client taking Intake through a full live run.
The evidence lifecycle: (1) Capture — Secure Intake organizes the first-party record. (2) Diagnose + Repair — the Entity Veracity Hub Health Clinic / Pre-Flight finds contradictions and cleanup needs before amplification starts. (3) Corroborate + Measure — Surge and supporting research test what is visible, verifiable, and independently supported across the wider web.
Surge V3 — better honesty about what was actually measured. Some of the most important July work in Surge V3 happened below the surface: better measurement accuracy, more stable scanning, and stronger honesty gates. If a sub-page cannot actually be fetched, Surge now reports not measured instead of turning a failed scan into false certainty. A useful diagnostic system should not just find more things. It should know when it doesn’t know: distinguish evidence from inference, and inference from absence of evidence.
Coffee with Team Human: the August challenge
Where does your business disagree with itself online? Search your business name and look at the first twenty results. What do those pages say your name is? Your address? Your phone number? Your services? If you find contradictions, do not rush to create more content. Start by fixing what is already wrong. (1) Write down your canonical business facts. (2) Search your business name and review the first 20 results. (3) Mark every important contradiction you find. (4) Fix those contradictions before chasing new mentions or corroborating sources.