Admin Tricks

https://sforcemaximizer.com/salesforce-winter-27-through-an-architects-lens-6-areas-that-matter/

If you are an architect or aspiring architect looking at Winter ' 27 features, here is my blog, which highlights key features with a framework that will help your organization scale, leverage the Well-Architected Framework, identify areas to rearchitect, change your operating model, do more with Salesforce, and prevent problems. 

Guys, if you're dealing with contract signing in Salesforce Revenue Cloud, this one's worth a look.

If you're setting up the post-quote process right now, or just tired of how it currently works, I came across something that handles it properly and figured I'd share ➡️ https://youtu.be/lOGqNBqTM0M. 

The flow usually goes like this: the quote goes out as a PDF, the customer replies asking about one line, you resend, then it's two weeks of chasing a signature, and nobody can tell you where the deal actually stands.

This does it all in one place instead. Customer clicks a link, lands right on the quote in the portal. No login, no account setup. Any questions, they just ask in the chat there. They pick the option they want and sign it right away. And you can see whether they've opened it, which is the bit I liked most.

Do you think such functionality would be helpful in your case?

https://sforcemaximizer.com/is-your-salesforce-security-model-ready-for-a-redesign-watch-this-session-at-dreamforce/

If you are admin, architect, IT leader going to dreamforce and looking for best practices on a security redesign, here is a great blog by

I've noticed one thing while watching Revenue Cloud projects slip: the delay rarely comes from the configuration itself. It comes from decisions nobody could make yet. 

How do amendments work for this product line? Who owns the renewal date? Does tax get handled here or downstream? Each one sits open for a week or two while the right people get in a room, and every module you've scoped in adds a few more of them.

So the projects that move fast aren't better at building. They just made fewer decisions in phase one, because they scoped fewer things to decide about. 

If you're mid-implementation and the timeline's drifting, it's worth listing everything currently blocked on a decision rather than on work. Usually the list is shorter than it feels, and half of it belongs to a module you didn't need live on day one. 

We're running a session next Friday on where the time actually goes, plus a customer who went live in weeks and what they pushed to later. Join if interested!

Something I've noticed on Revenue Cloud projects: nobody sets out to overscope. It just happens because everything's available on day one. Billing, orchestration, taxation, amendments, usage. All there, all reasonable to want, all in the plan by the second workshop. 

Then it's six months later, and sales is still quoting from a spreadsheet.

The orgs that get live fast usually didn't do anything clever. They just picked a smaller starting point. Pricing that doesn't need a human, quotes that go out same day, renewals that don't slip through, a portal so customers stop emailing. That's most of the pain for a fraction of the build.

The easiest way to find your own starting point is to ask what you could postpone six months without anyone complaining. Surprising how much of the original scope survives that question.

If you're interested, there is a session on how the discovery works, plus a customer who went live in weeks and what they left on the shelf.

Anyone else tired of the "ugh, gotta log into Salesforce for that" moment?

Been thinking about how much sales and partner stuff still gets stuck just because someone's not sitting in front of Salesforce when they need it. Especially partners who aren't in there every day, they end up waiting to check something or forgetting to log a lead until way later.

Here is a demo that kind of solves this in a fun way: a partner texting an agent on WhatsApp, asking "hey what deals do I have going right now," and just getting a quick summary back. Then they added a brand new lead the same way, just described it like you'd tell a coworker, and it showed up in Salesforce a minute later. No forms, no logging in, nothing.

Made me think there's a lot more room for this stuff beyond just support chatbots. 

Sharing the demo here in case anyone wants to see it in action: https://youtu.be/IchcGTDtnBI

https://sforcemaximizer.com/designing-salesforce-integration-users-for-enterprise-security-and-scale/

If you are an architect, admin, developer, IT manager concerned about your security with your integrations in Salesforce, my blog provides you a framework which you can use to design security which can help to scale, reduce your audit time and expand to the digital agents.

Anyone else dealing with the CPQ → Revenue Cloud switch? https://bit.ly/4x44s3R

CPQ is in end of sale now, and I've been reading up on how people are actually handling the move instead of just panicking about the deadline. Biggest thing I noticed: nobody does a straight cutover. Everyone phases it in, mostly because CPQ configs tend to have years of pricing logic nobody remembers setting up.

Found a solid writeup on the whole process if anyone wants it.

Would love to hear how it's actually gone for people, good or bad.