How to Keep Up With AI in 30 Minutes a Week

Spend the 30 minutes in three fixed blocks: ten minutes scanning the release notes of the AI tools your business runs on, ten minutes on one weekly digest, and ten minutes testing one change on real work. Log each decision in one line. Ignore any headline that doesn't touch a tool, task or cost you actually have.

The routine works because it starts from your business rather than from the news. You'll set up a short list of sources once, then use a filter that throws out most headlines in seconds, a safe way to test a feature, and a log that shows after a quarter whether keeping up has changed anything. If you're starting from zero, work through a 30-day self-study plan first; this routine is for staying current once you know the basics.

Follow me on Instagram@sagnikteaches

Why most AI news doesn't apply to a business your size

Most AI coverage is about model launches, benchmark scores, funding rounds and predictions. None of that changes how a six-person business answers customers or sends invoices next week. What does change it is narrower, and there are only four kinds of change worth your time:

Connect on LinkedInSagnik Bhattacharya

• A feature arriving in a tool you use now, such as a new drafting option in your email or a summary button in your accounting software.
• A price or plan change: a rise at renewal, a feature moving to a higher tier, a new seat minimum.
• A change to how your data is handled: retention periods, training settings, new sharing options that an admin needs to switch off or on.
• A new way to do a task your team does every week, which you can test on real work within days.

Real changes from 2026 show what each kind looks like in practice. Shopify Inbox gained a free AI agent that answers customers by itself on the Basic plan and above, which is a feature arriving in a tool many small shops already run. Microsoft 365 Business Standard went from $12.50 to $14 a user a month at renewals from 1 July, a price change that plenty of owners will first notice as a bigger invoice. OpenAI changed how ChatGPT memory works in June, a data-handling change worth a look from whoever sets up the accounts. And custom GPTs are being retired, with existing ones ceasing to run on 11 December 2026, which is a retirement that breaks a weekly task for anyone who built one. None of these led the general AI news, and every one of them mattered more to a small business than that week's model launch.

Subscribe on YouTube@codingliquids

Everything else is optional reading. The trap with general AI news is that it creates a sense of falling behind, and that feeling tends to end in a new subscription. A good routine should lead to fewer purchases, not more. When you meet an unfamiliar term in release notes, look it up in a plain-English AI glossary rather than following the story it came from.

One-off setup: your feed in about 45 minutes

Do this once. It decides what you read every week, so it's worth getting right.

1. List the AI you use or pay for (10 minutes). Include the chat assistant, your office suite, and any industry software with AI features: your online shop platform, booking system, accounting or email marketing tool. Most small businesses end up with three to six entries.
2. Find each tool's official release notes (15 minutes). Use the table below for the big assistants. For industry software, look under Help, Community or "What's new"; search the vendor's name plus "release notes" or "changelog".
3. Route everything to one place (10 minutes). Create an email folder called "AI updates" with a rule that moves vendor product emails into it, or add the pages to a free feed reader if they offer one. The goal is one place you open on Friday, not six tabs.
4. Choose one general digest (5 minutes). Weekly, not daily; written for people who run businesses, not developers; free to unsubscribe. One is plenty. You can swap it later if it fails the filter.
5. Bookmark the pricing pages of your three biggest AI costs (5 minutes). You'll glance at these once a quarter.

If the Message center digest currently goes to a former admin or an old address, fix that today. It's the one source on this list that carries formal notice of changes, and it's easy to lose track of in a small business where the person who set up Microsoft 365 has moved on.

Here's how that goes wrong, in an illustrative seven-person architecture studio. The office manager who set up Microsoft 365 left in the spring, and her address still received the digest. The notice about Business Standard's price rise went unread, the renewal went through, and the first the partners knew was an invoice $126 a year higher (seven users at an extra $1.50 a month). The amount was small; the lesson was that nobody was reading the one channel that gives formal notice. The fix took four minutes: Message center preferences, Email tab, a shared admin address that forwards to two people.

The 30 minutes, block by block

Put it in the calendar at the same time each week. Friday mornings suit many owners because the Workspace recap is usually out and the week's firefighting is mostly done.

1. Minutes 0 to 10: scan your own tools. Open the "AI updates" folder and each release notes page. Read headlines only, back to last week's date. Mark anything that fits one of the four kinds of change. Don't click through to demos yet.
2. Minutes 10 to 18: read the digest. Apply the filter below to each item. Most will score zero. Stop reading as soon as you reach items you'd score zero out of habit.
3. Minutes 18 to 27: test one thing. Pick the highest-scoring item and try it on a real task, following the method in the next section. One test per week, never two.
4. Minutes 27 to 30: log and share. One line per decision in the change log. If anything changes how the team works, post two sentences in your team chat: what changed and what to do about it.

The two sentences for the team are worth getting right, because they're the only part most staff will see. Compare a vague post with a useful one:

