Start with the AI tools you already pay for

Last Wednesday, Google rolled out its August set of Workspace features. The one I’d pay attention to is called skills. A team can now save a reusable prompt that carries its own rules, templates and reference files, and anyone on the team can call it with an @mention inside Gmail, Docs, Slides, Drive or Chat.

That sounds small. It means a 40-person company on Google Workspace can write down “how we answer a pricing question” once, attach the price sheet and the tone guide, and have everyone use the same instructions. It needs no new vendor and no new contract.

Before a company shops for another AI tool, I’d have it start with what’s already in the building.

What’s already in your subscription

Here is what the two big office suites have added in the last few months.

On the Google side, the August update also made meeting notes in Meet capture the slides that were presented, filed meeting notes, transcripts and recordings into a single Drive folder automatically, and let Forms build a full quiz from a document. It added admin controls to see and suspend the automated flows people build, plus rules that stop Gemini from reading Drive files with certain labels or content.

On the Microsoft side, on July 1 the company introduced Microsoft 365 Business Standard with Copilot and Business Premium with Copilot, plans for small businesses that put Copilot inside Word, Excel, PowerPoint and Outlook as part of the subscription. Microsoft says Copilot respects the file permissions you already have, connects to more than 1,000 outside apps including Shopify, Xero and Docusign, and lets users pick an OpenAI or Anthropic model for a task.

TimelineAI that arrived inside the office suite

Jul 1Copilot in 365 Business plans
Aug 26Workspace adds team skills
Aug 26Admin controls for Gemini flows

If you’re on either suite, check what your plan includes before you sign anything else. Some features depend on the edition, and Microsoft’s own announcement notes that some capabilities need additional products. The bigger gap, as the numbers below show, is between what people have and what they use.

Access isn’t the problem

Deloitte’s 2026 State of AI in the Enterprise survey of more than 3,000 business and IT leaders found that the share of workers with company-approved AI tools rose from under 40% to nearly 60% in a year. Among those who had access, fewer than 60% used the tools in their daily work, a rate that barely moved from the year before. And 84% of companies had not redesigned any jobs around what AI can do.

By the numbers

84%

of companies had not redesigned jobs around AI, per Deloitte

Source: deloitte.com

That matches what I’d expect. Companies hand out licenses, send a launch email and wait. People try it once to summarize a meeting, get something decent, and go back to how they worked before. Nothing about the job changed, so nothing about the results changed.

Buying a new tool doesn’t fix that. A new tool gets the same launch email and the same drop-off. What fixes it is picking one piece of real work, changing how it gets done, and making the new way the default for the team.

Say you run a 30-person agency on Google Workspace. Every Friday, each account manager spends part of the afternoon writing a status email for each client from the project tracker and the week’s meeting notes. That task is already sitting inside the suite. The tracker is a Sheet, the notes are in Drive, the email goes out through Gmail. A shared skill with the agency’s status template and two of last month’s best emails gets the account managers a draft to edit instead of a blank page. Nobody had to buy anything.

Get one real workflow out of what you have

This is the order I’d follow. It takes a couple of weeks, not a quarter.

Pick work that already lives inside the suite. The tools are strongest on work that happens in email, documents, spreadsheets and meetings. Good first candidates: weekly client status emails built from a project tracker, first drafts of proposals from a template and past examples, meeting notes turned into action items with owners, or answering the same internal questions about policy and pricing.

Write the team’s way of doing it into one shared instruction. In Workspace that’s a skill. If your suite has no equivalent, a shared document the team copies from works too. Include the rules a new hire would need: the template, two good examples, the tone, what never to promise. This is the step most teams skip, and it’s the step that makes the output usable instead of generic.

Give it one owner. One person on the team is responsible for the instruction, collects what goes wrong and fixes it weekly. Without an owner, ten people will write ten versions and none of them will improve.

Time it before and after. Pick five instances of the task this week and time how long they take now. Do the same three weeks after the change. If you can’t show hours saved on one task, you have no case for buying anything bigger.

Set the guardrails your plan already includes. Google now lets admins block Gemini from reading labeled Drive files, and Microsoft says Copilot follows the permissions and sensitivity labels you already have. Use the labels and data rules before you widen access. Payroll folders and HR files don’t need to be readable by every assistant in the company.

FlowOne workflow, using what you own

01Pick a task in email or docs
02Write one shared instruction
03Name an owner
04Time it before and after

The tool is already paid for. The work is in the setup.

When it makes sense to buy something new

The suite tools have real limits, and I’d be the first to say so. Buy or build something separate when:

The work happens mostly outside email and documents, for example inside your help desk, ERP or warehouse system, and the suite’s connectors can’t reach the data you need.
The agent has to take actions in other systems on its own, like issuing refunds or updating inventory, with logs and approvals you control.
The volume is high enough that you need a dedicated system with its own monitoring, like thousands of support tickets a week.
You’ve done the steps above, measured the result, and know exactly which gap the new tool fills.

That last condition is the one that saves money. A company that has run one workflow on its existing tools knows what good output looks like, how much review it needs and what the task is worth. It buys the next tool as an informed customer instead of from a demo.

What to do this week

Ask whoever manages your Google Workspace or Microsoft 365 account to list which AI features your current plan includes, and how many people have used them in the last 30 days.
Pick one recurring task that lives in email, documents or meetings and happens at least weekly.
Time the next five times someone does that task.
Write one shared instruction for it with the template, two good examples and the rules. Name one owner.
Put any new AI tool purchases on hold for three weeks, until you have the before and after numbers on this one task.