To what extent can non-engineers accomplish things with Claude? New feature Claude for Google…
In October, Claude added the Claude for Google Workspace add-on, which lets you bring up the Claude panel on the right side of Google Docs, Sheets, and Slides, read the current file, and edit it in place; it is in public beta for the paid Pro/Max/Team/Enterprise plans. During the same period, Docs/Slides/Design ended testing on October 8 and became available to all plans, including the free version; the Enterprise plan is enabled by default starting October 15; Dashboards and Motion remain beta features for paid plans or Team/Enterprise.
Body · AI translation
"Business apps are something you ask the experts for." That assumption clearly collapsed in the fall of 2026. This is because the people on the business side who know the requirements best became able to build their own apps and dashboards using Claude. In October, new features were announced one after another, and the range of what you can "build yourself" expanded even further.
In this series, the author—a non-engineer—shows, with steps and screenshots, how she runs her own work using Claude. At the same time, each installment clearly draws the line: "beyond this point, only engineers can be entrusted with it."
We will explain the applied content and the latest updates that could not fit in the book "Claude AI Utilization: The Strongest Textbook," released on Tuesday, October 27. Reading it together with the book will deepen your understanding even further.
In the first installment, we will actually try out "Claude for Google Workspace," a new feature added in October, and think about where that line should be drawn.
1 | People on the business side started building things themselves
The author does not write programs—she is what you would call a non-engineer. Her main job is management support for small and medium-sized enterprises, and she uses AI as a tool to run her own work. These days, she gives instructions to Claude Code (an AI agent for developers) to handle her own work, such as organizing materials, aggregating data, and proofreading manuscripts.
The reason she became able to do this is simple: if she tells the AI in Japanese "what she wants it to do," the AI now builds it for her. The people who know the requirements best are the ones who do that work every day. Until now, this required a back-and-forth: conveying the requirements to an engineer, having them turned into specifications, and checking what was produced. Now, the person who knows the requirements can become the builder directly.
The announcement of Claude's new features in October pushed this trend even further.
Docs/Slides/Design are now available on all plans. The features for creating documents, slides, and designs inside Claude ended their beta on October 8 and became available on all plans, including the free plan (on the Enterprise plan, they are enabled by default starting October 15). On the Japanese-language interface, they are displayed as "Documents," "Slides," and "Design."
Claude for Google Workspace add-on. It displays a Claude panel on the right side of Google Docs, Sheets, and Slides, allowing Claude to read the file currently open and edit it on the spot. It is in public beta on paid plans (Pro/Max/Team/Enterprise).
Dashboards and Motion. Dashboards is a feature that lets you create data visualizations by giving instructions in natural language, and turn them into dashboards that stay updated by connecting to your data infrastructure (beta on paid plans). Motion is a feature for creating explanatory videos that animate text and graphs (beta on Team/Enterprise).
The Workspace add-on in particular is significant for people on the business side. In many workplaces, both sales figures and customer lists are already inside spreadsheets. Being able to bring Claude in there means that instead of "taking the data to the AI," it is "the AI coming to your usual workplace." Let's try it out right away in a hands-on session.
Image 1: The "Artifacts" page in Claude's sidebar. Under "Create new" are listed "Documents," "Slides," "Design," and "Dashboard (beta)."
2 | Let's create a proposal and have it aggregated inside a spreadsheet
What we will make in this installment / Prerequisites / Time required
Prerequisites: A Claude account (Docs/Slides work on the free plan) and a Google account. The Workspace add-on requires a paid plan (the author tried it with the Windows desktop app (Japanese interface) and Chrome).
Time required: 15–20 minutes in total. Waiting for Claude to generate takes about 6 minutes for the proposal and slides, and about 4 minutes for the aggregation (including approval operations).
Data used: All fictional. For the sales table, we will use Table 1 from the article as is.
Step 1: Create a draft proposal in Docs
Open "Artifacts" in Claude's sidebar and select "New" under "Document." A screen opens with chat on the left and the document on the right. You write your instructions in the chat on the left.
Give instructions in the format of "purpose, audience, format." These are the three elements: for what purpose (purpose), for whom (audience), and in what form (format). Just adding these changes the quality of the document you get back.
> Please create a draft sales promotion plan for next term (January–March 2027). > Purpose: Preliminary materials to obtain budget approval at the department heads' meeting > Audience: The sales department head and the accounting department head (who are not familiar with the detailed circumstances on the ground) > Format: One A4 page. Headings should be the five: "Objectives," "Three Initiatives," "Required Budget," "Expected Effects," "Risks" > Premise: A fictional stationery manufacturer. Main products are planners and notebooks. Last year's sales promotion centered on trade shows, and online efforts were weak
Image 2: The new document screen. The above instructions have been pasted into the chat on the left (before sending)
When you send it, the proposal is written into the right side. In the author's environment, it took about 1 minute 40 seconds. Note that even though the document is written in Japanese, sometimes only the explanatory text on the chat side comes back in English. If this bothers you, just add "Please answer in Japanese," and it will respond in Japanese from then on.
Image 3: The generated draft proposal. It contains the five headings
You can edit the finished document on the spot. Give instructions only for the parts you want to change, such as "Of the three initiatives, replace the second one with an online initiative" or "Make the budget breakdown into a table."
Step 2: Turn it into a single slide in Slides and refine it with color scheme instructions
Once the draft is done, pass it to slides in the same chat thread. There is no need to open a separate screen.
> Please turn this proposal into a single slide for explaining it in 2 minutes at the department heads' meeting. Put the objective in one line, line up the three initiatives, and make the budget and effects stand out with just the numbers in large type.
Image 4: A single slide created by asking in the same chat
Once the slide's content is decided, refine its appearance. Again, just give instructions in the slide's chat.
> Please give this slide a calm blue color scheme, reduce the text, and make it more diagram-oriented. Do not include the company logo.
Image 5: The slide after adjusting the color scheme and amount of text
By this point, you have a draft proposal and a single slide. In the author's environment, the waiting time for Claude's generation was about 1 minute 40 seconds for the document, about 2 minutes for the slide, and about 2 minutes to refine the appearance, and even including the time to think up instructions, it took about 10 minutes.
Step 3: Have Claude aggregate data inside a spreadsheet
Next is Google Sheets. First, prepare a fictional sales table. Copy Table 1 as is and paste it starting at A1 of a new spreadsheet.
Table 1: Fictional sales table (April–September 2026)
Date Product Quantity Unit Price Sales
2026/04/03 Planner A 120 1,800 216,000
2026/04/18 Notebook B 300 400 120,000
2026/05/07 Notebook B 450 400 180,000
2026/05/21 Pen C 600 150 90,000
2026/06/02 Planner A 150 1,800 270,000
2026/06/19 Pen C 400 150 60,000
2026/07/08 Notebook B 520 400 208,000
2026/07/23 Planner A 90 1,800 162,000
2026/08/05 Pen C 700 150 105,000
2026/08/20 Notebook B 380 400 152,000
2026/09/04 Planner A 210 1,800 378,000
2026/09/17 Pen C 500 150 75,000
Next, install the add-on. Search for "Claude" in the Google Workspace Marketplace. The name on the Marketplace is simply "Claude" (developer: Anthropic; supports Docs, Sheets, and Slides). Install it.
Image 6: The "Claude" listing page in the Google Workspace Marketplace
Once installed, "Claude" is added to "Extensions" in the spreadsheet's menu bar. Select "Extensions" → "Claude" → "Open Claude" in that order, and a panel called "Claude for Sheets" opens on the right side of the screen. The first time you open it, a few screens appear, including one asking about your role, so just proceed through them. When you write an instruction in the panel, Claude reads the currently open sheet and edits the sheet on the spot.
Image 7: The "Claude for Sheets" panel open on the right side of the spreadsheet, with an instruction entered
Enter the following instruction in the panel. The panel display is in English, so add "Please answer in Japanese" at the end.
> Please create a new sheet called "Summary" that aggregates the sales table in this sheet by month and by product. Also include total rows and columns. Then, add a line chart of monthly sales trends to the "Summary" sheet. Please answer in Japanese.
By default, Claude asks for approval each time before making changes to the sheet. Under "Pending edits," the operations it is about to perform are listed in English, such as "1. Check whether a sheet named 'Summary' exists 2. If not, create a 'Summary' sheet," and three buttons appear: "Deny," "Always allow," and "Allow once."
Here, read the content and press "Allow once." For this aggregation and chart, approval was requested about 8 times.
Image 8: A screen where Claude is requesting approval for changes. Under "Pending edits," the operations it is about to perform are listed, and the Deny / Always allow / Allow once buttons appear
Image 9: The completed "Summary" sheet. A table by month and by product (with total rows and columns) and a line chart, "Monthly Sales Trends"
What you should check here is whether the grand total in the summary table matches the total sales in the original table. Return to the original table and select the sales column (E2:E13); the total appears at the bottom right of the screen (2,016,000 for Table 1). Compare this with the grand total in the summary table. Don't forget to "cross-check against the original" for work you leave to AI.
Image 10: Selecting the sales column in the original table and checking the total of 2,016,000 shown at the bottom right
How to use Design, Dashboards, and Motion
These weren't made into steps this time, but I'll also touch on Design and on Dashboards and Motion, which were announced in the same October.
Design is a feature for creating visuals such as pitch materials, one-pagers, and screen mockups, in a different format from documents and slides. For this article's slides, the color scheme and amount of text were adjusted simply by giving instructions in the slide chat, so I didn't use Design. Think of it as the entry point for when you "want to start from the look."
Dashboards is a feature that connects to data platforms such as BigQuery, Snowflake, and Databricks, or to CRMs like Salesforce, creates dashboards based on natural-language instructions, and updates automatically each time the data is updated. At the point of "connecting to the company's internal data platform," you enter the right-hand column of the line I'll discuss later—that is, the domain where you work together with engineers. It isn't something for business-side people to start alone; it's good to remember as a common language for telling engineers "I want this kind of dashboard."
Image 11: The Dashboards screen (quoted from Anthropic, "Build live dashboards and animate explainers with Claude," claude.com, published October 8, 2026)
Motion is a feature that lets Claude create short explanatory videos that animate text, graphs, and shapes. It's envisioned for uses such as turning quarterly reports or product explanations into 30-second videos. It's available as a beta on the Team/Enterprise plans, so it can't be used on individual plans.
Let's improve it with some polishing
Once you've followed the steps, try adding the following two things.
Add "objections and responses" to the proposal. Return to Docs and instruct: "For this proposal, list three objections the accounting department head is likely to raise, and add a proposed response to each." You can have answers ready before you're asked at the department heads' meeting.
Add a year-on-year comparison to the summary. The summary table I produced in my environment was built with formulas that reference the original sheet (Claude's response included an explanation of this). If you correct the numbers in the original table, they'll be reflected in the summary too, but the months being summarized are fixed to April–September. So, referring to Table 1, I'll create a fictional "Previous Year" sheet covering the same April–September period, and instruct in the panel: "Add a column for the year-on-year comparison to the summary table. Last year's data is in the 'Previous Year' sheet. Please answer in Japanese." Here, try changing the granularity of approvals. If you select "Always allow" on the approval screen, ordinary edits will proceed without confirmation (inserting links or external images, changing sharing settings, and similar actions will still require confirmation). Try this in an environment you can undo, such as a duplicated test file. Until you get used to it, I recommend using "Allow once" to watch step by step and become able to read what's being done before loosening it.
3 | How far may you build things yourself?
Information you must not put in
The sales table this time is fictional. When trying it with a real table, check before pasting that it doesn't contain any "information you must not put in." Columns with customer names, contact-person names, or contact details should be deleted before pasting, or replaced with something like "Company A" or "Contact B."
However, just using a test file doesn't make things safe. Before using it with real business data, check your company's regulations, Claude's contract plan, the data retention period (add-on inputs and outputs are deleted within 30 days), and the connectors you're connected to.
Let's make it a habit to check first so as not to step into the right-hand column of the boundary lines in Table 2 below.
Even so, areas that can only be left to engineers
As "things you can build yourself" expands, it becomes necessary to decide "how far you may build things yourself." The engineers referred to here aren't limited to your company's internal development department. For small and medium businesses, they include the systems companies of business partners; for individuals, they include outside experts. I draw the line as shown in the following table.
Table 2: Things you may build yourself vs. things that should be left to engineers
Things you may build yourself | Things that should be left to engineers
Tools that make your own or a small number of people's work easier | Systems used by many people that stop business if they go down
Things that handle data your organization's rules permit sending to Claude | Things that handle personal information, customer information, or payments
Things that can be returned to manual work if they break | Things that are publicly exposed or connected to core systems
A scale whose contents you yourself can explain | Things that require authentication, permissions, auditing, or legal compliance
What the left column has in common is "you can undo it yourself if it fails." The four points are: only you and a few people use it, it handles only data that may be sent to Claude, it can be returned to manual work if it breaks, and you yourself can explain what it's doing. Within the range where all four are met, it's an area where you can easily start building things yourself, within your organization's rules and your own authority.
Conversely, if even one item in the right column applies, consult an engineer. When personal information or legal compliance is involved, also consult the information systems and legal departments. This line doesn't move no matter how smart AI becomes. That's because the responsibility for security and for systems that many people depend on isn't a technical problem but a problem of organization and contracts.
The proposal and spreadsheet summary I made this time both fall within the left column. I can summarize a fictional sales table by myself and fix it by hand if something's wrong. However, the moment it becomes "everyone in the company looks at this sheet every day" or "sales flow in automatically from the core system," it moves to the right column. If that happens, consult an engineer. The path where an engineer takes over and grows something you built and got working yourself will be written about again in the latter half of this series.
Summary of this time
This time, using Claude's new features announced in October, I tried creating a proposal and summarizing in a spreadsheet, and confirmed the line between the range you may build yourself and the range to leave to engineers.
The "three classifications of information" introduced this time and the patterns for instructing Claude are compiled in Chapters 1 and 2 of the book "Claude AI Utilization: The Strongest Textbook," so please refer to them.