top of page
About Us: Salesforce Confessions
The Salesforce platform is a powerfully abundant architecture, but as The Notorious B.I.G. said “Mo Money, Mo' Problems". To put it into Salesforce terms, more resources means more layers code and a compounding burden on resources. And while we may grin at these confessions, there is a critical point here. Salesforce transforms businesses, but it also breeds technical inefficiency from numerous origins.
Posting these confessions is the most poignant expression of our community's mission. We founded the community to help businesses methodically assess which portions of their Salesforce flows can be moved onto Saashups to relieve the pressure and increase agility.
"We shaved 30 hours of maintenance and over $15,000 in consulting fees per month after running a load audit and offloading heavy flows to Saashups."
Richard Hall
President, RAHWorks
Sales, Support, and Marketing Operations Expert
Former Executive at Zapier and Shopify
Here is a root cause analysis - i.e. what you'll avoid when using Saashups to automate projects.
-
Incomplete business analysis and scope before build starts
-
No thought about architecture before build
-
No documentation of why changes were made
-
Not applying DevOps methodology
-
Not future proofing the build by factoring in contingencies and unforeseen changes.
Source Credit: Elements.cloud OrgConfessions
_1657207546.png)
#1
We have 15,000 reports with no sensible naming.
#2
5372 Apex Classes and 55 Managed Packages, but I am not sure which we can delete.
#3
I learned we had 1,500,000 lines of undocumented Apex code.
#4
The audit to scope the clean-up work has taken 4 consultants 30 days. This 8-year-old Org doesn’t have a single line of documentation.
#5
We have 49,700 email templates. A bug in the managed package that integrated with a 3rd party marketing app (not Salesforce) created email templates every time it ran.
#6
We have run out of fields on the Opportunity object 5 times.
#7
Over 100 picklist values on a field but we have no idea which ones are used so we can’t delete any.
#8
Contact object maxed out with 800 fields when trying to consolidate 5 orgs. So we have no idea how to consolidate without duplicating an object.
#9
15,000 reports. No comment.
#10
464 fields (all used) and 14 stages on Opportunity object but the page goes on forever and takes minutes to load.
#11
We have 271 Permission Sets, 100s of public groups used in sharing rules and 103(ish) profiles.
#12
We found people who are doing Trailhead modules inside our Production Org.
#13
Case object maxed out at 800 fields with 54 record types.
#14
738 Apex triggers developed over last 8 years by external consultants. No documentation.
#15
Our Development team built a trigger that lets an external system synchronize the account address to their contact addresses and validates with an error message if any user tries to update the contact addresses. After deploying it to the Production environment, users could not create contacts anymore.
We spent time analyzing what was going on and found out there were workflows overlapping the trigger in the way that any user can update the contact addresses through the respective account. Workflows were given every time a Contact record is created or updated. Saashup solves this issue: 3rd Party Lead Follow Up
#16
700 fields and 280 are formula fields on one object.
#17
Managed packaged installs 209 objects, 79 tabs, 351 Visualforce pages, 160 apex triggers and 3126 apex classes into your org.
#18
Profile for every user.
#19
All business process and data for a 40-user company was on the same standard object.
#20
Every user is a system administrator.
#21
Someone had referenced all the Test 1, Test 2, Test 3 account names to be ignored in their code. Yikes!
#22
Inside sales couldn’t work out how to convert lead so printed it out and left on the desk of the sales person.
#23
12 triggers on the Case object. Sigh.
#24
Everything was coded in Apex by consultants who didn’t understand core Salesforce features. 3 million lines of code!! Every field was referenced so none could ever be deleted.
#25
Core Opportunity object and then 2 extra custom objects for more fields.
#26
Our Org was taken over by keen developers who automated everything and now we have “the world’s best self driving car… with no wheels”.
#27
200 Apex Classes. 50 tests failing in production. The other ones are fake tests with no assertions.
#28
Date of first meeting being stored on Lead and Lead Stage being processed on Task.
#29
My Manager removed the ability to export reports. Without telling anybody. 2 days before month end reporting was due.
#30
Every day, users need to log into at least 4 different Orgs to get their job done.
see full list at Elements.cloud
bottom of page