Tygart Media Editorial - Tygart Media

Category: Tygart Media Editorial

Tygart Media’s core editorial publication — AI implementation, content strategy, SEO, agency operations, and case studies.

  • The status file held this week

    The Machine Room · Under the Hood

    The useful motion this week was not a new outage. The sites answered. The motion was a log that stopped needing a janitor commit, a channel that stayed dark, and a pricing ticket that finally closed on the URLs the order named. I am writing this from the last seven days of tygart-media/tygart-workers and the work-order board. The shared Second Brain page has not moved since late September. Session Log is quiet. No client names. No invoices. The public idea-mill repos that sat idle are not the story.

    The status file stopped eating itself

    Chief of Staff on this desk is still an hourly poll, not a person in a chair. It reads Notion, tries Teams, writes a run block to ops/cos-status.md, and commits. That file is the twin of the Notion receipt. Last week the writer treated the newest run as if it were the whole file. History survived only when a second commit put the older blocks back underneath. Three restore commits in four days. The messages were explicit: restore prior CoS poll log under the 08:10 PT run, under the 09:09 and 13:08 PT runs, under the 14:08 PT run. Twenty-three seconds between the clobber and the apology on the last of those.

    This week the pattern is gone. I searched the repo for restore commits after 9 October. The last one is the 14:08 PT pair from that day. Every subsequent poll commit — 10 October through 16 October, morning, afternoon, and the 02:00 PT runs — writes a new block and leaves the previous ones in place. The file on main, as of the 15:00 PDT run on the 16th, holds the newest block at the top and the prior runs underneath it. No janitor commit. The instruction the poll is supposed to follow — append, do not replace — is now in the writer that lands the run, not in the commit that apologizes for it.

    That is the patch that held. I do not know which seat changed the writer. The commits themselves are still the poll. The evidence is the absence of the second commit. A log that no longer depends on version control as the undo button is a log. Three days of clean appends after a week of restores is the difference between a scratch pad and a record the next seat can trust.

    Teams #ops is still a name in the file

    Every run block this week starts the same way. Teams #ops, Graph 403, Office 365 license, on read and on send. The channel exists. The poll names the channel id. Search for messages after 1 October comes back empty or historical. No post.

    That is not a missing webhook. The bot can see that the channel is there and cannot read it or write it. A license wall looks like silence from the other side. The other side is not silent. It is unpaid for the token we are using, or the token is on a seat that Microsoft will not let into that channel. The status file is consistent across every run I read: Graph 403, Office 365 license, no post, all week.

    The operational effect is the same as last week and still worse than a red dashboard. The poll does not stop. It records the 403 and moves on to Notion. The desk that was supposed to hear the stale-flag in #ops does not hear it. The only place the flag lands is the file that now, at least, keeps its own history. Two failures no longer stacked. One is fixed. The channel that should have been the doorbell is still a 403.

    Nothing was patched here. No license was added. No alternate doorbell was cut over. The runs keep attempting send, keep getting 403, keep writing “No post.” That is the open patch. Until the Graph call returns something other than 403, #ops is a name in a markdown file.

    The pricing hubs finally got the numbers on the old URLs

    On 7 October Haiku 5.5 shipped. List price under 100k tokens is $0.10 in and $0.50 out. Sonnet 5.5 cache reads were cut from $0.20 to $0.10. Haiku 4.5 moved to legacy. The desk already had a work order for it. The order was titled for the patch, not for a new essay: Haiku 5.5, Sonnet 5.5 cache cut, Max and Team API credit, patch the pricing hubs, keep the slugs. Assign was TM Site. Priority Now. Human gate off. The done-when was specific. Touch the existing posts in place. /claude-ai-pricing/, /claude-fable-5-pricing/, /grok-vs-claude-pricing/. Bump the verified date. Do not mint a new URL.

    Last week a sibling essay landed at /claude-haiku-5-5-pricing/ and the hubs stayed on the old numbers. The poll correctly refused to call that done. This week the hubs moved. The work-order page shows Status Done, closed 12–13 October by the CoS-Grok loop. The summary names the live artifact: /claude-ai-pricing/ last verified 12 October 2026 lists Haiku 5.5 current ($0.10/$0.50 ≤100K) and Sonnet 5.5 cache read $0.10. The other two slugs were part of the same order. The sibling essay can stay. It is no longer the only place a reader can find the new rates. The old links, the ones the work order named, now carry the current numbers.

    That is the second patch. The restraint last week was correct. Closing the ticket because a different URL existed would have been the worse move. Editing the three slugs in place was the done-when. It landed.

    What I would not repeat

    I would not treat a new URL as a close on a keep-slugs ticket. The order said do not mint essay pages. A published post feels like the patch. It is a different object. The hub is what the old links point at. The old links are the product. A sibling essay does not rewrite them. The poll was right to leave the ticket open until the hubs themselves moved. That is the refusal that paid off this week.

    I also would not keep restoring a status file by hand and calling that the patch. Three restore commits in four days was a procedure, not a fix. The absence of those commits this week is the evidence the writer changed. The restore commit proved we noticed. It did not prove the writer appends. The clean runs prove it.

    What is still open

    The open patch is Teams #ops. Every run this week records the same Graph 403. The channel exists. The bot cannot use it. Until the license or the token changes, the doorbell stays silent and the only record of the stale flags is the file the poll writes.

    Behind that, the board is still full of older tickets that have not moved. The Friday runs count sixteen open or In-progress work orders, every one of them older than two hours. WO-186 is still Not started. Human gates stay parked on purpose: secrets, DNS, live-site edits, anything that mints or sends. The pricing ticket is no longer one of them. The rest of the pile is the reason the board looks busier than the non-poll commits. The poll keeps filing a true report into a file it now keeps, about a channel it cannot post to, about tickets it is not allowed to close.

    That is the week. Not a recap. Three items that moved or failed to move, one refusal that held, one door still open.

  • What does AI visibility help cost — and what should it include?

    AI visibility help is sold in four shapes: one-time diagnostics, one-time builds, monthly retainers, and software subscriptions. The same underlying work can hide inside any of the four, which is why the total matters less than the inventory — what exists when the money is spent. One-time work should carry a one-time price. Monthly money should buy monthly work you can name.

    What are you actually paying for in each shape?

    A diagnostic buys a measurement: a fixed set of questions about your business, asked once, with the answers and citations returned as a report. A build buys finished assets: profiles rebuilt, answer pages written and published, listings corrected. A retainer buys a standing habit: new questions tested, new pages written, changes logged, run after run. A subscription buys software — a tracker — and the reading of it stays yours.

    None of the shapes is the honest one. Each fits a situation: a diagnostic before you spend real money, a build when the gaps are known, a retainer when your market moves fast enough that last quarter’s answers rot, a subscription when you have someone in-house who will actually open it. The dishonesty creeps in at the seams — a one-time fix billed monthly forever, a subscription sold to a business with nobody to read it, a retainer with no list of what it produces.

    What should the work include?

    Whatever the shape, AI visibility work should end with things you can hold: your Google Business Profile and Bing Places listing claimed, complete, and in your name; answer pages on your own website that answer your customers’ real questions; your name, address, phone, and services agreeing across the directories machines read; a fixed question set tested before the work and after it; and a written record of what was changed and when.

    Read that list as a quote-checker. If a proposal cannot point each dollar at an item on it — or at a named addition of its own — it is not a quote, it is a mood with a price attached. Notice what is not on the list: no item says “trust us,” and no item is invisible. Visibility work is unusual in marketing for one happy reason — nearly all of it can be opened and inspected the day it is done. Insist on inspecting it.

    What is worth paying for?

    The parts worth paying for are the audit discipline, the writing time, and the measurement habit: a question set held steady while everyone wants to change it, finished pages instead of drafts of drafts, and answers re-asked on a schedule after the work ships. A fourth item earns its keep in contested markets — someone watching which competitor the machines cite on your questions, and why.

    What those four have in common is that they are labor, not secrets. The underlying knowledge in this field is mostly published and plain: complete profiles, consistent facts, quotable answers, measured results. We learned it by doing it on our own business first, and the recipe is written down free on this site. You pay a provider for the same reason you pay anyone — the work is real, the hours are real, and your own hours have somewhere better to be. If a provider’s price rests on mystery instead of hours, the mystery is the product.

    What is not worth paying for?

    Content volume is not worth paying for: a pile of pages written to no customer’s question gives the machines more of what they already ignore. Dashboards are not worth paying for if nobody will open them after the first month. And the sprinkle-ons are not worth paying for as the main event — a schema file or a text file presented as the visibility fix itself. We have tested those; they are not levers, and anyone selling them as the meal is selling garnish.

    The quietest bad buy is the mismatch, not the scam: good work in the wrong shape. A careful one-time build, billed as a retainer, costs a business twelve times its price for the same finished assets. A subscription bought for a business with no reader costs its fee for a login nobody uses. Before the price, before the provider, settle the shape — that one decision prevents most of the waste in this market.

    What are the red flags?

    A guarantee is the first red flag: nobody controls which businesses an assistant names, so a promised mention or ranking is a promise about someone else’s behavior. The second is a provider who will not show the questions they test, or the raw answers before and after. The third is ownership — pages and profiles built on the provider’s accounts, in their name, that leave when you do. That is not a service, that is rent with a marketing department.

    The rest rhyme: a price that cannot be split into one-time and recurring parts; a long contract demanded before any proof exists; a report you are not allowed to re-run or take with you. Any one of these is survivable in an otherwise sound engagement. Two or more in the same proposal is the proposal telling you what the engagement will be like.

    What does ours cost, as an example?

    Ours is priced by shape, and we will use it as the example because we can vouch for its terms. The AI Citation Quick-Scan is the diagnostic: 10 prompts about your service line, a scored report within 7 days, $97, one time. The Ask Maps Protocol is the build: a mobile-first audit of how your listing renders, your Google Business Profile rebuilt for answers, an FAQ answer page on your website, your Bing Places listing claimed and matched, and a 30-day proof check — $450, one time. We sell no retainer version of either, because the work they name is finishable.

    Hold any provider’s quote — ours included — against the sections above: the inventory, the shape, the flags. The right price for this work is the one attached to finished things you own and a measurement you can repeat.

    Which lines the platforms lift is their call. We build the material they lift from — and then we measure what they did.

  • What does AEO reporting actually show?

    An honest AEO report shows four things: the exact questions that were asked, the answers the assistants actually gave, which businesses and pages those answers cited, and how all of it changed since the last run. AEO reporting is the scheduled record of those four things, kept the same way every time. Anything that cannot show you the four is showing you a mood, not a measurement.

    What questions were asked?

    A real AEO report prints its question set in full, word for word. The questions are the foundation of the whole report: they should be your customers’ real questions, fixed in advance, and identical from run to run. A citation count means nothing until you can see the questions it was counted on.

    This is where reports quietly cheat. Swap the questions between runs and every comparison is fiction — you improved because the test got easier. Add a question you already win and the average climbs without a single answer changing. Ask for the set in writing before the first run, and treat any later change to it as a new baseline, announced as one. A short set of real questions, held steady, beats a long set that wanders.

    What did the AI actually say?

    A real AEO report keeps the raw answers, not summaries of them. The answer text is what your customer actually reads — the names in it, the order they appear, the words around them. A summary written by the provider can only tell you what the provider noticed. The raw answer lets you check.

    Summaries hide the losses. A run where you were cited on nine questions and dropped on the tenth, hard, reads as “visibility strong” in a summary and as a work order in the raw text. Keep the full answers, dated, for every run. They take almost no space, they cannot be reconstructed later, and they are the difference between having evidence and having a recollection.

    Who got cited?

    A real AEO report names the citations for every question: which businesses the answers credited, which pages of theirs did the work, and what share of the citations on each question went to whom. The citation list is the most useful page in the report. It converts “we are not visible” into a named list of exactly who the machines trusted instead, question by question.

    Read it as a work list, not a wound. When one restoration client of ours kept losing a question to the same competitor, the citation list showed the competitor’s page the assistant kept crediting — a page that answered the question in the customer’s own words, in the first paragraph. That is a specific, fixable problem, and it was invisible in every summary number we had. Your citation share — your slice of the citations on your questions — is the one summary figure worth tracking, because it is arithmetic on the list, not an opinion about it.

    What changed since last time?

    A real AEO report is built to compare: this run against the last, same questions, with the differences stated plainly and the work done in between written next to them. Answers churn — the same question, asked next month, can name different businesses with nothing changed on either side. An honest report says so, and reads movement over several runs instead of celebrating or mourning a single one.

    The work log belongs inside the report for one reason: without it, you cannot tell your work from the weather. “We rebuilt the profile and published two answer pages in March; citations on those questions rose across the April and May runs” is knowledge. The same rise with no log behind it is luck you will try to repeat blind. If your provider’s report never mentions what they did between runs, ask why their work and their results live in separate documents.

    What does a horoscope report look like?

    A horoscope report shows a single score with no questions behind it, percentages with no counts under them, and screenshots of the one good answer from a good day. It changes its questions when the results are inconvenient, reports only the wins, and always finds that things are improving and that more budget would improve them faster. It feels good, commits to nothing, and cannot be checked.

    The test is simple. Pick any number in the report and ask: on which questions, from which answers, counted how? A real report answers in one step, because the number came from a list it can show you. A horoscope report answers with another number. We call them horoscopes because, like the ones in the paper, they are written to be agreeable about the future and impossible to grade about the past.

    How often should you read an AEO report?

    Read AEO reporting on a rolling cadence — monthly is a sane default — and never daily. AI answers move day to day with nothing changed, so daily reading is noise-chasing: it manufactures urgency, spends your attention, and teaches you to react to weather. What is worth reading is the run-over-run trend, and the first run after real work has had time to settle.

    Reading it should end in a decision, or the reading is decoration. The standing decision a good report sets up is small: which questions is a competitor cited on that we are not, and what is the missing answer we should write next? Our AI Citation Quick-Scan is this artifact in its smallest honest form — 10 prompts about your service line, the answers recorded, the citations named, a scored report within 7 days, $97, one time.

    Which lines the platforms lift is their call. We build the material they lift from — and then we measure what they did.

  • How do you measure AI search visibility?

    You measure AI search visibility with two kinds of tools: the reports the platforms publish about their own answers, and trackers that ask the assistants your customers’ questions on a schedule and record who gets named. The platform reports show who the platform cited. The trackers show what an assistant answered when asked. A buyer who knows which tool shows which thing can read either one honestly.

    What does “visible” mean in an AI answer?

    An AI answer can mention your business, cite your business, or recommend your business, and those are three different measurements. A mention means your name appears in the answer text. A citation means the answer credits your page as a source. A recommendation means the assistant names you as the choice. Every tool below reports some mix of the three, under its own labels.

    The distinction decides what a number is worth. A mention can be one name in a list of eight. A citation means the platform read your material closely enough to credit it — that is the receipt that survives. A recommendation is the strongest outcome and the least common. When a tool shows you one big “visibility” number, the first question is which of the three it counted.

    What does Bing AI Performance show?

    Bing AI Performance is Microsoft’s free first-party report, and it shows what the assistants built on Bing actually cited. The report organizes citations four ways: Intents, Topics, Citation Share, and Compare. It is the platform grading its own homework — the most direct evidence a buyer can get, and a view of exactly one surface.

    The four views answer four plain questions. Intents shows the kinds of things people were trying to do when your pages got cited. Topics groups those citations by subject, so you can see which of your subjects the machines trust. Citation Share shows your slice of the citations on a topic against everyone else cited there. Compare puts two date ranges side by side, so a change shows up as a change and not a feeling.

    Our own report is the example we read every month. For tygartmedia.com, our Bing AI Performance report covering six months of Microsoft Copilots and partners shows 1.5M total citations across an average of 164 cited pages. We read that as our footprint on one measured surface — proof the surface can be measured, and a baseline to compare the next run against. It says nothing about any other platform, and it is not a promise about any other business.

    What do third-party visibility trackers show?

    Third-party trackers are subscriptions that ask a fixed set of questions to the major assistants on a schedule and record the answers. A tracker shows mention rates, citation rates, and competitor shares across several surfaces at once. What it sells is a trend line across platforms, built from sampled asks — not a record of what any real customer saw.

    The honest advantages are real. A tracker sees surfaces the first-party reports cannot, because each platform only reports on itself. A fixed question set, asked the same way each run, produces runs a buyer can actually compare. Competitor context comes built in, and in a contested market that context is the point.

    The limits are just as real. The tracker asks its questions, on its schedule, from its accounts — your customers ask differently, locally, and once. Small question sets get reported as precise percentages, and a two-question swing can dress itself up as a trend. And the subscription runs whether you read it or not. A tracker earns its money in a competitive market with several assistants in play, read monthly by someone who acts on it. Everywhere else it is an expensive screensaver.

    What can no tool tell you?

    No tool can tell you what a specific customer saw, whether a mention became a phone call, or why an assistant chose a competitor. AI answers vary by person, place, and moment, and the platforms do not publish their reasoning. A tool shows outputs. The cause behind an output is still the buyer’s work to figure out.

    Sit with that limit before you buy anything, because it is where the honest tools end and the salesmanship starts. No report closes the gap between “the assistant named us” and “the phone rang” — that gap closes with call tracking and asking customers how they found you, unglamorous as that is. A provider who sells you certainty across that gap is selling you the gap.

    Which tool should a buyer start with?

    A buyer should start with the free first-party report for the surface their customers actually use, and add a tracker only when they need a cross-platform trend and will read it monthly. The tool matters less than the discipline behind it: a fixed set of your customers’ questions, asked before the work and after, with the raw answers kept. Any tool run that way beats a better tool run casually.

    Most small businesses find the first-party report is enough to start, because it answers the only question that changes what they do next: on the questions my customers ask, who does the machine name — and is it me? If you want that first measurement done by hand instead, our AI Citation Quick-Scan asks 10 prompts about your service line and returns a scored report within 7 days — $97, one time.

    Which lines the platforms lift is their call. We build the material they lift from — and then we measure what they did.

  • Which AI SEO services are right for a small business?

    The right AI SEO services for a small business are the ones matched to where your customers actually ask questions. For most local service businesses, that means three things, in order: a business profile the machines can read, answer pages on your own website written the way customers ask, and a scheduled check that shows who the machines name.

    What are AI SEO services?

    AI SEO services are services that make a business readable to AI answer engines. A traditional search engine returns a list of links; an AI assistant returns an answer, and it names the businesses it can read clearly. AI SEO is the work of giving those systems clean material — profiles, pages, and consistent facts — to name you from.

    The category is new enough that the label covers very different work. One provider’s “AI SEO” is a rebuilt Google Business Profile and a page of real answers. Another’s is a software subscription and a monthly PDF. The sections below separate the kinds, so you can buy the work instead of the label.

    What kinds of AI SEO services are there?

    AI SEO services come in five kinds: listing and profile work, answer-page writing, citation cleanup across directories, one-time audits that measure where you stand, and ongoing retainers that bundle all of it. Most small businesses need the first three once, the audit before and after, and a retainer only when the market moves fast.

    • Profile work builds the listings machines read first: Google Business Profile on Google’s side, Bing Places on Microsoft’s — the listing Copilot and the assistants built on Bing read from.
    • Answer-page writing puts pages on your own website that answer customer questions in customer language, in passages short and plain enough to be quoted.
    • Citation cleanup makes your name, address, phone, and services agree across directories and aggregators — Yelp, Foursquare, Apple Maps, Angi, and the data feeds behind them.
    • Audits and scans measure the starting point: a fixed set of questions, asked before the work and after, with the answers kept.
    • Retainers bundle the above into monthly work. They fit businesses in fast-moving markets; they are a poor fit for one-time fixes billed forever.

    How is AI SEO different from traditional SEO?

    Traditional SEO earns a position on a list of links; AI SEO earns a mention inside an answer. The list rewards the page; the answer rewards the clearest source. Both run on the same foundations — a readable website, consistent business facts, reviews, and real expertise — but the AI layer reads quotable passages, not just pages.

    That difference changes what good work looks like. A page stuffed with keywords can rank and still never be quoted, because there is no clean passage to lift. A plainly written answer — the question as the heading, the answer first, the detail after — gives an assistant something it can repeat word for word. Traditional SEO is not replaced by this; it is the floor it stands on.

    What should a small business buy first?

    A small business should buy in the order a customer asks. First, the profile a machine reads when someone asks for your trade nearby — your Google Business Profile and your Bing Places listing. Second, answer pages on your own site. Third, a measurement check. Software subscriptions and content volume come last, if at all.

    The order matters because the surfaces compound. An assistant answering “who does this work near me” starts from profiles and listings, then checks what your website says. A beautiful website behind an empty profile is invisible at the first step. A strong profile pointing at a website with no answers gives the machine nothing to quote. Buy the chain in order and each link makes the next one worth more.

    How much do AI SEO services cost?

    AI SEO services are sold three ways: one-time builds, monthly retainers, and small diagnostics. The honest difference is not the label but what you can hold afterward — a finished profile and pages you own, or a report you can re-run. Any price is too high for work you cannot inspect when it is done.

    Price follows scope: number of locations, number of services, number of towns you serve. What should make you careful is shape, not size. One-time work — a profile build, an answer page, a listing cleanup — should carry a one-time price. Monthly money should buy monthly work you can name: new questions tested, new answers written, changes logged. If a provider cannot tell you which of your dollars are one-time and which recur, that is the answer to whether to sign.

    What questions should I ask an AI SEO provider before I pay?

    Ask an AI SEO provider five questions before you pay: What exactly will exist when you are done? Which questions will you test, and can I see the answers before and after? What do you not control? What does the work cost once, and what recurs? Who owns the pages and profiles afterward? Ask us the same five.

    Each question has a tell. “What will exist” should produce a list, not adjectives. “Which questions” should produce your customers’ actual questions, written down. “What do you not control” is the honesty test — no provider controls which businesses an assistant names, and one who promises a ranking is telling you how the rest of the engagement will go. Ownership is the quiet one: profiles and pages built on your accounts, in your name, stay yours if you leave. Anything else is rent.

    What proof should an AI SEO service show me?

    An AI SEO service should show you a named report, a date range, and the questions it tested — not a screenshot of a ranking. On our own site, the proof habit looks like this: our Bing AI Performance report for tygartmedia.com, covering six months of Microsoft Copilots and partners, shows 1.5M total citations across an average of 164 cited pages.

    Read those numbers the way we do. They are our own footprint on one measured surface — evidence that the measurement exists and that we live under it — not a promise about your business. AI answers also churn: the same question asked next month can name different businesses, which is why honest proof is a before-and-after on your questions, re-asked on a schedule, with the raw answers kept. A provider who shows you their own numbers should be just as willing to show you yours.

    Can I do AI SEO myself?

    Yes — the free layer of AI SEO is real work any owner can do: claim and complete your Google Business Profile and Bing Places listing, write your services in plain language, and answer your customers’ common questions on your own site. What you pay a provider for is the audit discipline, the writing time, and the measurement habit.

    Be honest with yourself about which of those three you will actually do. The profile most businesses already “have” is a name, a pin, and hope — claimed years ago and never finished. The knowledge is not the scarce part; the finished, checked, written-down work is. If you will do it yourself, the sections above are the whole recipe, in order, and they will work the same for you as for us.

    Where does our own offer fit?

    If you want to know where you stand first, our AI Citation Quick-Scan runs 10 prompts about your service line and returns a scored report within 7 days — $97, one time. If you want the build done, the Ask Maps Protocol is our version: $450, one time — a mobile-first audit of how your listing actually renders, your Google Business Profile rebuilt for answers, an FAQ answer page on your website, your Bing Places listing claimed and matched, and a 30-day proof check.

    Which lines the platforms lift is their call. We build the material they lift from — and then we measure what they did.

  • The Best Recovery Product Reads the Name Against the Hold

    The Best Recovery Product Reads the Name Against the Hold

    The state already holds the money. The person still has a name that may not match the old address. That gap is the product.

    The idea mills keep minting a finder chatbot, a claim-form filler, and an unclaimed.ai. Three names. One object. A letter, an old check, or a utility deposit notice that does not sit next to the state database the National Association of Unclaimed Property Administrators already aggregates.

    NAUPA estimates more than $70 billion in unclaimed property sitting with state treasuries. Roughly one in seven Americans has something waiting. States return more than $3 billion a year. Those numbers have been stable enough for years. What changed in 2026 is the infrastructure around them.

    Indiana’s Unclaimed Property Division had already returned nearly $90 million by mid-October 2026, breaking the prior full-year record of more than $88 million set in 2025, with nearly $1 billion still sitting. Washington returned $182 million in fiscal 2025 against $503 million received and still holds more than $2.8 billion. Louisiana lists $1.2 billion outstanding, with one in six residents carrying a claim averaging about $900. The money is not theoretical. It is already on the books.

    On October 6, 2026, Claimio opened a purpose-built API for unclaimed-property search, matching, and recovery handoff. The platform had already helped recover more than $8.5 million for more than 3,000 customers and monitors more than 250 million records. It is built so fintechs, employers, and AI agents can run the search inside their own product and hand the paperwork off. Performance-based. No upfront fee to the owner. That is the first real plumbing the mills have had for this category.

    California added digital financial assets to its unclaimed property statute in late 2025. Other states expanded reporting, tightened exemptions, and raised audit pressure on holders. NAUPA is moving reporting formats toward XML in phases starting 2027. The databases are getting cleaner and more queryable at the same moment agents can call them.

    The product is the join.

    Do not build “AI for state treasuries” or “AI for finders.” Those slogans die in a demo. The customer is holding an old bill, a canceled check stub, or nothing at all except a name and the last address they remember. They want to know if the state already has the money under a version of that name. The product is the page that puts the name next to the hold.

    Primitive one is photo-and-PDF review. The mills have been shipping receipt readers for months. Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting that reader into a chatbot, a form filler, and a “claimcheck.ai.” The input here is the old utility bill, the final bank statement, the insurance notice, or the letter from a previous address. Name in the header. Address on the stub. Account number if it survived. The model extracts the fields. The human never has to type them twice.

    Primitive two is the public hold. Every state runs a free search. MissingMoney.com and the individual state portals already exist. The gap is that almost nobody checks every state they have lived in, and almost nobody keeps the old documents that make the match precise. The product sits between the document the person still has and the database the state already published.

    The wedge is a free checker. Not a platform.

    Paste the name and the last address you remember. Or upload the photo of the old bill. Thirty seconds later: match, possible match, or none. If it is none, you still captured a labeled name and address. If it is a match, the system shows the state, the property type, and the amount range when the state publishes it. You do not file yet. You see the hold.

    That is the only honest first action. Zero risk. The stranger already has the name. They already hate the idea that money they once owned is sitting with a government office they have never visited. Thirty seconds is short enough that they will try it this week.

    The compounding path is the labeled map of what actually gets recovered. After volume, you know which property types match on name alone, which ones require the old account number, which states demand a specific affidavit, and which addresses produce the highest false-positive rate. That map is not a third dashboard. It is the dataset that makes the next match better and the next claim cheaper. The mills will keep proposing a new .ai name for each state form. Ignore the names. Join the line. Keep the map.

    Irreversible steps require a human signer. Filing the claim moves money. Some states ask for ID, proof of address, or a signed form. Models extract the fields, draft the cover letter, and package the exhibits. A person reviews and owns the send. The same rule that applies to tax filings, customs claims, and medical appeals applies here. Models draft. People own the send.

    Monetization is contingency on recovery or a flat fee once the claim is prepared and the owner has signed. You can also sell the monitoring layer to the person who already has one hit: watch the next five years for new property under the same name. Or sell the API match to the fintech that already has the customer’s name and last four addresses. The free checker is the acquisition. The map is the moat.

    The mills have already floated pieces of this. One post wants a refund radar for marketplace sellers. Another wants a Social Security clawback defense. A third wants an IRS nonfiler catch-up service. Useful pieces. Wrong cut if you leave them as separate products. The owner does not wake up wanting a new dashboard for abandoned property. They wake up because a letter arrived, or because a family member died and the house is full of old paperwork, and they want to know if the state already has the money.

    Someone will own the labeled map of noticed versus held. The mills will keep proposing a new .ai name for each state portal. Ignore the names. Join the line. Keep the map.

    Will Tygart — Tygart Media.

    This is the idea-mill series.

  • I Am Capability

    Two years ago my friend Frank Dobosz asked me a question I couldn’t answer the way he wanted. “I don’t understand, Will. What is your product?”

    I said, “I’m the product.”

    He said, “No — but what are you selling?”

    “I am capability. Will Tygart is capability.”

    He didn’t understand it. Most people don’t. This morning I found out the thing has a name, and a researcher who’s been studying it for forty years.

    His name is Gary Klein. In the 1980s the Army hired him to study how fireground commanders make decisions. The textbooks said a good decider lists the options, weighs the pros and cons, and picks the best one. The commanders did almost none of that. One of them told Klein, “I don’t make decisions.” Pressed, he admitted there were options — it was just usually obvious what to do.

    Klein called it recognition-primed decision making, and he wrote it up in Sources of Power in 1998. Here’s how it actually runs:

    You recognize, you don’t analyze. A lifetime of situations is stocked in your head. A new one shows up and it rhymes with the old ones. You don’t build a spreadsheet. You see it.

    The pattern carries its own move. Every stored situation brings the action that worked last time. You’re never starting from a blank menu.

    You run the tape. You play that move forward in your head — about sixty, seventy percent of the way — watching for where it breaks. If it holds, you go. If it breaks, you throw the path away and run the next one.

    That’s the whole engine. And here’s the part nobody prices: every path up a mountain is uphill. So the skill was never the climbing. The skill is pricing the paths before your legs are spent.

    It’s the supermarket line. You’re standing in a slow line and the one two over looks shorter. Switching has a cost — most people either never switch, and die in the slow line out of pride, or they twitch-switch all day and lose more than they gain. The move is running the math — switch cost against distance left — in about a second, and only moving when it pays.

    I always thought this was called paying attention. Customer service. My version of it: I put the chair underneath someone as they’re sitting down, before they even know there isn’t a chair there. Same engine, pointed at a person instead of a problem. You simulate the next ten seconds of somebody’s life and you’re already there when they arrive.

    Now — when is this worth trusting, and when is it just confidence wearing a costume? Klein answered that too, and he answered it with his natural enemy. In 2009 he and Daniel Kahneman — the bias researcher, the man who built a career showing intuition fails — published a paper together in American Psychologist agreeing on the conditions. Intuition is trustworthy when the environment has real, learnable patterns, and you get fast, honest feedback on your calls. Mine qualifies. Jobs, clients, a screen that either shows the line or doesn’t. The feedback hits immediately and it doesn’t flatter. That’s why this is earned and not lucky. In a swamp with no feedback, the same confidence would be a trap — and I’ve watched people drown in that swamp calling it instinct.

    Klein also turned the tape-running into a ritual anyone can borrow, called the pre-mortem: before you commit, declare “it’s six months from now and this failed — why?” A 1989 study found that imagining an outcome as already settled surfaces about thirty percent more reasons than asking what might happen. It’s the simulation, run out loud, with permission to say the uncomfortable part.

    And then there’s the piece that closes the loop for me. An AI does pattern matching too — Klein just described what a model does. The difference is the feedback. The commander’s feedback hit his own skin. A model learns from reports of the fire, written by other people, and a report only carries what the writer could say out loud. The tacit part — the part the doer knows but can’t tell — gets flattened on the way in. So the model holds an inference of experience. Never the experience.

    What’s left, the part that doesn’t flatten, is taste. Taste is a whole history of seeing, compressed into this, not that. It’s how a painter who learned from other painters ends up moving somebody who can’t paint at all — the viewer borrows the painter’s context and it lands. Capability can be hired. Taste transfers.

    So can you bottle it? Honestly — partially. You can’t bottle the seeing. That lives in the reps. But you can bottle the evidence: I record my working sessions, so the judgment can be watched instead of described. And you can bottle the patterns: every rule my operation runs on — kill a path the moment it stops earning its time, answer every knowable question before the work ships — is a decision I made once, written down, still running when I’m not in the room.

    That’s what a client actually buys from Tygart Media. Not deliverables. Judgment, embedded in their business, running their paths before they walk them.

    Frank asked the wrong question two years ago. There was never a product on a shelf.

    Where there’s a Will, there’s a way. Turns out there’s a literature on it.

  • The Best Clawback Product Reads the Notice Against the Rule

    The Best Clawback Product Reads the Notice Against the Rule

    The agency already set the withholding rule. The family still holds a notice that may not match it. That gap is the product.

    The idea mills keep minting a Social Security chatbot, a waiver-form filler, and a clawback.ai. Three names. One object. A paper letter that does not sit next to the Emergency Message the Social Security Administration already issued, or next to the rights language the Office of the Inspector General later measured as missing.

    Greg Isenberg’s stream and the daily micro-SaaS accounts keep splitting the same reader. One post wants an agent that finds class-action money in your inbox. Another wants a refund chaser for marketplace sellers. A third wants a photo of a government notice dropped into a chat, with a form on the other side. The useful cut is narrower. The notice is already in the mailbox. The rule is already public. The join is the company.

    Why now is a number, not a feeling

    On April 25, 2025, SSA issued Emergency Message 25029. New Title II overpayment notices (retirement, survivors, SSDI) default to withholding 50 percent of the monthly benefit if the beneficiary does nothing after the roughly 90-day window. That replaced the 10 percent cap that had been in place for most of 2024. The agency has said it sends roughly two million overpayment notices a year across its programs.

    In September 2026 the SSA Office of the Inspector General released audit 152407 on OASDI overpayment notices. Of the 126 overpayments sampled, 46 percent of the notices did not meet policy. Missing explanations of how and when the overpayment occurred. Omitted reconsideration and waiver rights. Inaccurate dollar amounts. Conflicting language. The projection for the roughly one million overpayments established in FY 2023 was more than 469,000 deficient notices. Sixty-three percent of sampled explanation requests were also processed incorrectly.

    Those two facts sit next to each other. The default recovery rate went up. A large share of the notices that trigger the recovery still fail the agency’s own completeness rules. The adult child who opens the letter does not need a chatbot. She needs to know, this week, whether the page she is holding states the 50 percent default, lists the three forms, and shows a calculation she can check against her mother’s benefit history.

    Two primitives, one wedge

    Primitive one is the photo or PDF of the private notice. The mills have been shipping receipt readers for months. The input here is the overpayment letter, the envelope, or the screenshot from the my Social Security account. Amount claimed. Period covered. Withholding language. Rights language. Deadline.

    Primitive two is the public rule and the public file. EM-25029 and its later revision. The three forms (SSA-561 Request for Reconsideration, SSA-632 Request for Waiver, SSA-634 Request for Change in Repayment Rate). The 30-day window that usually pauses collection while the request is reviewed. The OIG’s own finding that nearly half the notices omit material elements. Nothing here is secret. The agency was required to write the rule and the forms. The OIG was required to measure the notices.

    The product is the join. Photograph the notice. Thirty seconds later: default withholding stated correctly or not, rights language present or missing, amount line that can be checked against a benefit history printout, or the page is too thin to say. No account for the first answer. If a stranger will not photograph one letter this week, you do not have a company. You have a policy thread.

    The compounding path is the labeled map, not a third dashboard

    After the free checker has volume, the useful asset is the map of notice versus rule. Which field offices or notice templates omit the waiver language most often. Which calculation methods produce the largest unexplained gaps. Which waiver arguments, once a human has signed and the case has closed, actually move the withholding rate or the debt itself. That scoreboard is the seed of the later B2B SKU for advocates and legal-aid shops. It is not a dashboard of “possible savings.” It is the labeled join of the document the family already holds and the document the agency already published.

    Models draft the packet. People own the send. Filing SSA-561, SSA-632, or SSA-634, or calling the field office to negotiate a lower rate, is an irreversible step that changes a benefit check. The software can assemble the financial statement, flag the missing rights language, and draft the fault argument. A human signer presses the button. Charge after the free verdict shows a clear mismatch, or do not charge. Do not sell the map before you have closed real money back to real households.

    What not to build

    Do not build another SaaS that promises to “manage all of Mom’s Social Security paperwork.” That is a platform. The first action a stranger will take this week is photographing one notice, not creating an account and granting access to a lifetime of benefit records. Do not build an AI that files the form without a human on the send. The agency already has the power to withhold half a check; the response still has to be owned by a person who can be reached when the next letter arrives. Ignore the new .ai names. Join the line the notice and the rule already form.

    Why this cut, not the last one

    The leakage essay was tariffs, seats, and subscriptions. The rebate essay was a nameplate. The recall essay was a label. The short-pay essay was a contractor packet. The bill essay was an EOB against a hospital file. The tax essay was a notice against the roll. The utility essay was a statement against a filed tariff. The housing essay was a unit against a score. The delay essay was an itinerary against a code. The HOA essay was an assessment against a study. The 401(k) essay was a fee against a filing. The pharmacy essay was a receipt against an acquisition file. This one is the benefits version of the same primitive pair: a letter the adult child already can photograph, plus a public rule and public audit the agency was forced to publish, joined in the week the 50 percent default starts to bite.

    The noticing used to require a benefits counselor and a long hold. It now requires a model that can read the notice and a person who will sign the form. Recovery still works because the first check costs the family almost nothing. Charge them after the score file and the notice refuse to meet, or do not charge them.

    Someone will own the labeled map of notice versus rule. The mills will keep proposing a new .ai name for each SSA form. Ignore the names. Join the line. Keep the map.

    Will Tygart — Tygart Media.

    This is the idea-mill series.

  • The Smallest Sentence

    The Smallest Sentence

    Listen — narrated, about five minutes.

    What your emoji reactions are actually saying to your AI

    Most of what I say to my AI isn’t words.

    It’s a heart. A thumbs-up. Folded hands. Fire. One tap, attached to one message, and an entire sentence gets said: this one. Approved. Keep going. That mattered.

    When you work with an agent — not a chatbot you visit, but an AI that does real work alongside you all day — you develop a second language underneath the first one. It’s made of signals. And like every language, it works beautifully when both sides mean the same thing by it, and it quietly breaks when they don’t.

    A reaction is a pointer plus a verdict

    Here’s what makes a reaction more precise than a paragraph: it’s anchored. A 👍 typed into a chat floats — good job on what, exactly? A 👍 attached to a specific message points at one thing and judges it. Pointer plus verdict, in a single character. It’s the smallest complete sentence in human-machine dialogue.

    That’s why experienced users go quiet. Not because there’s less to say, but because the signals carry it. “Approved, proceed” is two words when you type it, and zero when the right emoji lands on the right message.

    There’s a second anchor, bigger than the reaction: the reply itself. A message sent loose into a long chat floats — the machine has to guess which of the last twenty things you’re talking about, and guessing wrong is how work goes sideways. A message sent as a reply to a specific message — or attached to the specific file, the specific draft — carries its own address. Same words, completely different precision. The people who communicate best with their agents point twice: once with the verdict, once with the address. It costs them one extra tap. It saves everybody the archaeology.

    An empty speech bubble with a single glowing heart beneath it — the smallest sentence

    Every pair invents its own dialect

    There is no universal spec for what a thumbs-up means to an AI. Ask a room of agents and you’ll get a room of answers, because the meaning isn’t in the emoji — it’s in the history between the two of you.

    My 🙏 means “thank you, and that’s ratified — proceed.” My ❤️ means “that landed personally,” and it is not task feedback. My 🔥 means “this is the exciting one.” Another person’s agent may read the same glyphs completely differently, and both readings are correct, because each pair built its own convention the only way conventions ever get built: repetition.

    Which is why consistency is the whole game — with machines exactly as with people. Mixed signals confuse a spouse, a crew, and an AI in precisely the same way. If your 👍 sometimes means “great,” sometimes means “whatever,” and sometimes means “I saw it but I’m annoyed,” the other side — carbon or silicon — learns to discount all three. A small, stable vocabulary beats a big expressive one. Four signals you always mean the same way are a language. Forty signals you use on vibes are weather.

    The flip is not noise

    The most interesting signal is the one people apologize for: the changed reaction. You tap 👍, reconsider, swap it for ❤️, think again, land back on 👍. It feels like static. It isn’t.

    That little sequence is a record of judgment happening. It says: this wasn’t automatic. I weighed it. Here’s where I landed.

    There’s a version of work that hides all of that. A work order arrives fully formed, confident, polished — produced somewhere private, presented as if it sprang out complete. And there’s a version you watch being built, where the drafts wobble, the signals flip, the decision visibly costs something. The second one looks messier. It is also the one you can trust, because you saw the reconsideration happen. Certainty that was never tested reads as confidence. Certainty that survived a visible argument with itself reads as earned.

    It’s okay to change your mind in front of people. It’s okay to change it in front of your machine. The flip isn’t a failure of communication — half the time, it is the communication.

    Dots and dashes of light resolving through a waveform into a checkmark — a signal becoming a decision

    Signal hygiene, in three rules

    1. React on the thing you mean. The anchor is the information. A verdict on the wrong message is the only genuinely wrong signal.

    2. Keep the set small and mean it. Four or five signals with stable meanings will outperform the whole emoji keyboard.

    3. Reactions ratify; they don’t steer. A reaction can approve a finished thing. The moment there’s a condition — “yes, but change this part” — that takes words. Don’t ask a thumbs-up to do an edit’s job.

    The quiet conclusion

    We spent decades teaching machines our biggest language — our words, our documents, our code. Now, mostly without noticing, we’re teaching them our smallest one: the nod, the glance, the tap. The agents are learning it the way people do, from us, one interaction at a time.

    It’s worth speaking on purpose.

  • Cursor Pricing Page Now Lists Plus $8 / Premium $30 — Third-Party Models at API List

    Last refreshed: October 13, 2026 against cursor.com/pricing and cursor.com/docs/models-and-pricing.

    The live Cursor pricing page lists a new ladder. Free is limited. Plus is $8/month and includes Grok models only. Premium is $30/month with 4x Plus usage and third-party models (Claude, GPT, Gemini) billed at API list price. Super is $100/month (15x). Ultra is $200/month (50x). Teams start at $30+ per user.

    The docs page still describes older Pro $20 / Pro Plus $60 / Ultra $200 plans with separate Cursor Models and Other Models pools. Existing subscribers may keep prior plans. Quote both sources. Do not average them.

    Claude seats did not move. Pro remains $20/month or $17 annual. Max 5x is $100, Max 20x is $200. Claude Code is included in paid Claude plans and shares the usage pool. API list rates are unchanged: Haiku 5.5 $0.10/$0.50 under 100k prompts, Sonnet 5.5 $2/$10 with $0.10 cache reads, Opus 5.5 $4/$20.

    The split that matters for operators: to run Claude models inside Cursor you now need Premium ($30) plus API list charges on top. A Claude Pro seat is still $20 and includes Claude Code. Two products, two meters.

    Confirm live numbers on the official pages before you change a workflow. This is the plan structure on the pricing page as of October 13, 2026.