Goude Group · Weekly Intelligence

The Briefing.

This week's news: Chase the estimates you already priced, lock your ad accounts before a fake AI tool does it for you, move your custom GPTs before OpenAI switches them off, skip the AI search retainer, and put ChatGPT in Slack instead of buying a seat for everyone.

Read the whole thing in three minutes, or go deeper where it touches your business. We talk about the market here, not about ourselves.

No. 013
October 12, 2026

Every article comes with a working tool. It runs right here in the page, it is free, and we do not need your information to use it. No signup, no download, nothing to fill in first. That holds for every article in every issue, back issues included.

Headline · 5 seconds The brief · under a minute Go deeper · the read, plus a free tool you keep
In this issue

Send it when it hits. Every article here has its own link; the send button next to each one copies it, ready to text or email to the person who needs it. Back issues stay in the archive and their tools keep working, so nothing you forward goes stale.

Open the archive

Want a reminder when the next one is up? Leave an email and we send one note a week. That is the whole program. We will not flood your inbox.

01 / Works nowBrief · 45 sec

Point AI at your unsold estimates first. The money is there.

What moved

On October 5, Dallas startup UpSmith raised a $10 million Series A. Its AI agents chase open estimates, missed calls and lapsed memberships for home-services firms. It says it serves more than 200 operators. Its own numbers: Medley AC in Texas booked $147,000 in new revenue in three months and cut cancellations 25%. In late September, ServiceTitan added a Virtual Agent that texts customers about unsold estimates.

What it changes

Every business that quotes has a pile of estimates nobody chased. The customer asked for a price, went quiet, and your office moved on. That pile is the cheapest revenue you own, because the demand already exists. AI does the dull part: the second text, the third, the answer to the warranty question at 9pm. You are not buying leads. You are collecting on work you already priced.

What not to do

Do not treat UpSmith's $147,000 as your number; it is the vendor's figure for a customer it named in a funding announcement. Do not run two follow-up sequences at once; ServiceTitan warns its new agent and its older Unsold Estimates campaign will double-message the same customer. Do not let AI discount or change scope; price stays with a person. Do not text anyone who never gave you a number for it.

The tape

Mar 3The Federal Reserve publishes key findings from its 2025 Small Business Credit Survey. Just under half of employer firms use AI, and writing or marketing is the top use.
Sep 22The Philadelphia Fed breaks down the survey's AI module of 5,248 firms. Nationally, 46% of firms with employees use AI, and most users report no change in labor costs.
Sep 23ServiceTitan's release notes add a Virtual Agent goal for unsold estimates. It texts the customer, answers questions from the estimate and sends a secure link to approve, in the US and Canada.
Oct 5UpSmith raises a $10 million Series A led by SemperVirens. It claims more than 200 home-services customers and says Medley AC booked $147,000 in new revenue in three months.
NextServiceTitan's version stays in private preview and is not on every account yet. Pull your unsold estimates from the last 90 days this week, before the list goes cold.

The pile you already paid for

An unsold estimate is the cheapest revenue in the building. You already paid for the site visit, the drive and the takeoff. The customer already told you they want the work. What kills the deal is silence on day three and day ten, because your office is busy with today's calls. That is a memory problem, and software never forgets a date. It also never feels awkward sending the third message, which is the one a busy office always skips.

Start with what you already run. ServiceTitan now has the follow-up built in for Core, Pro and Max accounts, in private preview. On Jobber, Housecall Pro or a spreadsheet, a Zapier or Make flow plus ChatGPT or Claude drafts each message from the estimate notes. A person approves the first fifty before anything sends on its own. A dedicated tool like UpSmith works your whole customer history and answers calls, but you pay for another platform and hand it your customer data. Run the cheap version for thirty days, count booked jobs, then decide.