• Before: "FYI, there's a new AI thing in our email, have a play with it."
• After: "From Monday, the draft button in email can write replies to booking confirmations from the thread. Use it for those only, and check the date, time and price before you send."

The second one says which task, what to check and when it starts. Nobody has to ask a follow-up question, and nobody starts using the feature on complaints.

Some weeks nothing passes the filter and you're done in twelve minutes. That isn't the routine failing. It's the routine doing its job, which is to stop you reading things that don't matter.

The three-question filter

Score every item you read. It takes about five seconds once you've done it a few times.

1. Does it touch a tool we use now, or one we're actively choosing?
2. Does it change a task someone here does every week?
3. Does it change what we pay, what data leaves the business,
   or what our contract says?

Two or three yes  = test it or act on it this week
One yes           = log it as "watch" and look again next month
No yes            = ignore it, without guilt

Some quick examples. "New model tops a reasoning benchmark" scores zero unless it's the model inside your assistant and you've hit a limit it fixes. "Email drafting feature reaches business plans" scores two if you use that suite and answer customer email daily. "Assistant changes how long business chats are kept" scores at least one on question three, and data changes deserve a look even with a single yes, because an admin may need to act.

Testing a feature in nine minutes without risk

A test only counts if it uses a real task. Toy examples tell you nothing about whether a feature will save your team time. Follow four rules:

• Use a task you did recently, so you already know what a good result looks like and roughly how long it took.
• Work on a copy: a duplicate spreadsheet, a draft email, a test product listing. Never the live file.
• Time it against how you did it before.
• Decide there and then: adopt, watch or drop. "Interesting, I'll look again" becomes a pile of half-tried features.

For assistant features, this prompt gives you a fair comparison:

I'm testing a new feature: [name of feature].
Here is a task I did last week, and the result I produced:
[paste the original task and your result]

Do the same task using this feature. Then list:
- anything you were unsure about or had to guess
- anything in my version that yours left out

An illustrative independent bookshop used that prompt to test an AI feature in its spreadsheet tool. Last week the owner spent 20 minutes listing the 20 slowest-selling titles from the stock export, leaving out anything received in the past 30 days. The assistant's reply ended with these two lists (illustrative):

Unsure about / had to guess:
- "Slowest-selling" could mean fewest units sold or longest
  since the last sale. I used fewest units in 90 days.
- 14 titles have no "date received". I treated them as old stock.

Left out compared with your version:
- You excluded titles received in the last 30 days. I didn't,
  so 6 new arrivals appear in my list.

That is a useful result, not a failure. The owner adds one line to the request ("exclude anything received in the last 30 days; treat a missing date as new stock") and runs it again: 18 of the 20 titles now match, and the whole thing took four minutes. Decision: adopt for the monthly returns list, check the two that differ by hand. The "had to guess" list is the part to read first, because it tells you which of your own rules you never wrote down.

If the feature doesn't appear on your account yet, that's normal. New features often reach business plans in stages, and some need an admin to switch them on. Log it as "watch" and move on rather than hunting through settings for ten minutes.

A worked week: the coffee roaster's Friday half hour

Here's an illustrative example. Say a specialty coffee roaster has seven staff, sells wholesale to cafés and runs an online subscription shop. The owner uses a business office suite with built-in AI, pays for one chat assistant seat, and runs the shop on a hosted e-commerce platform.

• Minutes 0 to 10. The office suite's weekly recap lists a new option for drafting email replies from earlier threads, available on their plan. Filter score: three (tool they pay for, weekly task, and the admin needs to check it's on). The e-commerce platform's changelog mentions AI product descriptions on a higher plan. Score: one. Logged as "watch" until the price difference is known.
• Minutes 10 to 18. The digest leads with a video-generation model and a funding round. Both score zero. One item about a change to data retention on business chat plans scores one; the owner checks their assistant's release notes and finds it doesn't apply to their plan.
• Minutes 18 to 27. The owner tests the drafting option on five real wholesale emails from the week: re-orders, a delivery-day change, a question about a new single-origin. Two drafts are usable as written, three need a line changed. Answering took about three minutes per email before and about a minute and a half with the drafts.
• Minutes 27 to 30. Decision: adopt for wholesale email. With roughly 40 of those emails a week, that's about an hour saved. Posted to the team: "Wholesale replies: try the new draft button, always check prices and delivery days before sending."

Over a quarter of this, the owner spends about six and a half hours in total, adopts three changes, keeps two items on watch, and cancels one duplicate subscription the scan made obvious. That's the kind of result the routine should produce: a few small, tested changes and one fewer bill, not a stack of new tools.

Copy this change log

Keep it in a shared spreadsheet so anyone can see what was decided and why. The "result after two weeks" column is what makes the log useful; fill it in during the following sessions.

