u/qqwwbb

I work on spreadsheet infrastructure, and I’ve been thinking a lot about why agents took off so quickly in programming — but feel much slower to land in spreadsheet-heavy teams.

I don’t think the difference is model capability.

And I don’t think it’s because non-technical teams are resistant to AI.

In fact, when ChatGPT first arrived, teams like finance, HR, sales, operations, and marketing adopted it incredibly fast for writing, summarization, planning, research, and analysis.

The appetite was obviously there.

So why does the “agent era” still feel so much further ahead in programming?

My current belief is: programming already had Git.

Not just Git as a tool, but Git as an operating environment for collaboration between humans and machines.

I work on an open-source spreadsheet project, so I spend a lot of time looking at how companies actually use spreadsheets.

Not toy spreadsheets.

Real operational workbooks:

forecast models, revenue reports, pricing sheets, headcount plans, commission trackers, sales ops systems, finance templates.

These files already contain production logic.

And agents are becoming surprisingly capable at operating them.

They can write formulas.

Update tables.

Transform data.

Build charts.

Automate workflows.

Technically, a lot of the capability is already here.

But the moment agents start touching important spreadsheet logic, trust breaks down.

Because spreadsheets still behave like documents, even when they function like software systems.

In programming, an agent can modify a codebase and humans still remain in control.

You can inspect the diff.

Review the change.

Run tests.

Approve it.

Revert it later.

Trace the history.

That infrastructure changes the emotional experience completely.

Without it, agents feel risky.

With it, they feel usable.

Spreadsheet-heavy teams have the same underlying needs.

If an agent updates a forecast workbook, people still need to understand:

• what changed
• which formulas were affected
• whether calculations refreshed correctly
• whether downstream metrics moved unexpectedly
• whether charts or formatting broke
• who approved the change
• how to restore the previous version

These are fundamentally Git-style questions.

The problem is that spreadsheets contain production logic, but most spreadsheet workflows still lack production-grade collaboration infrastructure.

So my current belief is that spreadsheet agents don’t just need better prompts or larger context windows.

They need a Git-style runtime:

diffs, reviews, approvals, rollback, traceability, and structured collaboration between humans and agents.

That feels like the missing layer.

We’ve been exploring this direction ourselves and released an early runtime for spreadsheet agents today.

Still very early.

Could be wrong.

But I increasingly think agents will only become truly usable in operational workflows once humans can collaborate with them safely — not just prompt them.

Curious how others see this.

If you’ve tried bringing agents into finance, sales ops, HR, planning, or spreadsheet-heavy workflows, what actually blocked adoption?