💃 Is Your Salesforce Solution OP? 🕺

Good morning, Salesforce Nerds! When you see a problem, you design and build a Salesforce solution 😃!

What if you added these two criteria to your solution-

1) The solution must last 10 years.

2) The solution must hold up to 1 million cycles.

Does that change your design?

Let’s dive deeper 👇

10 YEARS AND 1 MILLION CYCLES

Enterprise Salesforce Solution, Quantified

How long has the company you work for been around? How long do they plan to be around?

And they’ll need to sell all this time, right? In a CRM?

10 Years

Enterprise solutions require longevity because the enterprise - the company you work for - intends to be around for the long term. The CRM needs to evolve and grow with the company 💯.

If you were 50 users 3 years ago, and you’re 100 users now, then how many users will your org be in 10 years? What will the org look like with that growth?

More users. More processes. More permission sets. More complexity.

1 Million Cycles

And what about 1 million cycles? That could be a number of things -

👉 1 million Flow runs

👉 1 million Lead → Opportunity conversions

👉 1 million inbound leads

Let’s take inbound leads as an example: Zapier is an amazing solution - easy to integrate, easy to configure - you can get a webform hooked up to your Sales Cloud in under an hour 🤩.

But 1 million inbound leads? Zapier charges based off of usage, and that many zaps will blow the budget 💸. You’re gonna need a badder solution. Perhaps a direct integration with the Salesforce API, into a staging object. Something that can scale up to 1 million cycles 🙂.

WHAT NEXT?

Future-Proofing Your Salesforce Org

What if you worked for an international company that dealt with different currencies? Well, you could hardcode the currencies into your code, or build a currency object. And each time you launched ops in a new country you’d add that currency to your solution 🧑‍💻.

OR

You integrate with a real-time exchange rate API. Not a small lift to integrate with this service, but at least this one scales beyond your current state 🙌.

Here are a three practical ways you can take this mindset into your own workstreams-

📈 Design for Growth - What if your org grew from 10 seats to 1000 seats? What if revenue grew from $10 million to $10 billion?

🥵 Stress Test - Your solution can handle one record. You know because you tested it! But can it handle one thousand records? If you dataloaded a ton of records, would your solution break? If your marketing team’s ad went viral and the webform was intaking hundreds of leads per minute, would it hold? Think about stress testing during your design process.

⛰️ Strong foundations - things that last 10 years have strong foundations. Toyotas last forever not because of superior materials, but rather superior build processes like Kaizen. In Salesforce, strong foundations can be considerations for DML operations, SOQL limitation, or even naming conventions (are your permission set names going to be understood in 10 years?).

FINAL THOUGHTS

Takeaway

The next time you’re designing a solution, pause and ask yourself:

Will this hold up for a decade? Can it withstand a million cycles? 

If the answer is yes, you’re not just solving today’s problem, you’re building something remarkable.

And the more reps you get doing this - the more you drill it into your solutioning process - then the easier it will become to synthesize the conversion of complexity to simplicity and building scaleable solutions.

SOUL FOOD

Today’s Principle

and now....Your Salesforce Memes