The play

  1. Your office manager, Monday: export every estimate from the last 90 days that did not close. Name, phone, job, amount, date sent.
  2. Sort by dollar value. A person calls the top twenty this week. Everything else goes into the AI sequence.
  3. Paste into ChatGPT or Claude with the list: "Here are my unsold estimates with job notes. Write a day 2, day 7 and day 21 text for each. Under 300 characters, plain words, one question each, no discounts."
  4. On ServiceTitan, ask your rep for the Virtual Agent unsold estimates goal, and switch off the older Unsold Estimates campaign for those business units first.
  5. Everyone else builds it in Zapier or Make: estimate marked unsold, wait two days, ChatGPT drafts the text, a person taps approve, it sends.
  6. Use The Quote Chaser on this page to write the sequence and house rules. Count booked jobs after 30 days.
02 / BewareBrief · 45 sec

Fake AI ad tools beat text codes. Put passkeys on ad accounts.

What moved

On October 6, browser security vendor Island published research on fake AI advertising tools posing as ChatGPT, Gemini, Claude, Perplexity, Manus and Meta's Muse. Each pitch ends in a Connect button. It opens a fake Google sign-in window drawn inside the page, showing accounts.google.com. A live operator then asks for your password and your text or app code. Island's own count: hundreds of victim submissions, still ongoing.

What it changes

Text codes and authenticator codes do not protect you here. The operator types your code into the real Google page while you wait. Targets are whoever runs your ads: you, a media buyer, your agency. Once in, attackers spend on your stored card, add their own admins and demote you. Island says pulling the card takes hours. Getting the account back takes weeks or months, and the ads keep running.

What not to do

Do not click Connect on any AI ad tool that reached you by email, ad or DM. Do not trust a sign-in window because the address bar says google.com; the fake draws its own. Do not share one ad login across your team or agency, because passkeys need one person per login. Do not wait for Google to call you; check your user list yourself this week.

The tape

Feb 4Google Ads introduces multi-party approval: a second admin must approve adding or removing users and changing their roles. Requests nobody approves expire after 20 days.
Sep 8Meta launches Muse, its AI agent, in the US. Within nine days a fake Muse Ads site is live, pitching ad help and ending in a Connect button.
Oct 6Island publishes its report on the fake ChatGPT, Gemini, Claude, Perplexity and Manus ad tools. BleepingComputer and The Hacker News cover it the same day. Island counts hundreds of victim submissions.
Oct 7TechRadar and The Register follow. The advice from Island: treat any AI tool asking to connect an ad account as an access request, and use passkeys or hardware keys.
NextIsland says the campaign is still running across Google, Meta, TikTok and Okta sign-ins. No total of hijacked accounts or losses has been published. Lock your logins before one turns up on your card.

Your code goes straight to them

This is not a fake page that collects a password for later. A person sits on the other end, watching each submission in real time. You type your password, the operator tries it on the real Google page, Google texts you a code, and the fake window asks you for it. Every code you can read, the operator can use. The lure works because AI ad tools are new and owners expect a Connect step. A fake Muse Ads site was live within nine days of Meta launching Muse on September 8.

Move the people who touch your ads onto passkeys. A passkey only answers the real site, so a fake window gets nothing reusable. Google Ads already asks for a passkey on sensitive actions like adding users and changing billing. The trade-off is that shared logins end: every person at your agency needs their own account and their own passkey. Pair it with a second admin. Google Ads multi-party approval makes another admin approve new users, removals and role changes, and unapproved requests expire after 20 days.

The play

  1. You, today: list every login that can touch your Google Ads, Meta and TikTok ad accounts, including your agency's. Shared logins go on the list in red.
  2. Each admin, this week: in Google Account, open Passkeys and security keys and select Create a passkey. Allow a day or two before Google Ads accepts it.
  3. Your office manager: open Admin, then Access and security in Google Ads. Remove any user or pending request nobody can name.
  4. Teach the drag test: before signing in through any pop-up, drag it outside the browser. A real window moves. A fake one stays stuck in the page.
  5. Paste the next AI ad invite into ChatGPT or Claude: "Here is an email inviting me to connect my ad account to an AI tool. List every sign it is phishing, tell me how to find the real company's site without using this email, and name what access Connect would grant."
  6. Use The Lockdown on this page to write your ad account checklist, then send it to everyone who runs your ads.
