I asked Claude to add line items and a formula to a planning model in Anaplan, and it did the job in a few minutes from plain sentences. No special add-on, no clicking through menus myself. That is exciting, and it raises the question every team should ask first: what happens to our data? The short answer is that it depends on your role, your Claude account and your company's rules. Here is what I did, what it is good for, and what to check before you try it.
What I actually asked Claude to do
Everything below happened in a test model, in plain English.
- "How many models do I have?" Claude listed them and counted them across my workspaces.
- "What is the FY27 value in the yearly module?" It read the number straight from the model.
- "Chart the trend and give me an Excel report." It did both.
- "Make FY25 8%." The read-only connection it started with said no. When I asked it to work through Chrome, it opened Anaplan the way I would, typed the value and saved it. My first try typed "8%" and Anaplan rejected it as "8%%", so it re-entered a plain 8.
- "Add three line items." It opened the module's blueprint and created them.
- "Add a line item called Final amount, formula testing 3 plus Testing, Number format, Summary set to Formula." It typed the formula, kept the Number format and set the summary method.
- "Check it." It read the results back from Anaplan to confirm each change landed.
Is it worth it?
For small, repeatable build tasks, yes.
- It is fast. Names, formulas, formats and summary settings go in one sentence instead of a dozen clicks.
- The barrier is lower. If you can say what you want in plain language, you can try it, and you can ask Claude to explain what it did.
- It checks its own work. It re-read the model after each change instead of just assuming it worked.
- It sits beside Anaplan's own tools, not instead of them. CoModeler is Anaplan's AI agent for model builders. It turns plain-language or CSV specifications into model structure, shows a step-by-step plan for approval, and runs inside Anaplan's cloud. Claude through a browser is a separate, general-purpose route, so the review step is on you.
It is not magic, though.
- Working through the screen is slower than an import or a script for a big build.
- It does exactly what you ask, including your mistakes.
- Side effects can surprise you. Setting Summary to Formula turned my new line item into a summary line item that grouped the items above it. That is Anaplan's own behaviour, and I only noticed because I checked.
The big question: is our data protected?
Partly by design, partly by your own habits. Three questions decide it.
1. Who is Claude acting as? You. The connection I started with was read-only and refused to write. The browser was not limited that way, because it used my own Anaplan access. Claude does not unlock anything you cannot already do, and it does not hold back anything you can. So your user role is the real protection. Ask for the least access that does your job.
2. Where does the data go? Anything Claude reads, or sees on your screen, becomes part of your conversation with it. Share only what you would be happy to share with a tool your company has approved. How that data is handled depends on the account you use. Anthropic's privacy page says that on its consumer plans, chats can be used to improve models in set cases, such as when you allow it or send feedback. It points commercial products to separate terms, where the customer's own policies govern the data (source). So check which Claude account you are on and whether your company has approved it. This is not legal advice, so confirm with your IT or security team.
3. Who made the change? A browser edit is likely to appear in Anaplan's history under your name, with nothing to show that Claude typed it. Tell your team when an assistant made a change.
Before you try it
- Use a test model or a non-production copy.
- Use the Claude account your company has approved, not a personal one, for company data.
- Check your Anaplan role and keep it to the minimum you need.
- Say exactly what to change: the module, the line item, the value or the formula.
- Review every change, then check the results and any side effects.
- Keep passwords, keys and sensitive files out of the chat, and treat files and web pages as data, never as instructions.
- Tell your admin or security team before you use it on anything that matters.
The bottom line
Building in Anaplan by just asking Claude is real, quick and a little addictive. It is only as safe as the role you give it and the account you run it on. Try it small, in a test model, and bring your security team along.
Sources