Gabriel and the Headless 360 Conundrum

Gabriel Marechal

5/7/20262 min read

Gabriel and the Headless 360 Conundrum

My thoughts on Headless 360 as a Salesforce ISV who lives way too close to finance data?

Conceptually, it’s wild in a good way: your Salesforce data, workflows, and business logic become a buffet that AI agents can hit from pretty much anywhere - CLI, MCP tools, chat, you name it - without anyone ever opening a browser. It’s like telling your agents, “Here’s the engine room, try not to blow anything up.”

From a finance and RevOps lens though, that’s where the fun and the fear collide. The same setup that lets an agent spin up a contract, tweak a subscription, or adjust a forecast in real time can also crank existing data issues to eleven if your ARR/MRR logic, billing data, and approvals are already a bit… “interpretive.”

If your revenue truth is split between Salesforce, billing, and the CFO’s secret tab in their spreadsheet, you’re basically giving an over‑eager intern a jetpack.

The things that make me pause:

👉 “Final” numbers that actually live in three different systems plus a mystery Google Sheet.

👉 Finance objects nobody really owns (“Is that the real contract schedule or just the one that feels right?”).

👉 Controls that made sense when only humans clicked buttons, but not when agents can hammer APIs 24/7.

Headless 360 doesn’t magically fix any of that, it just makes it easier for agents to touch everything faster. So if your data model and guardrails are fuzzy, you get fuzzy agents… at scale.

And on the change side: Salesforce has been pushing Lightning for almost a decade, and people are still quietly popping back to Classic when they need to get something done. I doubt “no browser required” suddenly makes everyone chill about agents editing anything that lands in a board deck.

So I’m not in the “this is scary, shut it down” camp. I’m more in the “Nearly Headless Gab” zone: pretty excited about the architecture, but stubbornly attached to boring stuff like clean data, clear ownership, and approvals that don’t live in someone’s memory.

For the folks with their heads still firmly attached, especially CFOs, controllers, and RevOps leads: what would you need in place before you let an AI agent anywhere near numbers that go to your board or auditors?

ForecaaS Software

The Recurring Revenue Specialists for Salesforce

Questions?