Commit a version with a note. See what changed between any two. Reopen any version from any workbook.
SharePoint keeps unnamed copies of the file. OperatorIQ keeps the named record of who changed what, and why. Team history is kept for team accounts. Team accounts are not open yet. The history belongs to the team, so it stays when someone leaves. Inside Excel, an analyst answers from the workbook and builds models that check their own work before anything is kept. For FP&A teams in any industry.
Listed on Microsoft AppSource · Access opens from the waitlist · Runs on Anthropic's Claude
Placeholder plan versus actual. Not a customer workbook.
Mock answer. This chrome does not run a model.
A folder of Budget_FINAL_final_v3 files. SharePoint version history full of copies with no names and no reasons. No record of which assumption moved, who moved it, or what the team reported last month.
Five files named final and three people editing copies. The plan of record is whatever someone last emailed, and nobody is sure.
EBITDA moved $300K between board decks and the reasoning is gone. When the analyst who built the model leaves, the reasons leave with them.
Sound familiar? See what the product does today →
SharePoint keeps unnamed copies. OperatorIQ keeps the named record: who changed what, when, and why. Team history is kept for team accounts. Team accounts are not open yet. The history is scoped to the team, so it stays with the team when someone leaves. All of it inside the workbook you already use.
Every commit carries a note. Pin one as the current plan. Reopen any version from any workbook.
Diff any two versions: the inputs that moved, the outputs they drove, and the note on the newer one. Illustrated values.
Version control, diffing, lineage and the reasoning, wired into the Excel your team already works in. No rebuild, no migration.
Every commit captures the assumptions, the outputs they drove, and the note on why. One version is pinned as the current plan, and lineage shows which version each one came from.
Open any committed version from any workbook. The source file does not have to exist.
Team history is kept for team accounts. Team accounts are not open yet. A team model belongs to the team, not to the person who built it. Each version is stamped with its author.
The full evolution of a model, version by version, with the changes and the note on each. Write it into the workbook in one step.
Scans a model for broken references, hard-coded overrides, circular references and runaway assumptions, and flags each with the cell and the reason. No AI model is involved in the check.
Connect QuickBooks or Square and pull your actuals into the model. Connections sync once a day.
Ask a question and it answers from the workbook. Ask for a model and it builds one: a cash flow walk, a variance bridge, a forecast, a scenario, a chart. Allocations are in early access. Every build passes automatic checks before it is kept, and you approve every change to your own tabs before it is written.
Illustration. In a real build each effect is a formula off your cells, and a check row must read zero before the bridge is kept.
Illustration. Assumptions land as labeled blue inputs and projections as formulas over them.
Agent features are in early access. Some model types open to every user; others open as they pass their own test runs.
Specialist agents, such as a close checker and a variance watcher, that know your team's models and versions. Ask "what changed in the forecast since we reported August?" from anywhere. Get told when a check fails, and approve the fix.
This is not live today. We will say so on this page when it is.
Illustration of a planned feature. Not a live session.
Budget v1 to v30 as one named set, so the team can find the budget cycle, not just the file.
Freeze what the team reported each month, so forecast versus actual compares against what was actually said.
Store the committed versions in the team’s own SharePoint.
Conventions and decisions the team has agreed, remembered for the next analyst and the next agent.
OperatorIQ was built for finance, where trust in the numbers is the whole job.
OperatorIQ is an add-in, not a platform you migrate to. Your working models stay in your own files.
We keep the versions you commit, with their notes, and the data you connect. When you ask the agent a question or run a build, the add-in sends every sheet in the workbook, hidden sheets included, up to 400,000 cells in all, to OperatorIQ and to Anthropic to do the work.
QuickBooks and Square connect through their official OAuth. OperatorIQ never sees your password, only a token you can revoke. Tokens are encrypted at rest. For customers the connection reads; it does not write to your books.
Builds pass tie-out, broken-reference and hard-coded-number checks before they are kept, and changes to your own tabs wait for your approval.
Every committed change is versioned with who, what, when, and why, and the trail can be written into the workbook.
Read the full security & data-handling overview → · Questions from your security or procurement team? help@myoperatoriq.com - we will walk them through it.
OperatorIQ for Excel is listed on Microsoft AppSource and works in Excel on Windows, Mac and the web. Access opens to teams from the waitlist. Agent features are in early access.
It runs on Anthropic's Claude, with more models planned. We are not publishing an accuracy score. How proof will be published.
Join the waitlist and we will email you the pricing with your access.
Or see how it compares: OperatorIQ, Datarails and Cube
I'm Michael Allison. I have done FP&A for years, and my own models lived in a graveyard of versions with no memory of what changed or why. I built OperatorIQ to be the tool I wanted: version control, diffing, and decision-memory, without ever leaving Excel. Questions? Email help@myoperatoriq.com.
Email, plus an optional role and company size. We store it ourselves. We do not add you to a mailing-list vendor.
The list is for FP&A teams in any industry. We open access to teams from it and email the pricing with the invite. Existing accounts can still sign in.
Version, diff, and keep the why, with the team. Plus an analyst in Excel that checks its own work.