03 / PriceBrief · 45 sec

OpenAI shuts off custom GPTs December 11. Keep your instructions outside ChatGPT.

What moved

On September 11 OpenAI said it will retire custom GPTs and replace them with plugins. The date is December 11, 2026, on every ChatGPT plan. After that, GPTs and their pages go dark. Enterprise workspaces stop creating new GPTs on October 26, and approved deferrals run to February 11, 2027. A migrate button in My GPTs turns instructions into a skill and knowledge files into reference files.

What it changes

Your seat price does not move. What you get for it does. Custom actions, the part that pushes data into your CRM or calendar, do not transfer. Neither does the model you picked or the people you shared it with. Every migrated plugin starts private. If your intake bot or quote helper runs on a GPT, someone on your team owes it hours before December, or it stops working.

What not to do

Do not wait for the banner; list every GPT your team opens this week, including public ones someone else built. Do not assume a migrated plugin behaves the same; OpenAI itself tells you to retest prompts, file use and output formats. Do not leave your only copy of the instructions inside ChatGPT. Do not pay a developer to rebuild a custom action before you check whether a ready-made app already does the job.

The tape

Sep 11OpenAI announces it will retire custom GPTs in favor of plugins that run across ChatGPT and Codex. Choosing to create a new GPT now offers you a plugin instead.
Sep 22OpenAI's target date for the migration tool and the in-product banner. Its FAQ says availability varies by account and workspace, so check My GPTs yourself instead of waiting for a notice.
Oct 5Trade coverage reports builder pushback: plugins do not replicate a GPT's dedicated environment, and sharing is harder. Custom actions, the chosen model and sharing settings do not carry over to the plugin.
Oct 26Enterprise workspaces lose the ability to create new custom GPTs. Enterprise customers with an approved deferral keep their existing GPTs running until February 11, 2027, two months past everyone else.
Dec 11Custom GPTs retire on every ChatGPT plan and their pages become inaccessible. Past conversations stay readable. Any GPT your team has not migrated and tested by then stops doing its job.

You rent what you build inside

The lesson is bigger than one migration. A custom GPT is instructions, files and a connection, stored on OpenAI's shelf under OpenAI's terms. Three months' notice was all it took to end the format. The instructions are the valuable part, and they are plain text. The custom actions are the fragile part, because rebuilding one can mean a custom MCP server, which is developer work. Public GPTs are the trap nobody counts. If your team leans on one somebody else built, you cannot migrate it. Only the account that created it can.

Do it in two passes. This week, copy every GPT's instructions and knowledge files into a shared folder you own, in Google Drive or SharePoint. That copy also works in Claude Projects or a Gemini Gem, so you stop depending on one vendor's format. Then migrate the GPTs that save real hours and let the rest go. The trade-off is staff time now against a broken tool in December. Migration is one button. Testing is not. Budget an hour or two per GPT, more if it has actions. On Enterprise, building plugins in Work burns credits, per OpenAI's own FAQ.

The play

  1. You, today: open My GPTs on each work account and list every GPT your team uses, who built it and what it does. Include public ones.
  2. Your office manager: copy each GPT's instructions and knowledge files into a shared Google Drive or SharePoint folder by Friday.
  3. Paste into ChatGPT or Claude: "Here are the instructions for a custom GPT my team uses. Rewrite them as a standalone prompt that works in any AI tool, list every outside system it connects to, and flag anything that depends on a custom action."
  4. Whoever built each GPT: publish the latest version, click Migrate to plugin, then run the same five real tasks through old and new and compare.
  5. For any GPT with a custom action, check the ChatGPT app directory, Zapier or Make for a ready-made connection before you pay anyone to rebuild it.
  6. Run The Rebuild Bill on this page to price the migration in staff hours against what you lose each week after December 11.
04 / Skip itBrief · 45 sec

Stop paying for AI search tricks. Google says it is still SEO.

What moved

