"We've been using Salesforce 'headless' for almost a year. And we basically never log in at all. The biggest advantage? We can connect to 30+ other systems, all together. And build our own agents easily on top of our Salesforce data, too."

how much do you pay salesforce for the privilege of not using their software? we vibe-coded a replacement for hubspot in 2 weeks and it's already way better

Curious How much of salesforce code do you really need to perform your daily actions? What is the case for abstracting your workflows into your own flows sans SFDC?

makes sense tbh. if your own agents sit on the data anyway the ui is just one more client. would be curious how clean the data stays with 30 systems writing into it

a year headless is a long time. what broke first

We use hubspot- and the same for us. I wonder how per seat pricing will change for those who don’t need crm’s agents and do their own pull of data. Questions for you all- Since salesforce target market is big enterprise companies who pay for all the compliance that sf helps them with and “safety”- do you see big companies moving to the headless way you all are talking about or do you think they will be sticking with agents that sf released last month?

Yeah I don’t think big enterprises will run “headless” the way we do BUT it may well be that teams run their own headless instances that work better for them Salesforce also is launched a more formal headless 360 which will be better architected for larger enterprises

Headless for a year, nobody logs in, 30+ systems wired in. So the seats are the next line item to cut. If agents read it over MCP and no human opens the UI, you're paying per-seat for a database. At renewal I'd push per-API-call pricing or walk. The UI was the moat.

More here:

the one screen id still want is "what did the agents change, and can i undo it?" especially once 30 systems are involved.

Headless means the data model is the product. The screen was doing quiet work too: it was where someone noticed a field had been repurposed, or a picklist had drifted. Nobody logs in, so nobody sees that happen. Worth putting the check somewhere else before you need it.

A health score based on logins would have you halfway out the door.

how do you handle two agents updating the same customer record? that's the integration detail i'd want to see

headless for a year means you actually escaped the ui tax

Living headless on the CRM while agents talk to thirty systems is the future desk. Logins die. The data loop stays.

finally cutting the UI is the best part of the whole stack

Did going headless reduce admin work for reps, or mainly move it elsewhere?

Abstracting the workflow around daily actions can be valuable when the underlying platform becomes too broad for the team.

If you are using Salesforce headless, why not just use a could hosted database instead? Aside from the standardized schema and object model in Salesforce which can be replicated in a database, what other value does it provide if you are not using the UI?

Us too. It’s working great