Date     | Source           | Change                        | Score | Decision | Owner | Result after 2 weeks
---------|------------------|-------------------------------|-------|----------|-------|---------------------------
[date]   | Suite recap      | Reply drafting from threads   | 3     | Adopt    | Owner | ~1 hr/week saved on wholesale
[date]   | Shop changelog   | AI product descriptions       | 1     | Watch    | Owner | Price still unclear
[date]   | Digest           | New video model               | 0     | Ignore   | -     | -

When a test turns into a prompt the team reuses, move it into your shared prompt library so the gain spreads beyond the person who ran the test.

What to leave out on purpose

• Benchmark leaderboards. They measure models on tests, not your tasks. Your nine-minute test on real work tells you more.
• Launch livestreams and demo videos. Demos show the best case. Wait for the release notes, which say which plans actually get the feature.
• "This changes everything" and "X is dead" posts. They score zero on all three questions by design.
• Prompt "hack" threads. Most are tricks for one model version that stop working after the next update.
• Funding and valuation news. Irrelevant unless a vendor you depend on is being bought, in which case their email to customers will tell you.
• Tools you don't use. Unless you're actively choosing between them, a feature in a competitor's product is not your concern this week.

The quarterly check that keeps the routine honest

Every thirteenth week, replace the normal half hour with a review. Count what you adopted, watched and ignored. Look again at every "watch" item: act on it or delete it. Open the pricing pages you bookmarked and note any change. Drop any source that produced nothing in three months. This is also a good moment to run a keep, fix or cancel review on any tool you adopted, and to check your AI subscriptions for wasted spend.

Custom GPTs are a good test of whether the "watch" column works. For an illustrative physiotherapy clinic whose receptionist uses a custom GPT to draft appointment letters, OpenAI's retirement notice scores three on the filter: a tool in use, a weekly task, and a change to what the clinic relies on. The log entry reads "Custom GPT retiring 11 Dec 2026, move letter instructions and files into a ChatGPT Project (or use OpenAI's migration, which turns a GPT into a plugin); owner: receptionist; by 30 Nov". If that item had sat on "watch" until the next quarterly check, the letters would have been one missed review away from stopping.

Watch for signs the routine has drifted:

• Sessions regularly run past 30 minutes. You're following too many sources; cut the digest first.
• You buy tools after reading about them rather than after testing them. Go back to one test per week.
• The log has been empty for four weeks. Either your sources have gone quiet or you've stopped scoring honestly; check that vendor emails still reach the folder.
• The team hears about changes late or not at all. The two-line summary has been skipped; make it part of the 30 minutes, not an extra.

In a team, the person who runs this doesn't have to be the owner. Handing it to an AI champion works well, as long as they have admin access to the tools and a direct line to whoever approves spending.

Questions about the weekly AI half hour

Should I pay for an AI newsletter or course to keep up?

Not to start with. The free release notes for the tools you use every week cover most of what changes your work. Add one general newsletter only if it passes the three-question filter for a month; if you skip most issues, unsubscribe. Paid material earns its place when it teaches a skill you will use weekly, not when it summarises launches you could read for free.

What if something important happens and I miss it?

Changes that affect you directly, such as a price rise, new data terms or a retired feature, normally reach the account owner by email as well as appearing in release notes. Make sure billing and admin emails land in a folder you actually read. The quarterly check in this routine then catches anything the weekly scan missed, so a single skipped week costs very little.

Who should run this in a team of five to fifteen people?

One person, ideally whoever already looks after your software or acts as your AI champion. They run the half hour and post a two-line summary to the team. Everyone else needs to hear about changes to the tools they use, not follow the news themselves. Rotate the job every six months so the knowledge doesn't sit with one person who might leave.

Is 30 minutes a week really enough?

For a small business, yes, because the routine only tracks the handful of tools you use and the tasks you do. Most weeks nothing passes the filter and the session ends early. If you regularly overrun, you're either following too many sources or testing too much at once. Cut the digest first, then limit yourself to one test per week.

Further reads

• Your Software Raised Its Price for AI: Keep, Downgrade or Switch? — What to do when a tool you use raises its price for AI features.
• What to Check in an AI Tool's Privacy Policy and Terms — How to read the data terms that the filter flags as changed.
• Why AI Gives Different Answers Each Time, and How to Fix It — Explains why a feature that worked in your test can behave differently later.
• AI Literacy Requirements: What Your Staff Need to Know — What your team should know, beyond hearing about new features.
• AI Adoption Stages: Where Is Your Business Now, and What's Next? — Place your business on the adoption path so you know which news matters now.
• How to Give AI Your Business Context So Answers Fit — Make every feature you test give answers that fit your business.
• How Much Time Can AI Save a Solo Consultant Each Week? — A task-by-task estimate of the hours AI saves a one-person consultancy, three example weeks, the hidden costs and a two-week way to measure yours.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: OpenAI help site, ChatGPT and ChatGPT Business release notes; Anthropic, Claude apps release notes; Microsoft Learn, release notes for Microsoft 365 Copilot and Message center documentation; Google Workspace Updates weekly recaps. All checked September 2026.