Claude Sheets, Meetings, and Whiteboards: A Guide for Your Business

Claude Sheets brings spreadsheet creation and editing into the Claude workspace. Claude Meetings aims to document meetings and retrieve decisions and commitments. Claude Whiteboards lets you organize ideas on a collaborative whiteboard and turn them into working materials.

Anthropic's November 10, 2026, Claude announcement brings these tools closer to everyday work, but there is an important distinction: as of November 11, Anthropic still lists Meetings as “coming soon”. This guide distinguishes what you can try when access is enabled from what you should prepare for later; see the official Anthropic announcement.

1. Before you start: choose a small deliverable

For an initial business AI pilot, avoid bringing in your entire operation. Choose a specific outcome: a monthly sales report, minutes from an internal meeting, or a prioritized list of improvements.

Define who provides the information, who reviews the results, and where the approved version will be stored. Use fictional or anonymized data while you confirm permissions and internal policies.

The announcement also expands work with connected apps and introduces Claude Data, formerly Dashboards, for querying business data sources. That does not mean Sheets automatically updates figures from your CRM. Distinguishing a collaborative spreadsheet from a data integration helps set realistic expectations from the start.

2. Claude Sheets: a sales report by branch

This exercise compares two full months and produces a file that leadership can review. Work on the web or desktop: the documentation limits mobile use to basic viewing.

Step 1. Prepare a copy of your data

Export an authorized file with these columns: date, branch, transaction ID, and net sales amount. Define whether the figures include VAT and how returns or cancellations are recorded. Do not mix currencies or compare a full month against one still in progress without noting it.

Keep the original outside the pilot. Then provide the copy to Claude and ask:

Create a spreadsheet with a tab called Data using this file. Preserve the original records. Check dates, amounts, missing branch values, and possible duplicate transaction IDs. List the anomalies without correcting them or deleting records until I authorize it.

Step 2. Build the monthly comparison

Resolve the anomalies before calculating. If a transaction ID can have multiple line items, do not automatically treat it as a duplicate.

Create a Sales by Branch tab. Use formulas to calculate total net sales for each branch for the two full months in the file, the difference in pesos, and the percentage change: (recent month − previous month) / previous month. If the previous month is zero, display “Not comparable”. Include a grand total calculated from the amounts, not from the average of the percentages.

Step 3. Prepare the executive summary

Add a Summary tab with total sales for both months, the difference in pesos, and the percentage change. Identify the branches with the largest increase and decrease in absolute terms. Link the figures to the previous tabs using formulas. Separate observations from hypotheses: do not attribute changes to campaigns, staffing, or inventory without evidence.

This gives leadership a useful overview without turning a coincidence into a business explanation.

Step 4. Audit before exporting

Explain the report's formulas and the ranges they use. Describe how they handle blank cells, returns, and zero comparison baselines. Identify any manually entered figure that should be calculated. After my review, prepare the Excel export in .xlsx format.

Claude's explanation does not replace human validation. Before using the numbers:

• Compare the grand total against the source system.
• Manually calculate one branch's total and its monthly percentage change.
• Check that the ranges include all records and exclude headers or subtotals.
• Confirm that returns have the correct sign.
• Open the exported file and verify formulas, results, and formatting.

Sheets supports multiple tabs, collaboration, and identifiable changes made by Claude. Its documented limit is 100,000 cells; it does not support pivot tables, macros/VBA, Power Query, or DAX, and it does not pull live data from connected apps. These limits are described in the Claude Sheets help center.

3. Claude Meetings: prepare for your weekly meeting

This workflow depends on Meetings being enabled in your organization. Launch coverage places it in Team and Enterprise, initially for Google Meet, while the official announcement still lists it as coming soon. Do not purchase a plan assuming access is immediate.

Before the meeting, confirm availability with your administrator and agree on what information may be processed. Tell attendees that an AI tool will be taking notes, how those notes will be used, and who will be able to access them.

The announced functionality includes a visible participant and a notice in the chat. That does not replace your company's authorization or advance notice. For calls with external guests, a reported restriction requires administrative permission: do not use it with clients without authorization.

During the meeting, state each commitment clearly: action, owner, and date. When the meeting ends, ask:

Summarize only confirmed commitments. For each one, specify the action, owner, and committed date. If any information is missing, write “To be confirmed”; do not infer it.

Separate decisions, proposals still under consideration, and blockers. Which action items from last week remain unresolved, based on what was mentioned in this meeting?

The meeting coordinator should validate the minutes before sharing them. If you do not have Meetings yet, apply this format to your manual notes now: you will have a defined process ready for rollout.

4. Claude Whiteboards: from ideas to action items

Try a session focused on improving lead follow-up. The goal is not to fill a whiteboard, but to leave with actions the team can carry out.

1. State the problem: “Prospects wait too long between initial contact and receiving a quote”. Avoid including personal data.
2. Capture ideas without prioritizing them yet: simplify requirements, prepare answers to frequently asked questions, or clarify who assigns each opportunity.
3. Ask for grouping: “Organize the ideas by process stage. Preserve the original proposals and flag possible duplicates for the team to review”.
4. Select actions: the team decides which ones to test, considering effort, dependencies, and expected benefit.
5. Request action items: “Turn the selected ideas into a list with an action, proposed owner, proposed date, and completion criteria. Mark owners and dates as pending approval”.

Whiteboards supports collaboration, idea grouping, and turning the results into documents or presentations, according to its official documentation. Combining it with Meetings should wait until both features are available in your account.

Assigning names on a whiteboard is not the same as creating tasks in your management system. Confirm how you will transfer and track approved action items.

5. Choosing a tool: plans and limits

Tool	Best for	Plan and availability as of publication	Main precaution
Claude Sheets	Operational reports and monthly comparisons	Beta in Pro, Max, Ultra, Team, and Enterprise	Validate formulas; basic viewing on mobile
Claude Meetings	Retrieving decisions and commitments from internal meetings	Team and Enterprise according to coverage; Anthropic says “coming soon”	Confirm access and authorization
Claude Whiteboards	Brainstorming and process design	Beta in Pro, Max, Ultra, Team, and Enterprise	Approve proposed owners and dates

Sheets is not the right choice for replacing complex financial models that depend on macros, unsupported tools, or specialized controls. It is also not the same as Claude for Excel or Claude for Google Workspace: these are distinct experiences, even though they belong to the same ecosystem.

Before uploading information, review collaboration permissions, data processing terms, retention, and your organization's policies. Beta features may change.

If you need to connect the results to a CRM or ERP, evaluate an AI integration for your business. To execute subsequent steps, such as creating tasks or requesting approvals, consider an AI process automation project, with defined permissions and review procedures.

6. Checklist to get started this week

• Confirm the plan, actual access, and internal authorization.
• Choose a low-risk report or process.
• Prepare fictional or anonymized data.
• Assign a reviewer.
• Run the prompts and compare the results against the original.
• Record time spent on preparation, corrections, and review.
• Decide whether to repeat, adjust, or stop the pilot.

Claude Sheets can be a good starting point if you begin with a verifiable report, while preparing for Meetings and Whiteboards based on their availability. The useful question is no longer just whether to use AI, but which task it could save you hours on this week without losing control.

Message us on WhatsApp to identify that first process. You can start on the Slashweb contact page and tell us which activity your team currently repeats.