That fear is the symptom. CleanForce removes it. We clean up and refactor Sales Cloud and Service Cloud Orgs: Page Layouts, Fields, Record Types, Permission Sets, Flows and Apex. Cleaning is the only thing we do.
Nobody calls it tech debt. They say "Salesforce is slow." They say "we can't touch that." They say "maybe we need a new Org." Every one of those sentences is the same problem wearing a different costume.
“What if Cases stop being created when I touch this?”
The fear is rational. You don't fix it by being braver about clicking things. You fix it by making the Org readable again.
"What if Cases/Opportunities/Leads stop being created when I touch this?" All field notes on this →“Why does a simple change take three weeks?”
It isn't your team. Years of clutter turn three-day changes into three-week projects. Cleanup gives you the runway back.
There is a monster hiding under your bed, and its name is Technical Debt All field notes on this →“Half my team is fixing bugs instead of building.”
Fires come from dirty Orgs. The fix is not another firefighter. It's cleaning the Org.
No, it is not normal to be firefighting all the time in your Salesforce Org All field notes on this →“Salesforce is slow. Salesforce is annoying.”
Users don't hate Salesforce. They hate the mess. Clean the one screen they touch 50 times a day.
No wonder nobody wants to use your Salesforce, just look at your Opportunity All field notes on this →“Maybe we just need a new Org.”
More than 90% of "we need a new Org" should be a cleanup. Keep what works, remove what doesn't, clean the rest.
DON'T WASTE YOUR MONEY ON A NEW ORG! All field notes on this →“Agentforce is next year. Is our Org ready?”
An agent inherits your Org exactly as it is. AI isn't a fix for a messy Org. It's a stress test.
An AI Agent will not save you from a messy Org All field notes on this →“I know it's a mess. I just can't prove it.”
That's exactly what the free audit is for: a score, your top priorities and a summary you can hand to your manager.
How to ask for a Cleanup Budget that actually gets approved All field notes on this →“Where do I even start?”
At the front door. Easy wins first, the boss fight last.
Nobody starts a video game at the final boss! All field notes on this →Cleaning is a profession, done by professionals. That's why cleaning is the only thing we do.
Walk into any office at 6pm and you'll find a cleaning crew. Not because the people there are careless, but because real work under real deadlines always leaves residue. Your Org works the same way. You wouldn't ask your sales team to mop the floor between calls. So why do we ask Salesforce teams to clean "as they go"?
Judgment, Org experience, stakeholder alignment and the decision what to delete. None of that is done by AI.
Your line cooks keep cooking. We clean the kitchen, outside your normal sprint cycle.
Low risk, visible results, and your developers stop spending sprint time on guerrilla cleanup.
Most cleanups die in week three because they start with the scariest thing in the Org. We start where Users notice it and nothing can break.
Tabs, Page Layouts and List Views. Not the basement. Users notice the difference the same week, and that buys trust for everything after.
The 5-second method: for every Field, Button and Component, "what do you need that for, and when did you last use it?" No answer in five seconds, it goes. Typically 50 to 70% less clutter.
Unused Fields, inactive Flows, Reports nobody opened in two years. None of it can break anything, and it shrinks the monster class before anyone touches it.
Not everything messy needs cleaning. The ugly Visualforce page that hasn't caused a problem in years can wait. No pain, no priority.
Remove access before deleting. Switch logic off with a toggle before removing it. Change on a Tuesday morning and watch. Backups, always.
A maintenance plan for every important part of the Org and a fixed share of capacity. The goal is an Org that can be cleaned faster than it gets dirty.
You don't need a giant ROI spreadsheet. But the numbers are there, once someone looks.
record save time after old Validation Rules, Roll-ups and unnecessary Flows were removed.
hidden in a Record Type maze for 500 agents: 10,800 hours, five full-time agents.
bug hunting on a Validation Rule that reads like a business requirement.
story points per sprint, same team, no hiring. Cleanup is capacity recovery.
burned by one legacy button on a Case layout, at 1,000 agents and 40 Cases a day.
up to that, often from $50k, spent on licences, packages and portals nobody uses anymore.
Examples and calculations from Johann's field notes. Your numbers will differ, which is why we look at your Org.
Most "broken" Orgs are just overgrown. With a new Org you pay a massive premium to avoid the work of cleaning, and often end up copy-pasting most of the dirt.
There are legit reasons for a new Org. A messy Org is none of them.
Most Admins, Developers and Architects I talk to know their Org is a mess. 600 Fields on Opportunity. Flows and Apex nobody understands. But they can't prove it and don't know where to start, so cleanup never gets budget. The free audit fixes both in 60 minutes.
Live, side by side, on a screen share. I start where your Users start and walk the core process end to end, the way someone doing the job every day experiences it.
Core Objects and Fields, Record Types, Validation Rules, Flows, Apex, Sharing and Roles. Plus a few random deep dives, because the surprises live there.
Two questions matter more than any checklist: what are the dirtiest parts of this Org, in your own words? And if you had a magic wand, what would you clean first?
A score for Usability and Build Quality, your top cleanup priorities ranked by impact and effort, and a clear summary to share with your manager.
I score your Org on exactly two things, benchmarked against what I'd expect from a comparable clean Org of your size and industry.
How it feels for the people doing the job every day.
How safe and easy it is to change.
Architects who've seen dozens of Orgs and almost none of them clean. Product Owners who can't understand why the simplest change takes forever. VPs whose Salesforce headcount blew past every projection. Three complaints, one root cause.
If cleanup doesn't have a line item, a share of every sprint and an owner, it loses to the feature backlog. Every single time. Until the day it's the only thing that matters.
Open your Org. Find one dirty thing. Fix it this week.
Short, practical, practitioner to practitioner. Pick the moment you're in.
For the last 10–15 years: Another Field here, another Flow there, another integration, another quick fix, another project. Bit by bit, the technical debt monster grew.
Read field note Afraid to touch it · 1 minWe are all scared to touch big, old Orgs. Years of Flows stacked on ancient Validation Rules stacked on Triggers nobody fully understands anymore. You open the Object Manager and just…
Read field note Thinking about a new Org · 1 minI'm going to put my foot down on this one: >90% of "we need a new Salesforce Org" should be a cleanup and focused refactoring effort instead.
Read field note Getting cleanup approved · 1 minDavid Giller and I discussed how to convince the business to invest in Salesforce cleanup, here's our idea: "Use their Sales Leaders".
Read field note Users avoid Salesforce · 2 minMost Orgs are carrying 50-70% more clutter on their Page Layouts than anyone actually needs, and the fix is an average User and a stopwatch. Ask a user "what's this for, when did you last…
Read field note Afraid to touch it · 2 minA bank's Salesforce team was staring at an Apex class that handled almost every important process in their Org, a payment class. Nobody wanted to touch it. It had grown for six years,…
Read field noteI dreamt about CleanForce for years. My first cleanup was a mess I made myself, and I'm still sorry to every "Test_Johann" Page Layout out there.
Fifteen years, a CTA and more than 30 certifications later, I've seen dozens of Orgs and almost none of them clean. Not because people did a bad job. Because nobody ever owned the cleanup.
I still build the way I wrote my first BASIC programs over 30 years ago: when this happens, check this, do that, finish. Every Flow, Apex Class and Validation Rule should read like a recipe. For most Orgs, simplicity isn't a compromise. It's the better engineering decision.
To the teams of three punching like a team of fifty, and to every Admin who inherited "Sales Copy of Copy FINAL": I see you. Based in Berlin, cleaning Orgs across Europe and the USA.
You don't need to fix everything. You need to fix the right things first. In 60 minutes we find them, and you leave with a score you can take into your next leadership meeting.