Google's guide to its AI search features says optimizing for generative AI search "is optimizing for the search experience, and thus still SEO." It says you do not need llms.txt files, special schema or pages chopped into chunks. On August 31, Search Console's report on impressions in AI Overviews and AI Mode reached every website worldwide. It shows impressions only, with no clicks and no queries.

What it changes

The pitch in your inbox sells a separate game: a GEO or AEO retainer, an AI rank tracker, an llms.txt file. Google says its AI answers are rooted in its core ranking systems. A SparkToro and Gumshoe study found ChatGPT and Google's AI gave the same brand list less than once in 100 runs. A dashboard reporting your AI rank is measuring dice rolls. Your money belongs on the basics.

What not to do

Do not sign a monthly GEO retainer that cannot show its math: which prompts, how many runs, which tools. Do not pay anyone to build an llms.txt file for Google; Google Search does not use it. Do not buy mentions on random sites; Google says inauthentic mentions help less than they look. Do not block OAI-SearchBot in robots.txt, or ChatGPT search leaves you out.

The tape

Jan 28SparkToro and Gumshoe publish a test of 2,961 prompts run through ChatGPT, Claude and Google's AI. The same brand list came back less than once in 100 runs, the same order about once in 1,000.
May 15Google publishes its guide to optimizing for generative AI features in Search. It calls AEO and GEO still SEO and says llms.txt, special schema and chunked content are not needed.
Jun 3Google launches generative AI reports in Search Console for a subset of sites, starting in the UK. They show impressions from AI Overviews, AI Mode and Discover, by page, country and date.
Aug 31Google says the reports and the AI opt-out control have rolled out to all websites worldwide. The reports still carry no click data and no query data, and small sites can lack enough impressions to show one.
Sep 24BrightEdge, which sells AI visibility tracking, says by its own count that ChatGPT referral traffic doubled from January to August and sent 95.1 percent of AI referrals in August.
NextExpect more AI search pitches as that traffic grows. Open your free Search Console report and log how new customers found you before you renew or sign anything.

There is no second ranking to buy

Here is what the retainer gets wrong. Google's AI Overviews and AI Mode retrieve pages from its own index using its core ranking systems. The page that ranks for your service in your town is the page the AI answer reads. Chatbots add a second problem. Their brand lists reshuffle on almost every run, so a weekly AI rank moves with nothing you did. The SparkToro team found presence held up better than position: brands that showed up often kept showing up. Exact order did not. A report built on AI rank is noise with a chart on top.

Spend the retainer money on what Google names. Fill out your Google Business Profile completely; Google's guide says it helps your products and services show in AI responses. Write pages only you could write: your prices, your process, your local jobs with photos. Google calls that non-commodity content. Then open the generative AI report in Search Console once a month. The trade-off: it shows impressions, not clicks, and it says nothing about ChatGPT. For ChatGPT, ask every new customer how they found you and log the answer. A tally sheet at the front desk beats a paid dashboard.

The play

  1. You, today: open Search Console, find the generative AI performance report, and write down which pages show impressions in AI Overviews and AI Mode.
  2. Your office manager: fill every field of your Google Business Profile this week. Services, hours, service area, photos. Google names it in its AI search guide.
  3. Your web person: confirm robots.txt allows OAI-SearchBot. OpenAI says sites that block it are left out of ChatGPT search answers.
  4. Paste the agency's proposal into ChatGPT or Claude with: "List every deliverable in this proposal. Mark each one as standard SEO, not needed according to Google's AI search guide, or unclear. Then write the five questions I should ask before signing."
  5. Your front desk: add one intake question, how did you hear about us, with ChatGPT, Google and referral as choices. Count them monthly.
  6. Use The Pitch Reply on this page to answer the next GEO agency email with six questions it has to answer in writing.
05 / Steal thisBrief · 45 sec

Stop buying ChatGPT seats for the whole crew. Tag it in Slack.

What moved

