Your AI surface area grew.
Choose where it belongs.
More workflows arrived.
So did more checking.
Pick one surface.
Start with the useful part
Get the eight calls from this week.
Read the pair that matters
More workflows. More review burden.
What I read. What you can try. What I left alone.
My goal: save you time, reduce noise, and help you make steady progress.
From Joyce
Read Stories 1 and 2 together
Anthropic released fifteen prebuilt small-business workflows in the same week that Workday research said 37 to 40% of the time AI saves can get spent reviewing, correcting, and verifying its output.
That pairing changed the useful move. You could turn on every new workflow and inherit more work to check, or you could set up one workflow with enough context that the output earned your trust.
Pick one workflow. Load the context. Let it earn your trust before you give it another job.
Read this first
This issue in 30 seconds
Claude packaged fifteen workflows for small businesses.
Canva and Google Workspace were the most relevant connectors for creators and course operators.
Checking AI's work can consume 40% of the time it saves.
Tighter context mattered more than adding another workflow to supervise.
Zoom treated AI-powered solopreneurs as a real category.
Its grant program selected fifty businesses of one from nearly 3,000 applicants.
Saved AI instructions became a cross-tool pattern.
Gemini joined Claude, ChatGPT, and Notion in making repeatable prompts easier to reuse.
ChatGPT showed users which memories shaped an answer.
The practical task was a ten-minute cleanup of stale context.
A lawsuit alleged ChatGPT queries were shared without consent.
It was a complaint rather than a finding, but it made sensitive prompts worth reconsidering.
ChatGPT Pro added a personal-finance preview.
Most readers did not need to connect their bank accounts to a chatbot.
AI moved into more surfaces of everyday business.
The useful question became which access you chose and which access simply accumulated.
Claude arrived with a small-business package built around the tools members already used.
Fifteen workflows, fifteen reusable skills, and connectors for Canva, Google Workspace, QuickBooks, HubSpot, and more.
This was the first Claude package aimed directly at online small businesses instead of enterprise teams. Canva and Google Workspace were the two connectors most likely to earn their keep first for creators and course operators.
What actually changed
- Anthropic launched Claude for Small Business on May 13 as a toggle inside Claude Cowork.
- The package included fifteen workflows for jobs such as marketing campaigns, payroll planning, month-end close, and performance monitoring.
- It also included fifteen reusable skills for cash-flow forecasting, invoice chasing, lead triage, content strategy, and contract review.
- Connectors covered QuickBooks, PayPal, HubSpot, Canva, Docusign, Google Workspace, Microsoft 365, and Slack.
- Anthropic and PayPal also released a free AI fluency course built around a 4D Framework.
Try this: Give one workflow a real job
- Connect either Canva or Google Workspace, whichever already contains the material needed for this week's work.
- Choose one job, such as auditing sixty days of content or preparing three graphics from existing brand assets.
- Give Claude the source files and the definition of a usable result before it starts.
- Review the finished output once and write down what context was missing. Add that context before repeating the workflow.
My take
This was the first time Anthropic packaged Claude for the stage my members actually operate at. Canva and Google Workspace were the two connectors most likely to earn their keep first.
If your business runs on visuals and shared documents, choose one of those connections and one real job. The number of workflows was less important than whether one of them could produce something you trusted.
The verification tax was eating a large share of AI's time savings.
Research put a number on the checking, correcting, and monitoring that can make AI-assisted work feel heavier.
The research gave members evidence for a familiar experience. AI sped up production but introduced a second job: supervising what it produced.
What actually changed
- Workday's 2026 research found that 37 to 40% of the time supposedly saved by AI was spent reviewing, correcting, and verifying its output.
- Employees who closely monitored AI output reported 12% more mental fatigue than people who let it run and audited at the end.
- Advisor Perspectives applied the finding to professional services, where solo and small-team operators absorb the review burden themselves.
- The pattern matched earlier research on the cognitive fatigue created by managing multiple AI systems.
Think about this
- What percentage of your last AI session was spent prompting compared with checking the output?
- Where are you reviewing the same kind of AI work twice because the first result still does not feel trustworthy?
- What context, example, boundary, or source could move that correction upstream?
My take
Putting my clinical hat on, this research was measuring hypervigilance. When you do not trust the output, you watch it more closely, and the watching itself is exhausting.
The extra fatigue was not simply from using AI. It came from not trusting it. The fix started upstream with tighter context, clearer examples, and a defined review point.
Zoom put $150,000 behind AI-powered businesses of one.
The Solopreneur 50 program treated solo, AI-powered businesses as a category worth investing in.
Services and consulting made up a larger share of selected businesses than technology and SaaS. Coaches, consultants, and creators were not an edge case in this group.
What actually changed
- Zoom announced its first Solopreneur 50 on May 4.
- Fifty AI-powered businesses of one were selected from nearly 3,000 US applicants.
- Five winners received $30,000 each, for $150,000 in grants.
- Services and consulting accounted for 20% of selected businesses, while technology and SaaS accounted for 5%.
- Solo-founded startups had grown from 23.7% in 2019 to 36.3% by mid-2025.
Think about this
- What concrete AI workflow and measurable output would you have named in an application?
- Which grant programs or business categories might follow this one over the next year?
My take
This was structural recognition that AI-powered businesses are a real category, not a side project anyone needs to apologize for.
That is why the Lab was built around helping people use these tools for the business they are actually building, not around selling a generic course about AI.
Saved AI instructions were becoming a shared pattern across major tools.
Gemini added Skills to Chrome, joining Claude, ChatGPT, and Notion in making good instructions reusable.
The product names varied, but the pattern stayed the same: write the instruction once, reuse it, and update the context when the result drifts.
What actually changed
- Gemini in Chrome let eligible Google Workspace users save useful prompts and run them with one click across the web.
- Claude, ChatGPT, and Notion already offered their own versions of reusable skills or saved instructions.
- The repeated pattern was save once, run repeatedly, and edit when the work changed.
- Google had not yet specified which Workspace tiers received the feature.
Try this: Save the three instructions you repeat
- Choose the three prompts you typed most often in the prior month.
- Save each one in the reusable-instruction feature available in your primary AI tool.
- Run each saved instruction on real work from that week.
- Delete or combine any saved instruction you have not used in thirty days.
My take
This was a useful sign that context architecture was becoming a product pattern across tools.
Write the best instruction once. Keep the context current. Let the tool name change without rebuilding how you think.
ChatGPT showed users which memories were shaping an answer.
Memory Sources made stale context easier to find, correct, or remove.
If ChatGPT kept referring to an old client, role, or business focus, this was the setting that could explain why.
What actually changed
- Memory improvements rolled out to ChatGPT Plus and Pro users in May 2026.
- Memory Sources showed whether past chats, saved memories, files, or connected Gmail had personalized a response.
- Users could delete or correct outdated memories from the source view.
- The feature worked across the models available on a user's plan.
Try this: Audit what ChatGPT thinks it knows
- Open ChatGPT's Memory settings and remove anything stale.
- Run one prompt you use often and inspect which memory sources shaped the answer.
- Add a boundary for anything that should remain inside one conversation rather than become ongoing context.
- Repeat the audit quarterly, not weekly.
My take
If ChatGPT was where you lived, this audit was worth ten minutes. I had found three pieces of context from a project I closed in February still influencing new outputs.
Correcting the memory once was easier than fighting the same stale assumption every time.
A class action alleged that ChatGPT queries were shared without consent.
The complaint named embedded tracking technology and alleged that query data reached Meta and Google.
This was an allegation rather than a ruling. It still made the handling of sensitive client or business information worth reviewing.
What actually changed
- A California class action was filed against OpenAI in May 2026.
- The complaint alleged that embedded tracking technology shared ChatGPT queries with Meta and Google for advertising purposes.
- OpenAI had not responded when the brief was published, and no hearing date had been set.
- The filing was a complaint, not a finding of fact.
Think about this
- What sensitive information had you placed in ChatGPT during the prior ninety days?
- Would a client, employee, or partner expect that information to remain outside a consumer chatbot?
- Have you reviewed the setting that controls whether chats improve the model?
My take
I was watching this one without changing everything based on an unresolved complaint.
If client information had entered ChatGPT, the time to decide whether that workflow was appropriate was before a ruling, not after one.
ChatGPT Pro users could connect bank accounts. Most readers could ignore it.
A US personal-finance preview connected ChatGPT to bank, brokerage, and credit-card accounts through Plaid.
The feature was limited to a $200-per-month plan at publication. The bigger question was whether a financial dashboard belonged inside a chatbot at all.
What actually changed
- OpenAI launched a Personal Finance preview in ChatGPT on May 15.
- It was available to Pro subscribers in the United States at publication.
- Plaid connected bank, brokerage, and credit-card accounts from more than 12,000 institutions.
- The dashboard summarized spending, subscriptions, portfolio performance, and upcoming payments.
Think about this
- Would this solve a financial job you already had, or would it create another dashboard to monitor?
- Were you comfortable with financial information and prompt history sharing the same work surface?
My take
I wanted to like this, but I was not ready to recommend it. Plaid was familiar infrastructure. The concern was the prompt history and the data flow around it.
If you were not already paying for Pro and did not have a clear job for the connection, there was nothing to do.
AI moved into more layers of everyday business in one week.
Bookkeeping, banking, and communications all gained new AI access points.
This was the pattern underneath the week. AI was no longer only a tool people opened. It was becoming a layer inside the places where the business already happened.
What actually changed
- Claude for Small Business put AI inside bookkeeping, invoicing, payroll, marketing, and design tools.
- ChatGPT Personal Finance put AI inside bank, brokerage, and credit-card accounts.
- The OpenAI complaint raised questions about where chatbot queries might travel.
- The practical pattern was an expanding surface area, each with its own access and review burden.
Try this: Run a surface-area check
- List the places where AI currently touches your business, including email, calendar, design, bookkeeping, banking, and chat tools.
- Mark each one as chosen, inherited, or unclear.
- Choose one unclear surface to investigate before adding anything new.
- For the next tool, ask which part of the business it will enter and whether that is where help is actually needed.
My take
I tried this audit and quickly found more AI surfaces than I could count accurately. That was the lesson.
The audit did not need to be perfect. It needed to interrupt the moment when another tool entered the business because the marketing found me when I was tired.
The useful question was which surfaces I chose, which ones accumulated, and which one I wanted to close.
Joyce's read
The workflow count was not the win
The fifteen new workflows sounded useful until the verification research sat beside them. Every new AI surface can save production time and create another place where someone has to check the result.
The calmer move was to choose one recurring job, give it the context it needed, and decide where the human review belonged before turning on anything else.
One workflow. Better context. One review point.
Let one workflow earn a permanent place in the business. The rest can wait outside.
Put it to work
Tighten one workflow until the checking stops multiplying
Use this whenAI produces a recurring draft or summary for you, but you still rewrite, recheck, or hover over the output every time.
Skip it whenThe workflow contains regulated, highly sensitive, or irreversible decisions that need specialist oversight.
Choose one job
- A weekly newsletter draft
- Client follow-up after a call
- A recurring content batch
- A meeting recap and task list
Done means
One recurring workflow has a reusable context sheet, a visible human review point, and one successful test. Do not add a second workflow until this one reduces the checking it created.
I use AI to help with [recurring job], but I still spend too much time checking the result. Ask me for the five pieces of context, examples, or boundaries that would make the output easier to trust. Do not draft the output yet.
Using my answers, create a reusable context sheet for this job. Include the source material to use, the output format, what good looks like, what to avoid, and the one point where I should review before the work is finished.
For a weekly newsletter: provide two past examples, the audience, the required sections, the voice rules, and the source links. AI prepares the first draft. You review claims and the final call to action once, after the complete draft is ready.
No homework required
Worth knowing, and safe to leave alone
Google I/O was scheduled for May 19.
At publication, Gemini, agent, video, and Workspace announcements were expected. Joyce's instruction was simple: do not watch the keynote. Wait for something useful to become available.
Read the sourceWhat I'm watching
The week expanded the number of places AI could enter a small business. The question to carry forward was not how many connections were possible. It was whether each connection solved a named job and had a clear review boundary.
One question
Which AI surface in your business did you actively choose, and which one simply accumulated?