Get tomorrow's brief in your inbox
Today: Google Gemini now lets you edit documents, spreadsheets, and presentations directly inside chats, reducing the back-and-forth of routine office work. Canva's Brush targets faster design revisions, while Granola adds unlimited Mac dictation across its plans. The practical priority is to test these additions against work you already pay people or software to do.
Gemini brings document editing into the conversation
For a small business, the useful change is the shorter revision loop. You can expand a document into full-screen editing, highlight a passage, and request a targeted change instead of copying text between applications. Google also describes highlighting a table and asking Gemini to turn it into a graph. That makes this worth testing for proposals, internal reports, and presentations where drafting is only the first step.
What to do: Take one nonconfidential document you regularly produce and run it through a complete draft-and-revise cycle. Check facts, calculations, formatting, and the finished file before sharing it. Measure the total time, including corrections, against your normal process. The business opportunity is fewer handoffs and less repetitive editing, not a reason to replace a working document workflow before testing it.
Try it: Duplicate an existing promotional deck, link the design within Canva, and request one clearly bounded change across its pages. Inspect typography, spacing, and brand consistency afterward, particularly because Brand Kit support is described as a future improvement. For businesses producing frequent marketing variations, the opportunity is less repetitive layout work.
What to do: If you manage sensitive infrastructure, ask your IT provider to assess deployment requirements, license terms, security controls, and total operating cost before considering a pilot. Downloadable weights do not mean free operation or straightforward hosting. The business benefit is potential control over deployment and data handling, not an automatic saving for a small IT team.
What to do: If you develop properties or run an AEC practice, request a demonstration using a completed project whose requirements and costs you know. Confirm current pricing and have qualified professionals validate outputs before relying on them. Faster early option comparisons could be useful, but this is not grounds to remove engineering review.
Try it: If you already use Amazon for routine supplies, test a low-risk list update before allowing changes to recurring deliveries. Verify quantities, addresses, and account permissions after any action. The potential value is less purchasing administration, provided voice convenience does not weaken your approval process.
Your smaller-business version: Maintain a shared ledger with each subscription, usage charge, owner, and intended business outcome. Review whether simpler tasks can use cheaper models, and whether fixed-rule automation would do the job more reliably without AI. The payoff is clearer purchasing decisions, not merely lower spending: an inexpensive tool that creates correction work can still be poor value.
What to do: Before an agent can send customer messages, change records, or spend money, ask whether you can reconstruct its tool actions, permissions, and approvals. Start with limited permissions and human sign-off for consequential changes. These are recommended safeguards, not a statement that every business faces a newly established regulatory mandate; the business benefit is easier investigation and recovery when something goes wrong.
What to do: Compare your own search referrals, qualified inquiries, and sales before changing marketing spend. Strengthen permission-based email capture and direct customer relationships where appropriate. Reddit's experience does not prove your traffic will follow, but it illustrates the risk of relying on discovery channels you cannot control.
What to do: If you already use Granola on a Mac, test dictation for email drafts, notes, and prompts before renewing a separate dictation subscription. Compare accuracy, correction time, and handling of sensitive information. Confirm current plan pricing before subscribing; unlimited dictation alone does not establish that access is free.
What to do: If you are commissioning a voice receptionist or support agent, ask your developer which components can be replaced independently and how hosted-service changes would affect you. The opportunity is flexibility across providers, but vendor-neutral commitments should be checked against the architecture and commercial terms you actually buy.
What to do: For business-critical AI workflows, confirm capacity and service expectations with your provider and document a manual fallback. Revenue growth is not a service guarantee.
Test targeted editing instead of requesting another full rewrite. In Gemini's new file editor, highlight one section and try: "Rewrite this section for a first-time customer. Preserve every price, date, and commitment. Flag unclear claims rather than filling in details." Review the result against the original. This is a practical experiment using the reported editing feature, not a guarantee of factual preservation.
Run a 20-minute AI subscription audit. Following Zapier's cost-management approach, list each tool's monthly cost, owner, and last useful output. Pick one overlapping subscription to test for consolidation, but cancel only after confirming the replacement handles the actual work.
The clearest near-term opportunity is inside tools you already use: document editing, design revisions, and dictation. This week, measure complete workflows rather than impressive first drafts, and require stronger controls whenever AI moves from suggesting work to taking action.