On September 29, at DevDay, OpenAI put @ChatGPT inside Slack and Microsoft Teams. Anyone in an enabled channel, thread or DM mentions it and gets answers, summaries or drafts. OpenAI says teammates can add context and refine results without an individual ChatGPT license. It is available on Business and Enterprise plans. It runs through an account your admin configures, not through each person's own login or files.

What it changes

Your seat math changes. You used to buy a seat for every person who wanted AI. Now one Business workspace can stand up a channel where the field crew, front desk and estimators all ask it for help. The work happens where your team already talks, in the open, where you can read it. The catch is control. Whatever you connect, everyone in that channel can reach.

What not to do

Do not connect your whole Google Drive or SharePoint on day one; the assistant reads through its own account, not the asker's. Do not leave it open in every channel; pick Selected channels only, and know that setting does not block direct messages. Do not add it to channels with guests or Slack Connect clients; replies show to everyone there. Do not let anything it writes reach a customer before a person reads it.

The tape

Sep 29At DevDay, OpenAI launches @ChatGPT in Slack and Microsoft Teams for Business and Enterprise plans. Teammates refine its results in the same thread without needing an individual ChatGPT license.
Sep 29Same day, OpenAI adds support for the proposed MCP Events specification on all plans, so plugins start automations when something happens in a connected app, such as a new task on a project board.
Oct 2Setup guides spell out the order: an admin opens Agents in the ChatGPT admin console, connects Slack or Teams, then adds @ChatGPT to a channel. Without that admin setup, mentioning it does nothing.
Oct 4A review of OpenAI's documentation flags two gaps owners miss: Slack channel restrictions do not block direct messages, and replies in shared threads show to every participant, guests included.
NextOpenAI's help center lists @ChatGPT as available globally to Business and Enterprise users, subject to your organization's settings. Check your admin console for the Agents menu before you plan the rollout.

The connection list is the permission system

Here is the part most owners miss. @ChatGPT does not borrow your login. It runs through an account your admin sets up, with the tools your admin connects. That cuts both ways. It cannot open a file just because you can. It can open anything you connected to it, even for an apprentice who has never seen that folder. OpenAI's own setup docs say the people using the surface reach tools and data that differ from their personal access. Your old folder permissions do not follow it into the channel. The list of connections is the only gate.

Start with one job and one channel. A contractor picks #job-updates: crews post photos and notes, then tag @ChatGPT to draft the customer update. A clinic picks the front desk channel for policy answers. Connect one source through an account that can only view it, like the price sheet or the policy binder, and nothing that sends or edits. Pin a channel brief so every request carries the same rules, tone and blanks. Run it two weeks, then count the drafts your team kept. The trade-off is reach against exposure. Every connection makes it smarter and the channel more sensitive.

The play

  1. You, today: open the ChatGPT admin console, go to Agents, click Add and connect Slack. On Teams, your Microsoft admin installs the app for chosen users or groups.
  2. Your office manager: create one surface, set it to Selected channels only, and add a single internal channel with no guests and no client workspaces.
  3. Connect one source through an account that can only view it: the price sheet, the warranty terms or the policy binder. Nothing that sends email or edits files.
  4. Pin this for the crew: "@ChatGPT, write a customer update from the notes and photos above. Two short paragraphs, plain words, what we did today and what happens next. Put [CHECK] on anything you are unsure of."
  5. Use The Channel Brief on this page to write the pinned rules and starter prompts, and post it before anyone tags the bot.
  6. Friday of week two: count the drafts your team sent with light edits. If most were kept, add a second channel. If not, tighten the brief first.
Next issue

Five more things will move by Monday. We will bring the tools.

The Briefing arrives weekly: what moved, what it changes, what not to do, and a working tool for each. Every issue gives the tools away, free and built for the week they cover. No product tours, no victory laps. If it stops earning the read, unsubscribe.

Back issue

This is back issue No. 013. Every tool in it still runs. Read the current issue · Open the archive

One more thing

If something in here lands on a problem you are already working, and you would rather not work it alone, write to hello@goudegroup.com and tell us what you are exploring. You get a reply from a person, not a sequence.