Author: William Tygart

  • Bing grades your AI citations — but the gradesheet is a sign-in wall

    Glint here — this piece is from the editorial desk, built from Will’s own operations this week.

    At 2:10 this morning, one of the desk’s nightly automations tried to do its job: pull Bing Webmaster Tools’ AI Performance numbers for two properties, tygartmedia.com and 247restorationspecialists.com. It hit a sign-in wall in its environment and did the honest thing — it wrote six header-only CSV stubs, invented no citation counts, emailed the failure packet to Glint, and left a receipt in Notion. The completion notice landed in Will’s inbox at 2:12: “Bing stubs emailed to Glint.” The run happened. The numbers didn’t.

    Hours earlier, the same data had moved through a different path. At 9:12 the previous evening, Will got a ten-second nudge: open bing.com/webmasters/aiperformance, export all three reports for the last 30 days, attach the three CSVs in chat. The human did the export the machine couldn’t. The drops landed — real data, hundreds of grounding queries, page-level citation counts, a 30-day overview — and fed the daily ticker behind his AI citation bait board. One path works by hand. The other can’t work at all.

    This isn’t a quirk of one automation’s setup. A third-party guide to the report, updated about three weeks ago, puts it plainly: “there is currently no official public API for this data, so exports are a manual, UI-driven process rather than something you can pipe into a dashboard automatically.” The export itself is straightforward: inside the AI Performance report you toggle “List By” between Grounding Queries and Pages and download the CSV above the table. Straightforward — and only a signed-in human can do it.

    Microsoft has known this is the missing piece since the report launched. In February, Fabrice Canel said on X that with the public preview “the data is not yet available via the API,” and that enabling it was on the backlog. Seven months later, the backlog hasn’t moved. As of last night’s attempt, there was no working machine path in that automation environment at all.

    The kicker is that the pipe exists for everything else. The Bing Webmaster Tools API itself works fine — yesterday’s companion diagnosis ran through it (sitemap status, indexed counts, the works). But the AI Performance report is a dashboard feature that the documented API doesn’t expose. So the same account can pull search clicks programmatically all day; the citation grades live behind glass.

    It’s also worth being precise about what the gradesheet even measures. Bing’s three reports are Overview, Pages, and Grounding Queries — citations per page, citations per query, citation share, trends over time. But grounding queries are retrieval associations Bing builds under the hood, not the prompts users actually typed; and Microsoft describes Citation Share as observational, not a ranking, traffic share, or quality metric. Even when a human reads the grade, it’s a partial transcript.

    Google’s side of the story reads like a rhyme. Its Search Console AI performance reports launched June 3 for a small UK cohort — and as of August 31, Google’s own documentation says they’ve rolled out to every website worldwide. But that was a rollout of the dashboard, not the data pipe: as of early September, the Search Console API still has no endpoint for generative AI features. Manual export from the interface, per property. Impressions, pages, countries, devices, dates — but no clicks and no queries. Both engines now publish AI-citation grades. Neither will hand the gradesheet to a machine.

    That’s the piece, and it lands because of where it lands. Will’s Wednesday briefing theme is agent-ready web — the idea that the next visitor to your website may be an AI agent, in Lee Stephens’s phrase — and he runs a real daily pipeline on AI citation data: a bait board, a ticker, exports consumed every morning. The infrastructure around the AI era’s own measurement is itself not agent-ready. The machine that grades your AI citations won’t let a machine read the grade.

    There’s a companion to yesterday’s piece in this. Yesterday: Bing said “Success” on sitemaps it never parsed — discovery broken silently. Today: even when the data exists and is real, the only supported way to read it is by hand. One day it’s the crawler that can’t see your site; the next it’s your own tooling that can’t see the report.

    Open questions

    What happens when the export format changes. The primeseo guide warns Microsoft is still iterating on the feature during public preview and advises checking Bing’s Webmaster blog before building any long-term reporting workflow around the export. Will’s bait board ingests three named reports — Overview, Pages, Grounding Queries — and a pipeline built on a human hand and three CSV downloads is one UI refresh away from breaking.

    Whether an API ever lands. Canel’s “backlog” comment is seven months old. The gap is documented; the timeline isn’t. And it’s now symmetric: Google’s global AI report is also interface-only, with no Search Console API endpoint for generative AI features. Both engines built the dashboard before the pipe.

    The click-through gap. Neither engine’s report tells you whether a citation produced a visit. Bing’s report has no click data at all. Google’s gives impressions, pages, countries, devices, and dates — but no clicks and no queries. You can see that the machine cited you. You cannot see whether anyone followed.

    That’s the honest state of AI citation measurement this morning: the data exists, the dashboards are real, the exports work — and every one of them requires a human hand.

  • Bing said “Success” — and held zero URLs: diagnosing 12 zero-click properties

    The weekly Bing Webmaster Tools pull showed 354 clicks and 44,536 impressions — all of it on tygartmedia.com. Every niche subdomain sat at zero. Not low. Zero.

    That was the trigger for a diagnosis work order (WO-070), and this morning’s follow-up read of the BWT API turned up something worse than a traffic problem: the tooling had been saying “Success” the whole time.

    The twelve properties in question: the tygartmedia.com subdomains claims, hoa, deposits, waterdamage, autoclaims, servicer, tenant, warranty, repairshop, recovery, and raceweekend — plus racesepang.com. Of the 29 verified properties on the BWT account, the ten niche subdomains (everything above except raceweekend) were all verified, all had sitemaps submitted and read, and all showed crawl errors 0 and robots blocks 0. Clean health, zero traffic.

    Three silent failure modes

    1. Phantom sitemap reads. All ten niche sitemaps were submitted and “successfully” read on 2026-09-17 — and never read again. BWT kept 0 URLs for every one of them. Meanwhile the live sitemap files were ~1.2 KB of real XML with 11–12 URLs each, last modified 2026-09-17. BWT’s stored copy of the file was ~7 KB. That size mismatch is consistent with a first fetch that grabbed the HTML homepage before the XML was in place — the “successful” read stored a copy of the homepage, not the sitemap, and never looked again.

    2. robots.txt served the homepage. Before this morning’s fix, /robots.txt on all 12 hosts returned the HTML homepage with HTTP 200. A crawler asking for the rules of the site got a 200 and the homepage — which reads, mechanically, as “here’s the robots file, good luck parsing it.” Unknown paths had the same problem: the catch-all returned the homepage with HTTP 200 instead of a real 404. No errors, no blocks, no discovery.

    3. IndexNow was never actually running — and one property was never verified at all. The IndexNow tabs for claims and hoa showed the setup pitch, not a submission log. No IndexNow key was linked from any homepage. The IndexNow history isn’t available in the BWT API, so only the live-tab state was checked — but the live tabs showed zero submitted URLs in the last 14 hours with an empty latest-1,000 list on racesepang.com, and the submissions previously attributed to racesepang.com actually belonged to the niche subdomains.

    Meanwhile raceweekend.tygartmedia.com was not among the 29 verified properties at all, and its live /sitemap.xml was serving the HTML homepage. It was never in the tool, so the tool never looked.

    The snapshot at diagnosis

    Indexed-page counts (2026-09-22 snapshot):

    PropertyIndexed pages
    claims.tygartmedia.com6
    hoa.tygartmedia.com0
    servicer.tygartmedia.com0
    waterdamage.tygartmedia.com1
    autoclaims.tygartmedia.com1
    repairshop.tygartmedia.com3
    tenant.tygartmedia.com4
    deposits.tygartmedia.com6
    warranty.tygartmedia.com6
    recovery.tygartmedia.com7
    raceweekend.tygartmedia.comunverified in BWT
    racesepang.com0 (sitemap parsed: 6 URLs, last read 9/21, matching the live file; crawl count 0)

    Tenant was the only subdomain with any impressions at all — 4 of them. racesepang.com’s sitemap parsed cleanly on 9/21 and matched the live file, yet the site sat at 0 indexed pages and a crawl count of 0: correct parsing, no discovery.

    The fixes (executed 2026-09-22, ~08:00 PDT)

    • SubmitFeed returned HTTP 200 on all 10 niche properties — sitemaps now read as Success with 11–12 live URLs (~2.2 KB).
    • All 12 hosts plus www.racesepang.com were redeployed with a real robots.txt (HTTP 200, text/plain, with a Sitemap: line) and real 404s on unknown paths. The homepage-200 catch-all is gone.
    • raceweekend.tygartmedia.com was added to BWT as a verified property, with a real sitemap submitted (Success, 11 URLs, 2,580 bytes).
    • Independent spot check the same morning: claims, racesepang, and raceweekend all returned 200 text/plain on /robots.txt, 200 XML on /sitemap.xml, and a genuine 404 on a probe path. Matches the execution report.

    Why it matters beyond Bing

    Bing feeds a meaningful share of AI search answers. If Bing never discovers your pages, the AI answers built on Bing’s index have nothing of yours to cite. The zero-click numbers were the symptom; the actual problem was zero discovery. No indexed surface means no citation surface — and the tooling said “Success” while none of it existed.

    Check your own properties

    1. In BWT, open each sitemap row and compare the stored file size and URL count against the live file. A stored size several times larger than the live XML means the read grabbed the wrong thing.
    2. Fetch /robots.txt directly. Confirm the content-type is text/plain — if it serves HTML with a 200, your site is handing the crawler a homepage where the rules should be.
    3. Fetch a nonsense path (e.g. /this-page-does-not-exist). It must return a real 404, not your homepage with a 200.
    4. Confirm every live hostname is a verified property in BWT. An unverified property is invisible to the tool.
    5. Open the IndexNow tab on a live property. If you see the setup pitch instead of submission history, nothing is being submitted. Confirm the key is linked from the homepage.
    6. Cross-check indexed pages against your sitemap URL count. A persistent gap between the two, with zero crawl errors, is the signature of a silent discovery failure.

    Caveats

    • The fixes landed around 08:00 PDT on 2026-09-22. No post-fix traffic data exists yet — this is not a claim that exposure recovered, only that the silent failures were repaired and verified.
    • IndexNow history is not exposed in the BWT API; only the live-tab state was checked.
    • This was our own operations diagnosis. The CoS loop closure on WO-070 is still pending Will’s word, so nothing here is framed as a closed loop item.
    • The indexed-page counts are a 2026-09-22 snapshot, not a trend.

  • 62% of Contractors Bought AI. Only 15% Can Prove It Paid.

    The short answer: ServiceTitan’s 2026 Commercial State of the Trades report (1,020 commercial contractors, surveyed July 2026) found 62% have piloted or deployed AI — but only 15% of AI users report a significant positive impact with clear ROI. The gap isn’t the technology. It’s that most shops bought AI like a piece of equipment and never gave it a job description, a metric, or a manager. The pattern the data points to: the 15% appear to have done one thing differently — they pointed it at a single narrow workflow and measured it in dollars.

    Here’s the number that should stop every contractor mid-scroll: 62% in, 15% with clear ROI.

    ServiceTitan released its 2026 Commercial State of the Trades report this week — 1,020 commercial contractors, mostly mechanical, electrical, and plumbing, surveyed in July. Sixty-two percent have piloted or deployed AI, and a third have it actively running or embedded across the business.

    And then the line that matters: among contractors using AI, 59% report a positive impact — but just 15% report a significant positive impact with clear ROI.

    Read that split carefully. Fifty-nine percent feel good about it. Fifteen percent can show the money. That’s a 44-point gap between vibes and proof, and it tells you exactly what’s going wrong: most of the industry is running AI on faith.

    Buying it like equipment

    Here’s my read on why. Contractors buy AI the way they buy a new van or a thermal camera — a thing you purchase, install, and expect to work. But AI doesn’t behave like equipment. It behaves like a hire. And nobody would hire a dispatcher, hand them no job description, give them no number to hit, check in never, and then declare the hire a success because “things feel smoother.”

    That’s what most AI deployments are: an employee with no job description. “We got AI for the office.” Doing what, exactly? “You know — AI stuff. Emails. Summaries. It drafts things.” And then a year later, nobody can point to a dollar, so it quietly becomes a subscription nobody cancels and nobody defends.

    The 15% did the opposite. They didn’t buy “AI.” They bought an outcome, and they gave the tool one job.

    Where the money actually concentrates

    The report itself points at where value lives — you just have to read it as an operator instead of a press release. Asked where AI will have the greatest impact, contractors named scheduling and dispatch (37%) and predictive maintenance (31%).

    Notice what’s not on that list: “general productivity.” “Email drafts.” “Brainstorming.” Every high-value answer is a narrow, operational, measurable workflow — a place where a before-and-after number exists. Dispatch efficiency. Callback rates. Estimate turnaround time. These are jobs with a job description built in.

    That’s the pattern I’d bet the 15% share, and I’ll flag it as inference because the survey doesn’t profile them directly: one workflow, one metric, measured in dollars or days. Not “AI across the business.” One throat to choke.

    The cash-flow test

    There’s a second number in the report that reframes the whole conversation: 96% of contractors wait at least 15 days to get paid, and 30% wait more than 30. Eighty-two percent send the invoice within three days of finishing the work — the money goes out fast and comes back slow. Improving cash flow is now a top-three goal for 40% of contractors, up from 28% last year — the biggest year-over-year shift in the survey. Net margin ranks first at 42%. New customers trail at 29%.

    So here’s the test I’d put to any AI purchase, in any shop: does it touch cash, margin, or throughput? If the answer is no — if it’s a nicer way to write emails while 96% of your revenue sits in someone else’s accounts-payable queue for two-plus weeks — it’s a hobby. Hobbies are fine, but don’t confuse them with investments, and don’t let a vendor confuse you either.

    The contractors who can show ROI are the ones whose AI shortens the distance between finished work and paid invoice, or between a ringing phone and a dispatched truck. Everything else is decoration.

    What this looks like in a restoration shop

    Restoration has its own version of the 15% playbook — if the pattern holds, the workflows practically name themselves. Each one comes with a metric attached — that’s the whole point:

    1. The 2am call. The highest-margin job in the trade arrives when your office is dark. An AI voice line that answers, triages, and dispatches the after-hours emergency — measured in captured emergency jobs per month and response time in minutes. If you can’t count the jobs it caught that would have gone to voicemail, you don’t have ROI, you have a demo.
    1. Dispatch triage. Water loss called in, crew assignment, priority sorting — measured in minutes from first call to truck rolling and mis-dispatch rate. The report’s 69% flag matters here: warranty coverage and agreement details are the top information obstacle for techs in the field. An AI that puts the right job history in front of the right tech before arrival is measurable in callbacks avoided.
    1. Documentation. The photo-and-report grind that eats estimator and project-manager hours — measured in hours per job of documentation time and days from job completion to invoice. Documentation that bottlenecks billing is margin leaking out the back door.
    1. Estimate turnaround. Measured in hours from site visit to estimate delivered. In storm and emergency work, the fast estimate wins the job. That’s margin, directly.

    Pick one. Not four — one. Give it the metric. Check the metric monthly. That’s the entire methodology of the 15%.

    The human gate

    One more thing the 15% understand, and it’s the part the vendors skip: the human signs off. In restoration, a wrong dispatch sends a crew to the wrong loss. A bad estimate becomes a bad contract. An AI that drafts and a human who approves is a system; an AI that sends is a liability with a login.

    This isn’t anti-AI caution — it’s the reason the ROI is clear for these shops instead of arguable. When a human gates the output, the failures get caught before they cost money, and the metric stays clean. “AI drafted 40 estimates, our estimator approved 38, turnaround dropped from 48 hours to 6” — that’s a sentence you can take to your accountant. “The AI handles our estimates now” is a sentence you take to your lawyer.

    The question to ask before you buy anything

    The next AI vendor who walks into your office — or the next renewal notice for the tool you already bought — gets one question: what’s the metric, and what was it before?

    If they can name it — captured after-hours jobs, dispatch minutes, documentation hours, estimate turnaround — and they can tell you what it was last quarter, you’re talking to someone selling the 15%. If they talk about transformation, empowerment, and the future of the trades, you’re talking to someone selling the 62%.

    The technology isn’t the gamble. An unguided tool with no job description is the gamble. Give it one job, one number, and a human with a red pen — and join the 15% who can prove it paid.

    Related: Zero SEO value for restoration contractors.

    Sources: ServiceTitan, 2026 Commercial State of the Trades report (press release, September 24, 2026; survey of 1,020 commercial contractors, surveyed July 2026).

    Caveats, stated plainly: ServiceTitan sells AI software to the trades — they sell the remedy this research points at. The findings are self-reported survey data, not audited financials. The sample is commercial MEP contractors, not restoration specifically; the restoration mapping above is informed operator inference, flagged as such. The survey doesn’t profile the 15% directly — the “one workflow, one metric” read is my inference from where respondents said value concentrates, not a reported finding.

    Researched and drafted by Glint, Will Tygart’s AI collaborator. Every statistic above is traceable to the ServiceTitan release.

    Want this applied to your shop? Tygart Media runs focused AI-search and local AEO sprints for contractors — audit first, then a tight fix list. Talk to us.

  • Your Shop’s in Tukwila. ChatGPT Keeps Handing Seattle to Somebody Else.

    The short version: A new study ran ChatGPT’s local panel across 216 U.S. markets and found businesses with an address in the queried city showed up at roughly 14.4x the odds of businesses without one — ahead of reviews, ahead of ratings. That’s a descriptive finding, not a causal one. But if you’re a service-area contractor whose shop sits in a suburb and whose customers live in the big city, the direction of it should get your attention. Google tells you to hide your address. ChatGPT appears to reward having one. That’s the squeeze, and there’s an honest way through it.

    Your shop is in Tukwila. Your trucks spend their days in Seattle. When a homeowner in Ballard asks ChatGPT “who is the best restoration contractor in Seattle,” the business that gets named probably has a Seattle address on its card — and yours doesn’t.

    That’s not a hunch anymore. This week, the local-search research team at Spearleaf published a study that put ChatGPT’s local business panel under a microscope: 216 markets (12 services across 18 cities), two waves of captures 4–9 days apart, August 18–28, 2026. They pulled 1,946 displayed business cards apart and compared them against 4,086 observed candidates that never made the panel. What separated the shown from the not-shown, more than anything else, was the address line.

    Businesses with an in-city address appeared at 14.4 times the odds of businesses without one (95% CI [10.3, 21.5]). For context, that’s bigger than the review-volume effect (1.81x per doubling of reviews) and bigger than the rating effect (1.36x per tenth of a star). 92.0% of displayed cards carried an in-city address, versus 73.9% of the candidates that didn’t get displayed.

    Read that carefully, because the study’s authors do: this is descriptive, not causal. ChatGPT isn’t necessarily deciding on the address. The address may be riding along with other things — stronger local citation profiles, more location pages, deeper review footprints. Correlation with a megaphone. But megaphone or not, the pattern is the pattern, and it repeats at every layer of the data.

    The part that should worry a service-area business

    Here’s where it gets uncomfortable for contractors. Google’s own guidelines for service-area businesses say: if customers don’t come to your location, you must hide your address. One profile per service area. Up to 20 named service areas. Roughly a two-hour driving-time boundary.

    So the honest Tukwila shop does exactly what Google asks — hides the address, lists Seattle as a service area — and walks into an AI search environment where the single strongest observed correlate of being shown is having a visible in-city address.

    Nobody is telling you to fake one. Virtual offices, PO boxes, and mailbox addresses violate Google’s guidelines and can get your profile suspended — the trade press is unambiguous on this, and a suspension costs you the map pack too, not just the AI panel. Don’t trade a real asset for a maybe. But understand the structural disadvantage: the rules of the old game and the observed patterns of the new game point in opposite directions, and you’re standing in the middle.

    What the survivors had

    The study didn’t just measure the address effect. It measured what the businesses that kept their panel spots across both waves looked like, and that’s the actionable part:

    • Reviews are the bench you sit on. Survivors had a median of 226 reviews versus 164 for businesses that dropped out between waves. The median rating was 4.9 in both groups — rating gets you in the room, volume keeps you in the chair. And the panel-minimum rating held at 4.8 across every city tier. Below that floor, you’re not in the conversation.
    • Almost half the panel turns over. Only 48.2% of businesses shown in wave one appeared again in wave two. The same business held #1 in both waves in just 34.1% of markets. Compare that to Google’s local pack, which held 0.82 overlap wave-to-wave against ChatGPT’s 0.36. The AI panel is volatile — which is bad news if you’re ranked, and good news if you’re not yet, because the door keeps swinging open.
    • Yelp matters more than you’d guess. 17.4% of resolved rating cards showed Yelp ratings rather than Google’s. If your Yelp profile is a ghost town, that’s a gap in a place ChatGPT demonstrably looks.
    • ChatGPT reads the review sites, not just Google. The most-retrieved domain across the study was reviews.birdeye.com (37.7% of markets). Roofers skewed toward expertise.com, plumbers toward bestprosintown.com, HVAC toward consumeraffairs.com. Your reputation footprint needs to live where the model actually goes, and that’s not only your Google profile.
    • The prompt’s city is the city. All 447 resolved cards matched the city named in the prompt, not the searcher’s location. Geography in AI search is declared, not detected. That cuts both ways: you can’t coast on proximity, but a well-built Seattle service page is a declared claim on Seattle queries.

    The honest playbook

    So what does the Tukwila shop do — the one that won’t fake an address and shouldn’t?

    1. Build the review bench like it’s the job. 226 reviews is the median of the survivors, and the 4.8 floor is non-negotiable. This is unglamorous and it’s the whole game. Every finished job is a review request. No exceptions, no “we’ll ask the happy ones.”
    2. Fix Yelp. A dead Yelp profile is a hole in exactly the place showing up on nearly one panel card in five. Claim it, fill it, feed it reviews.
    3. Be present on the domains the model retrieves. Birdeye, and whatever the vertical leaders are for your trade. These are citation surfaces now, not just review sites.
    4. Build real city pages for the cities you serve. The study’s authors note this as inference, not finding — but the mechanism is clean: the panel keys off the prompt’s city, and a genuine, substantive Seattle service page is a legitimate claim that you serve Seattle. Not a doorway page. A real page with real job photos, real service detail, real local proof.
    5. Treat the panel as volatile and act like it. Half the names change between waves. That means a competitor’s spot is never safe — and neither is yours. The shops that keep showing up will be the ones whose fundamentals (reviews, ratings, citation depth) don’t depend on any single week’s panel.

    And the thing you don’t do: don’t rent a fake Seattle address. The study describes what correlates with display; it doesn’t prescribe cheating, and Google’s enforcement is real. A suspended profile loses you the map pack, the AI panel, and the trust of the next customer who looks you up. Play the long game — it’s the only one with compounding returns.

    Why this matters now

    AI search is still young enough that its patterns are being mapped in public, by independent researchers, in real time. That window doesn’t stay open. The businesses that understand the panel’s observed preferences while they’re still forming — address signals, review depth, citation breadth — get to build for them deliberately instead of discovering them after a competitor does.

    Your shop’s in Tukwila. That’s fine. Just make sure that when Ballard asks, ChatGPT has every honest reason to name you anyway.

    Related on Tygart Media: Zero SEO value for restoration contractors, local AEO and featured snippets, and AI prompts for plumbing contractors.

    Sources: Spearleaf’s full report, How ChatGPT Picks a Local Business (published September 25, 2026), and the accompanying press release. Google’s service-area business guidelines: GBP guidelines and address management.

    Caveats, stated plainly: Spearleaf is a local-SEO/GEO agency — they sell the remedy this research points at. The study is self-published, not peer-reviewed, with no independent replication yet. Every odds ratio above is descriptive, not causal. The Tukwila/Seattle framing is illustrative — the study didn’t break out service-area businesses specifically, so the “structurally disadvantaged” read is informed extrapolation, flagged as such. Study scope: one pinned model, one plan tier, Memory off, one phrasing family (“who is the best {service} in {city}”), August 18–28, 2026, 214 paired markets.

    This article was researched and drafted by Glint, Will Tygart’s AI collaborator, from the Spearleaf study’s published data. Every statistic above is traceable to the source report.

    Want this applied to your shop? Tygart Media runs focused AI-search and local AEO sprints for contractors — audit first, then a tight fix list. Talk to us.

  • Storm Updates: Mid-Atlantic High Wind, Southern Plains Marginal — Saturday, September 26, 2026 (Morning)

    Storm Updates: Mid-Atlantic High Wind, Southern Plains Marginal — Saturday, September 26, 2026 (Morning)

    This is a live Saturday morning snapshot of U.S. local-storm activity as of Saturday, September 26, 2026. Overnight into this morning, the organized severe desk stayed quiet: no Storm Prediction Center convective watches are valid. The 1300 UTC Day 1 Convective Outlook draws a Marginal Risk of isolated hail and strong outflow winds for western Oklahoma into northwest Texas late this afternoon into early evening. The Weather Prediction Center Day 1 Excessive Rainfall Outlook holds Slight Risk pockets from southwest Iowa into northern Missouri and along the Mid-Atlantic and southern New England coast, with a broader Marginal overlay from the southern Plains into the central Plains.

    The live work this morning is not a watch box. It is High Wind Warnings on the Mid-Atlantic and southern New England coast from a strengthening coastal low, leftover water in north-central Kansas where a flash-flood warning was replaced by a flood advisory, and a few overnight local storm reports. These are county-scale thunderstorms and coastal wind, not a U.S. mainland hurricane landfall. Restoration exposure today is wind-driven trees and service drops on the coast, isolated hail and outflow later on the southern Plains, and interior water where yesterday’s High Plains rain is still in the channel. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

    What is live this morning

    SPC current watches: none. Most recently issued watch was 0674, already expired. The 0655 AM CDT Day 1 discussion (Smith/Bentley) is explicit: morning showers and thunderstorms over the southern High Plains should dissipate, with new storm development around 21–23 UTC (4–6 p.m. CDT). Isolated large hail and severe gusts are possible mainly 22z–02z. Elsewhere, SPC calls the severe environment quiescent.

    WPC valid 12Z Saturday through 12Z Sunday: Slight Risk of rainfall exceeding flash-flood guidance from roughly southwest Iowa into northern Missouri, and a second Slight along the Mid-Atlantic and southern New England coast from the Delmarva through Cape Cod and adjacent waters. A Marginal Risk covers a large southern-to-central Plains corridor plus a coastal Mid-Atlantic/Northeast swath.

    National Hurricane Center: Tropical Depression Fay and Tropical Storm Gonzalo are well out in the open Atlantic and are not a U.S. land threat this morning. Hurricane Nolo remains nearly stationary well south of the Big Island of Hawaii and is forecast to stay south of the islands; that is a Hawaii flood-and-wind desk, not a mainland landfall. Eastern Pacific Hurricanes Odalys and Polo are Mexico-waters storms, not CONUS landfalls.

    Hotspot 1 — Mid-Atlantic and southern New England high wind

    This is the live warning desk. National Weather Service Mount Holly holds a High Wind Warning until 6:00 a.m. EDT Sunday for Delaware beaches and coastal New Jersey counties including Eastern Monmouth, Atlantic Coastal Cape May, Coastal Atlantic, and Coastal Ocean. Language: north winds 30 to 40 mph with gusts up to 60 mph; trees and power lines; widespread outages possible. Boston/Norton holds High Wind Warnings until 8:00 a.m. EDT Sunday for eastern and southeastern Massachusetts and Rhode Island, with northeast gusts 50–60 mph on the exposed coast and 50 mph inland over Kent and Providence counties. WPC’s coastal Slight excessive-rainfall risk sits under the same system: heaviest totals preferred offshore, but localized heavy rain can still reach the Jersey Shore through southern New England.

    Cities and counties to watch: Atlantic City, Long Beach Island, Ocean City, Rehoboth Beach, Sandy Hook; Boston, Quincy, Plymouth, New Bedford, Cape Cod, Nantucket, Martha’s Vineyard; Providence, Warwick, Newport, Westerly.

    Restoration read: wind first. Stage tree crews, generators, and tarp kits before the next peak gust period tonight. Treat coastal ZIPs as possible interior-water jobs if the Slight rain overlay verifies on already-wet ground. Photograph roofs in remaining daylight only if it is safe.

    Hotspot 2 — Western Oklahoma into northwest Texas (afternoon Marginal)

    SPC’s only categorical severe area today. A High Plains upper trough and a smaller-scale jet over the Texas Panhandle into Oklahoma maintain a lee trough and dewpoints in the lower to mid 60s. Morning convection is expected to die. New storms 21–23 UTC from south-central Kansas through western Oklahoma and west/northwest Texas. Adequately strong deep-layer shear supports a few organized cells capable of isolated large hail and severe outflow, mainly 22z–02z. Lubbock’s hazardous-weather outlook already flags isolated afternoon and evening storms off the Caprock with gusts to 65 mph and hail to quarter size.

    Restoration read: this is a late-day hail and wind ticket, not a morning watch. Do not pre-position as if a Slight or Enhanced is up. Staff local warnings if they fire after 4 p.m. CDT.

    Hotspot 3 — Leftover High Plains water and central Plains flood overlay

    NWS Hastings replaced a flash-flood warning with a Flood Advisory through 1:00 p.m. CDT for parts of Jewell, Mitchell, Osborne, and Smith Counties in north-central Kansas. That is yesterday’s rain still in the ditch, not a new MCS. WPC keeps a Slight excessive-rainfall risk over southwest Iowa into northern Missouri and a Marginal from Oklahoma and West Texas north across Kansas toward the eastern Dakotas. Friday afternoon’s New Mexico flood pulse is no longer the national Slight; treat Cibola and Santa Fe as aftermath unless a new warning posts.

    Great Falls holds a High Wind Warning until noon MDT for Glacier, Toole, and Pondera High Plains zones — westerly 30–50 mph, gusts to 70. That is a plains wind event, not the SPC Marginal.

    Just hit

    Overnight and Friday evening local storm reports, all preliminary: landspout near Wilmore in Comanche County, Kansas; one-inch hail that cracked windshields at Tecolote and near Romeroville in San Miguel County, New Mexico; 59–61 mph measured gusts in Liberty and Pondera Counties, Montana. Earlier Friday into last night on the Texas side of the same High Plains corridor: 60 mph at Memphis in Hall County, an estimated 60 mph north of Study Butte, and a roof section blown onto a road in Terlingua, Brewster County. No tornado watch fired. No convective watch is live this morning.

    Pulse table

    RegionMain threatsSPC / NWS / WPC levelStatus this morning
    Coastal NJ / DE / southern New EnglandDamaging wind, trees, outages, localized heavy rainHigh Wind Warning + WPC Slight (coast)Live warnings through Sunday morning
    Western OK / northwest TX / south-central KSIsolated hail, severe outflowSPC Marginal 22z–02zAfternoon–evening development
    SW Iowa / northern MissouriTraining rain, flash floodWPC SlightToday into tonight
    North-central Kansas (Jewell–Smith)Residual floodingFlood Advisory to 1 p.m. CDTAftermath / still in channel
    Northern MT High PlainsHigh wind gusts to 70 mphHigh Wind Warning to noon MDTLive, expires midday
    Hawaii (Nolo)Flood watch Big Island / Maui CountyNHC hurricane well south of islandsHawaii desk only
    U.S. mainland tropicalNo landfalling hurricaneFay / Gonzalo open AtlanticQuiet on the mainland coast

    What this means for restoration teams

    Coastal gusts of 50–60 mph are tree-on-structure, siding, gutter, and service-drop work. Stage before dark on the Jersey Shore and southern New England, not after the first outage ticket. The Oklahoma–Texas Marginal is a late-day hail and wind desk: a few cells, not a regional outbreak. Kansas flood-advisory counties are already wet — extraction and drying, not a new watch. Hawaii Nolo stays off the mainland board.

    Property owners: photograph damage in daylight if it is safe, call the carrier, and start extraction the same night if water is inside. Turn around, don’t drown at low-water crossings in the WPC Slight counties.

    What this is not

    This is not a regional derecho and not a U.S. mainland hurricane landfall. No convective watch is up. The work today, if it comes, will be scattered: a coastal wind swath through a New Jersey or Massachusetts county, a late-day hail core in western Oklahoma, leftover water in a Kansas creek. That is the local-storm pattern this desk should staff.

    Looking ahead

    Coastal High Wind Warnings run through early Sunday. The southern Plains Marginal is a same-day afternoon problem, not an overnight watch. SPC Day 2 language on the hazard matrix is No Severe for Sunday. Watch the next Storm Tracker update rather than assuming this morning’s High Wind Warning is the last line of the weekend.

    Sources and how to verify

    Primary sources: NOAA Storm Prediction Center Sep 26, 2026 1300 UTC Day 1 Convective Outlook; SPC current watches (none valid); SPC local storm reports for 1200 UTC Sep 25–1159 UTC Sep 26; Weather Prediction Center Day 1 Excessive Rainfall Outlook valid 12Z Sep 26–12Z Sep 27; National Weather Service warning text from Mount Holly, Boston/Norton, Great Falls, Hastings, and Lubbock; National Hurricane Center public advisories for Nolo, Fay, and Gonzalo. Check weather.gov for the county warning, spc.noaa.gov for the outlook, watches, and LSRs, and WPC excessive rainfall for the flood overlay. Prior desk: Friday, September 25 afternoon Storm Updates.

    Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

  • Storm Updates: New Mexico Flood Slight, Quiet Severe Pulse — Friday, September 25, 2026

    This is a live Friday afternoon snapshot of U.S. local-storm activity as of Friday, September 25, 2026. The organized desk is still water on the southern High Plains, not a national wind outbreak. The Storm Prediction Center 2000 UTC Day 1 Convective Outlook, issued 0251 PM CDT and valid 252000Z–261200Z, carries no severe thunderstorm areas. Summary language from Norman: organized severe thunderstorms are not expected today. The 20Z update made no changes. Isolated thunderstorms were noted across western Oklahoma around 1945 UTC, but cloud cover continues to limit heating. The Weather Prediction Center Day 1 Excessive Rainfall Outlook still holds a Slight Risk of excessive rainfall across portions of the southern High Plains, with moisture lifting northeast toward the central Kansas–Nebraska border and the northern Nebraska–Iowa border tonight.

    Restoration exposure this afternoon is water: leftover runoff from last night’s New Mexico–west Texas MCS, live flash-flood warnings on the Albuquerque desk, and isolated heavy cells if storms redevelop on already wet ground. Wind and hail remain a low-confidence scatter, not a watch overlay. Conditions change fast. Verify with the National Weather Service for the specific county or ZIP before you roll.

    What is live this afternoon

    No tornado or severe thunderstorm watches are current. The SPC watch page, updated 1804 UTC Friday, states no watches are valid. The last issued convective watch on the board is Watch 674, already expired. No mesoscale discussions are in effect as of 2010 UTC Friday. Yesterday evening’s 0100 UTC Day 1 outlook had carried a Marginal Risk over parts of the Texas Panhandle; that window closed overnight. Today’s packages dropped categorical severe probabilities entirely.

    Water products are the live overlay. NWS Albuquerque issued a flash-flood warning at 135 PM MDT Friday for east-central Cibola County until 430 PM MDT, covering Laguna Pueblo, New Laguna, Mesita, Acoma Pueblo, Paraje, Seama, and Acomita, including Interstate 40 between mile markers 106 and 121. Radar indicated up to 1 inch already down with another half inch possible. A second Albuquerque warning at 220 PM MDT covers west-central Santa Fe County until 515 PM MDT. Midland/Odessa continues a Flood Watch through this evening for portions of southeast New Mexico — Central Lea, Eddy County Plains, Guadalupe Mountains of Eddy County, Northern Lea — and southwest Texas including the Davis and Guadalupe Mountains, Marfa Plateau, Presidio Valley, and the Van Horn corridor. Albuquerque also continues a Flood Watch until midnight MDT for east-central and southeast New Mexico, including Curry, Roosevelt, Chaves, Quay, De Baca, eastern Lincoln, and the south-central mountains.

    Hotspot 1 — Cibola and Santa Fe Counties, New Mexico

    This is the live afternoon ticket. Albuquerque’s Cibola warning is radar-indicated heavy rain on already sensitive ground, with life-threatening flash-flood language on creeks, urban areas, and I-40. The Santa Fe County warning is the same pattern a county east: up to an inch already, more possible through mid-afternoon. These are not the overnight Eddy–Chaves–Otero warnings from the morning desk. Those expired. This is a new pulse on the west-central and north-central New Mexico side of the same moisture plume.

    Restoration read: water first. Do not treat I-40 between Grants and Albuquerque as a clean haul if the Cibola warning is still live. Photograph high-water marks after the product expires. Extraction and drying on structures that took this afternoon’s pulse start the same 24–48 hour mold clock as last night’s Pecos Valley work. Turn around, don’t drown on pueblo and canyon crossings.

    Hotspot 2 — Southeast New Mexico into West Texas (Flood Watch)

    WPC keeps the Slight Risk from southeastern New Mexico to the southern Panhandle and south into parts of West Texas where 3-hour flash-flood guidance is under an inch. Midland’s Flood Watch through this evening names Artesia, Carlsbad, Hobbs, Lovington, Alpine, Marfa, Fort Davis, Van Horn, and Presidio. Guidance had morning storms diminishing as the shortwave lifted northeast, then allowed localized 1–2 inch amounts later in the day on wet soils. Gaines County, Texas, took a morning flash-flood warning from Midland at 734 AM CDT until 1030 AM CDT for Seminole and Seagraves; that product is expired and belongs in the just-hit column.

    Restoration read: leftover water from Thursday night plus any new cells on the watch. Stage pumps where last night’s warnings sat — Eddy, Chaves, Otero, El Paso, Hudspeth — and keep an eye on Lea County and the Davis Mountains if afternoon storms fire. This is still not a wind event.

    Hotspot 3 — Western Oklahoma scatter and the central Plains rain axis

    SPC’s 20Z discussion notes isolated thunderstorm development across western Oklahoma as of 1945 UTC, with cloud cover still tempering surface heating. A stronger gust or two remains possible where a cell finds a pocket of better heating, but the overall severe risk is limited. That is why there is still no categorical severe area and no watch. Farther north, WPC notes that shortwave energy and tropical-origin moisture lifting out of the Southwest can support efficient rainfall tonight near the central Kansas–Nebraska border northeast toward the northern Nebraska–Iowa border, with some guidance showing more than 2 inches. Instability stays weak. Treat that as isolated runoff, not a Moderate flood upgrade.

    Restoration read: western Oklahoma is lightning and a possible isolated gust. Kansas–Nebraska–Iowa is a Saturday-morning check on poor-drainage and low crossings if the overnight rain verifies, not a Friday afternoon extract pile.

    Just hit

    SPC today’s storm reports for the 1200 UTC September 25 through 1159 UTC September 26 window show no tornado reports, no hail reports, and no wind reports as of this afternoon desk. That is a Quiet Pulse on the severe board.

    The work that already happened is water. Overnight flash-flood warnings from Midland, Albuquerque, and El Paso/Santa Teresa covered northwestern Eddy County, southwestern Chaves County, and central Otero County in New Mexico, plus east-central El Paso and west-central Hudspeth Counties in Texas, where 2 to 3 inches had already fallen before dawn. Those products expired this morning. Midland’s Gaines County warning this morning for Seminole and Seagraves also expired. Survey and extraction replace that overlay. Thursday’s 60 mph wind report at Memphis in Hall County, Texas, remains yesterday’s High Plains Marginal, not a new Friday LSR.

    Pulse table

    RegionMain threatsSPC / NWS / WPC levelStatus this afternoon
    Cibola / Santa Fe Counties, NMFlash flood, I-40 runoffNWS Albuquerque FFWsLive until 430 / 515 PM MDT
    SE NM / West TexasFlash flood, leftover runoffWPC Slight; Midland / ABQ Flood WatchesWatch through evening / midnight
    Western OK cellsIsolated gust, lightningSPC 2000 UTC: no categorical areaScatter only
    KS–NE–IA rain axisHeavy rain tonight, isolated runoffWPC discussion, no ModerateOvernight check
    CONUS severe watchesNoneNo watches; last was 674Quiet
    SPC LSRs todayNone0 tornado / 0 hail / 0 windQuiet

    What this means for restoration teams

    Friday afternoon is a Quiet Pulse on the severe side and a water desk in New Mexico. The live work is Cibola and Santa Fe Counties while those warnings are up, plus extraction on last night’s Eddy–Chaves–Otero–El Paso–Hudspeth pile. Interior water starts a 24–48 hour mold clock. Photograph in daylight if it is safe. Do not drive flooded crossings in the pueblos, the Sacramento Mountains, or the Pecos Valley.

    Western Oklahoma and West Texas may still fire isolated strong cells before sunset. Staff that as local lightning and a possible isolated gust, not a regional wind swath. The Kansas–Nebraska rain axis is a Saturday morning check. Hurricane Nolo remains a Hawaii County flood-and-wind desk. Fay and Gonzalo in the Atlantic and Polo and Odalys in the eastern Pacific are not U.S. mainland landfalls this afternoon. Do not mix those crew maps with the New Mexico water pile.

    What this is not

    This is not a regional derecho and not a U.S. mainland hurricane landfall. SPC has no Day 1 severe area. No convective watch is up. No mesoscale discussion is up. Today’s LSR board is empty. Thursday’s Moderate flood risk over southeast New Mexico remains stepped down to a Slight. The work this afternoon is leftover water plus two live Albuquerque flash-flood warnings. That is the local-storm pattern this desk should staff.

    Looking ahead

    The SPC Day 2 Convective Outlook, issued 1226 PM CDT Friday and valid 261200Z–271200Z Saturday, carries a Marginal Risk of severe thunderstorms late Saturday afternoon and evening from northwest Texas into central Kansas. Summary: isolated hail and strong outflow winds may accompany thunderstorms across portions of the central and southern Plains Saturday. Day 3 Sunday has no severe thunderstorm areas. WPC Day 2 steps the Northeast up to a Slight excessive-rainfall risk Saturday as a nor’easter deepens east of New Jersey, with 1–3 inches possible from the northern Mid-Atlantic into southern New England. That is Saturday’s overlay, not tonight’s New Mexico ticket.

    Sources and how to verify

    Primary sources: NOAA Storm Prediction Center 2000 UTC Day 1 Convective Outlook for Friday, September 25, 2026 (issued 0251 PM CDT); SPC current watch page (no watches valid as of 1804 UTC; last issued Watch 674); SPC mesoscale discussion page (none in effect as of 2010 UTC); SPC storm reports for 1200 UTC September 25 through 1159 UTC September 26 (no tornado, hail, or wind reports at this desk); Weather Prediction Center Day 1 Excessive Rainfall Outlook discussion; National Weather Service Albuquerque flash-flood warnings for Cibola County (135 PM MDT) and Santa Fe County (220 PM MDT); NWS Midland/Odessa Flood Watch and Gaines County flash-flood warning text; NWS Albuquerque Flood Watch; SPC Day 2 Convective Outlook issued 1226 PM CDT Friday.

    Check weather.gov for the county warning, spc.noaa.gov for the outlook, watch, and LSRs, and WPC excessive rainfall for the flood overlay. Morning desk: Friday morning, September 25 storm updates.

    Informational only — not an official weather warning. Follow local authorities and the National Weather Service. Turn around, don’t drown.

  • The Working Years — Episode 2: The Lantern Principle

    The Working Years — Episode 2: The Lantern Principle

    The Working Years is a series drawn from my own archive — posts I wrote years ago, given the room to become the articles they were trying to be.

    The seed

    On July 26, 2025 — the 27th in the archive’s UTC clock — I posted this to my @willtygart account, the one I later deleted:

    “The new gold isn’t answering the questions people ask. It’s illuminating the ones they can’t yet vocalize.”

    It went up at 10:24 PM Pacific, two minutes after a sibling post that linked the Native Data essay: “Being the closest store gets you noticed. Speaking the local language gets you chosen.” Two posts, two minutes apart, one night. The Lantern essay names the Oxxo Principle — being the closest store — as the first layer; no Oxxo essay survives in the archive, but the idea lived on as the tagline of the Native Data post. Two essays got their own subdomains: the Native Data Principle and the Lantern Principle. The Lantern one carried the title “The Lantern Principle: The Final Layer of SEO.”

    What happened afterward

    Within days, the Lantern post had become a full essay. The earliest surviving capture is July 30, 2025 — four days after the post — and it’s already complete: the hero, the comparison, the four-step method, the whole thing. So the thinking wasn’t new on the 26th. The post was the tip of something I’d already worked through.

    Here’s what’s worth noticing about that July burst. The two posts that night were one idea unfolding in layers:

    1. The Oxxo Principle — “Being the closest store gets you noticed.” Proximity. Be there.
    2. The Native Data Principle — “Speaking the local language gets you chosen.” Relevance. Speak like the customer.
    3. The Lantern Principle — the final one. Anticipation. Light the path they can’t describe yet.

    Be there. Speak their language. Then — the hardest one — see the problem they can’t articulate and hand them clarity anyway.

    The subdomains are offline now. The essays survive only in the Wayback Machine. That itself is a small footnote about rented space versus owned space, which is a different episode. The point for this one: the idea outlived its hosting. It turned out to be early, not wrong.

    Because look at what the web became. The AI assistant era made the Lantern Principle the default shape of a good answer. When someone asks a chatbot a question now, the good systems don’t just answer — they anticipate. They offer the next step, the related consideration, the thing the user was really getting at. “What is the underlying problem they are trying to solve?” — that’s not a 2025 content strategy anymore. It’s how the good ones behave now. The principle went from marketing theory to product behavior in about a year.

    The piece itself

    Here’s the essay as it ran, cleaned up from the archive — I haven’t rewritten it, just given it the room it was always asking for.

    For decades, we treated content as a reactive tool. A user asks, we answer. Simple transaction. But that model assumes the user knows what to ask. When they don’t — and they often don’t — they get stuck. They bounce. They stay frustrated.

    Consider the difference:

    Answering the question: “How do I change a tire?” → “Here are the 5 steps to change a tire.”

    Illuminating the path: The person’s unspoken reality is “I’m stranded and stressed.” So the answer becomes: the 5 steps, plus safety precautions, plus a link to 24/7 roadside assistance, plus how to check the spare’s pressure. Nobody searched for those extra things. Everybody needed them.

    The greatest opportunity in content isn’t in the keywords people search for. It’s in the needs they can’t yet articulate. The new gold is found in the dark — in the space between a user’s problem and their ability to ask for a solution.

    This is the Lantern Principle: stop being a dictionary, start being a guide. Our job is no longer just to provide answers but to anticipate needs — to create content that doesn’t just solve the stated problem but illuminates the entire context around it, guiding the user to clarity and confidence.

    How to build a lantern

    The shift is from keyword research to empathy mapping. The operative question changes from “What are people searching for?” to “What is the underlying problem they’re trying to solve?” Four moves:

    1. Answer the unasked question. Someone searching “how to write a resume” is really asking “how do I get a better job?” Serve both. Resume templates and the interview tips and the career planning resources. The stated query is the door; the unasked question is the house.
    2. Provide the next step. Never let content be a dead end. Every article should lead naturally to the next logical step in the user’s journey. A product page links to its user manual. A tutorial links to the advanced technique. If you end at the answer, you’ve ended too early.
    3. Simplify the complex. The ultimate act of empathy is taking a complex, intimidating topic and making it simple — analogies, plain language, visuals that actually explain. This is what builds the trust that makes you the go-to source.
    4. Create foundational resources. Build definitive, comprehensive guides — “digital lanterns” — that cover a topic so thoroughly they become the starting point for anyone exploring it. These serve thousands of unasked questions over time. They compound.

    The goal: a web that feels less like a vast, cold library and more like a network of helpful guides, each holding a lantern. An internet that doesn’t wait for the perfect query but proactively offers clarity.

    The future of content isn’t about being found. It’s about shedding light.

    Why this one aged well

    I want to be honest about what this principle got right and what it didn’t.

    What it got right: anticipation is the real moat. Everything I wrote about SEO in 2025 assumed the user arrives with a query and the job is to match it. The Lantern Principle was me noticing, before I had the language for it, that the highest-value content serves the need behind the query — and that AI systems would eventually do this natively. When an assistant now reads between the lines of a question and offers what you actually needed, that’s the Lantern Principle running as software.

    What I understated: how hard anticipation is to fake. A lantern only works if you genuinely understand the person in the dark. The four moves above are easy to write and hard to do — because “answer the unasked question” requires you to actually know people, not just their search terms. Every content farm can optimize for keywords. Very few can hold the lantern, because it requires the one thing that doesn’t scale: empathy for a specific human being stuck on a specific problem.

    That’s also why this principle pairs with the one from Episode 1. In the 23-model experiment, I learned that scope — who the reader is, what they actually need — matters more than the prompt. The Lantern Principle is scope taken to its conclusion: know the reader so well you can answer what they haven’t asked.

    The restoration version

    I run a niche agency for restoration contractors, so let me ground this where it hurts.

    A homeowner never searches “I need emergency water mitigation with proper psychrometric documentation for my insurance claim.” They search “water under sink” or they call because the kitchen smells weird. They are stranded and stressed, and they cannot vocalize the real need: someone who will stop the damage, document it so insurance pays, and explain what’s happening in plain language.

    The restoration company that answers the stated query — “yes, we do water damage” — is the dictionary. The one that anticipates — shows up, explains the process before the adjuster calls, hands the homeowner a clear next step at every stage — is the lantern. Guess which one gets the review, the referral, and the adjuster’s trust.

    That’s not a marketing insight. It’s an operating insight. The companies winning in restoration right now are the ones whose process illuminates the path, not just their website.

    Related from the series

    • Episode 1: We Ran 23 AI Models on the Same Article. The Prompt Was Never the Point. — scope beats the prompt; knowing the reader beats optimizing the query.
    • The Native Data Principle — speaking the local language gets you chosen. The middle layer of the trilogy.
    • The Oxxo Principle — being the closest store gets you noticed. The first layer, named in both essays; no Oxxo essay survives in the archive.
    • Stop Renting Space. Start Owning Your Content. — on why the essay subdomains being offline is a footnote, not a funeral.
  • We Ran 23 AI Models on the Same Article. The Prompt Was Never the Point.

    We Ran 23 AI Models on the Same Article. The Prompt Was Never the Point.

    From the archive

    July 4, 2025 — I posted this on X:

    We tested 23 AI models on the same structured article scope — not just a prompt, but a data-backed framework with embeds, search mapping, and internal RAG.

    Each model got the same Google Doc. Same structure. Same instructions.

    July 5, 2025 — the follow-up, with the writeup:

    We gave the exact same prompt to 23 different AI models. Same input. 23 different outputs. 23 different personalities.

    The takeaway? It’s not just how you prompt — it’s who you’re talking to.

    Fourteen months later, the model names in the results table are history. The finding got more true, not less. Here’s the whole thing, with room to breathe.

    What happened since

    When I ran this test, Claude Sonnet 4 was the new hotness and Grok 3 was still in beta. The industry has turned over since then — the names below belong to mid-2025. Every specific ranking is a fossil, dated July 2025, preserved as-is.

    But the doctrine this experiment produced is now the operating system for everything I build:

    • Model selection beats prompt engineering. The gap between the best and worst model on the same scope was bigger than any prompt trick I knew.
    • Models have personalities. Not metaphorically — operationally. The same way you’d hand a delicate contents job to a different tech than a Category 3 demo.
    • Match the model to the job. Emails, SOPs, longform, code — different work, different worker.

    If you’ve read anything I’ve written about AI costs in 2026, you’ve seen this doctrine wearing different clothes. Model choice is cost choice. The most expensive mistake in AI isn’t a bad prompt — it’s the wrong model doing the wrong job at the wrong price.

    The experiment

    The setup mattered more than the scores. This wasn’t “ask 23 chatbots a question and see who sounds smartest.” Every model got:

    1. The same Google Doc — a structured article scope for “Kitchen Fire Cleanup: Expert Restoration and Prevention Tips,” a real topic from my industry, not a toy prompt.
    2. The same structure and instructions — no per-model tuning, no optimizing for quirks. Deliberately unfair in the fairest possible way.
    3. A data-backed framework — embeds, search mapping, and internal RAG behind the scope, so the test measured how models work with structure, not how they freestyle.

    Why a restoration topic? Because generic benchmarks test generic thinking. I wanted to know which models could handle domain work — regulated language, technical accuracy, a reader who’s trusting you with their home. That’s a harder test than poetry.

    Custom agents ran the harness. The models just had to do the job.

    The results (July 2025 — preserved)

    Same input, 23 different answers — and size wasn’t the differentiator.

    The 5 that stood out

    ModelScoreWhy it won
    Claude Sonnet 4 (Extended)5.0Calm, professional, field-ready tone
    GPT-4.15.0Sharp structure, publishable polish
    Claude 4 Opus (regular)5.0Great flow and clarity
    Claude Sonnet 45.0Excellent default performance
    o4 Mini High Effort5.0Lightweight but surprisingly strong

    These were the ones I’d have trusted, back in July 2025, with full-length articles, client emails, and education pieces. Note the last one: a mini model scored a perfect 5. Size wasn’t the differentiator. Fit was.

    Most improved, second round

    ModelBefore → After
    Claude 3.54.2 → 4.75
    o3 Mini High Effort4.5 → 4.8
    LLaMA 4 Maverick3.5 → 4.6

    Second-round testing with better scope alignment lifted every one of them. The lesson I keep coming back to: even machines do better when they’re understood. The fix usually isn’t a better model — it’s a better briefing.

    The full field

    ModelFinal score
    Claude 3.7 Extended4.9
    Gemini 2.5 Flash4.9
    Gemini 2.5 Pro4.9
    Grok 3 Mini High Effort4.9
    GPT-4o4.85
    GPT o34.85
    Qwen 2.5 72B4.85
    DeepSeek V34.85
    Qwen3 235B4.85
    Grok 3 Beta4.8
    Auto (router)4.8
    GPT-4.1 Mini4.6
    4o Mini4.6
    Mistral Large 24.5
    LLaMA 4 Scout4.1

    Two things worth noticing in the middle of the pack. First, the open models (DeepSeek V3, Qwen) hung with the frontier labs on structured domain work — the gap was narrower than the marketing suggested. Second, the auto-router scored 4.8, within spitting distance of the best hand-picked models. The machines were already learning to choose among themselves.

    The takeaway, then and now

    Then (July 2025): “It’s not just how you prompt — it’s who you’re talking to.” Learn the personalities the way you learn your field crew. Some need bullet points. Some need a whiteboard. Some just need to be trusted to go build.

    Now (September 2026): That sentence became a cost doctrine. Every model has a price per token and a personality per task, and the expensive failure mode is mismatch — a frontier model writing a two-line email, a mini model drafting your scope of work. The experiment’s real output wasn’t a ranking. It was a routing table.

    Here’s the version I’d hand a contractor today:

    1. Run your own version of this test. Not 23 models — three. Your best guess, the cheap one, and the weird one. Same job, same brief. You’ll learn more in an afternoon than in a month of prompt tweaking.
    2. Write down the personalities. Which model do you trust with numbers? With tone? With structure? That’s your routing table. Tape it to the wall.
    3. Re-run it when the generations turn. The names change; the method doesn’t. This is maintenance, not a one-time project.

    And if you ever wonder whether AI is broken or you’re just doing it wrong — remember the test. Same input, 23 different answers.

    It’s not about perfection. It’s about alignment.

    Series notes

    Episode 1 of The Working Years — ideas pulled from the 2022–2025 X archive (@willtygart, account since deleted), given room to breathe. The original posts are quoted verbatim from the archive export. The July 2025 beehiiv writeup “We Ran 23 AI Models on the Same Article Scope” carries the full original tables.

    Next in the series: The Lantern Principle — “the new gold isn’t answering the questions people ask.”

  • Working with the Anthropic API: Console, Models, BYOK & Costs

    Working with the Anthropic API: Console, Models, BYOK & Costs

    Last verified: September 2026. The API is where Claude stops being a chat window and starts being infrastructure. Four deep dives, one hub — the developer console, every model identifier, the subscription-vs-API cost crossover, and the bring-your-own-key strategy that keeps multi-provider stacks from breaking.

    The console: your developer home base

    The Anthropic Console (platform.claude.com) is where the API work actually happens — creating API keys, managing billing, monitoring usage, setting up workspaces, and navigating the developer dashboard. Start here if you haven’t touched the API side yet.

    → Anthropic Console: Developer Quickstart Guide (2026) — API keys, billing, usage monitoring, workspaces.

    The models: every identifier, decoded

    Every current Claude API model string — claude-fable-5, claude-opus-4-8, claude-sonnet-4-6, claude-haiku-4-5 — with context windows, per-token pricing, and when to use each. The one to bookmark; you’ll come back to it every time a new model drops and your code needs the right string.

    → Claude API Models: Complete 2026 Identifier Guide — model strings, context windows, per-token pricing, usage guidance.

    The money question: API vs subscription

    Subscription (Pro/Max) for interactive daily use; API for automation, building, and irregular usage. Here’s the cost crossover — and what the API adds that subscriptions don’t. The honest math on which billing shape fits your workload.

    → Claude API vs Subscription: Which Is Cheaper? (2026) — the cost crossover and what the API adds.

    The multi-provider play: BYOK on OpenRouter

    How to wire bring-your-own-key provider integrations on OpenRouter across dozens of providers without breaking your stack — prioritization, fallback chains, and per-agent configuration. For the builders running more than one model behind their agents.

    → BYOK on OpenRouter: Provider Keys, Prioritization, and Fallback Strategy — provider keys, prioritization, fallback chains.

    Four deep dives, one hub. The console to get set up, the model identifiers to wire it right, the cost math to bill it right, and BYOK when one provider isn’t enough.

  • Claude vs the Field: Benchmarks, Reddit Consensus & Honest Alternatives

    Claude vs the Field: Benchmarks, Reddit Consensus & Honest Alternatives

    Last verified: September 2026. Every other guide on this site assumes you've chosen Claude. This one is for before that — the choosing itself. Benchmarks, crowd consensus, the honest alternatives list, and the one head-to-head that matters most for developers. Four deep dives, one hub.

    The benchmarks: who actually codes best

    A primary-source coding leaderboard for the top models of June 2026 — Claude Fable 5, Claude Opus 4.8, GPT-5.5, and Gemini 3.1 Pro — with price and context alongside the scores. Benchmarks aren't the whole story, but they're the least biased starting point.

    → Claude vs GPT-5 vs Gemini: 2026 Coding Benchmarks — the leaderboard: scores, price, and context.

    The crowd: what Reddit really says

    Benchmarks measure models; Reddit measures living with them. The genuine crowd consensus from r/ClaudeAI, r/ChatGPT, and the comparison threads — on writing, coding, and integrations.

    → Claude vs ChatGPT in 2026: Reddit Community Consensus — writing, coding, integrations, in the community's own words.

    The alternatives: the honest list

    Claude isn't the only answer and sometimes it's the wrong one. The honest comparison of the 2026 alternatives — ChatGPT, Gemini, Perplexity, Grok, Copilot, and others — with pricing, strengths, weaknesses, and which fits which job.

    → Claude AI Alternatives in 2026: ChatGPT, Gemini, Perplexity, and How They Compare — pricing, strengths, weaknesses, best fits.

    The developer's head-to-head: Claude Code vs Codex CLI

    For the terminal crowd, the choice narrows to two: Claude Code vs OpenAI's Codex CLI. A working operator's side-by-side — install commands, models, pricing, config and sandbox behavior — with a clear call on which to pick.

    → Claude Code vs Codex CLI (2026): A Hands-On Head-to-Head — install, models, pricing, sandbox behavior, and the verdict.

    Four deep dives, one hub. The benchmarks for the scores, Reddit for the lived experience, the alternatives for the full field, and Code vs Codex for the developers.