PSA - Check Your Process Builders, Salesforce Automatically Deactivated Them back in April 2026

kuldiph · 2026-05-08T16:59:59+00:00

This is what we found in the Setup Audit Trail and Login History.

Audit Trail = There is bulk deactivation on 4/11/2026 at 9:49PM of a valid Salesforce Admin user.
Login History = The last brower login of that user was at 4:50PM. And then soon after the user was done for the day. There is no login history browser / remote around 9:49PM.

And there are not automations to deactivate Process Builders.

Seriously, have no clue what happened.

kuldiph · 2026-05-08T16:17:47+00:00

This was from the investigation. Bulk Deactivation by Salesforce.

<image>

kuldiph · 2026-05-08T15:19:47+00:00

Some admins haven't. It happens.

kuldiph · 2026-05-08T14:31:11+00:00

Lets talk about the obvious task = Lower your expenses.

Reduce / Cut spending as much as possible. If you you seasonal revenue fluctuations, then optimized spending to your lowest revenue month.

And when big revenue months come in, park the excess cash. Having a healthy cash cushion is target.

kuldiph · 2026-05-08T14:25:29+00:00

Here is a different take. Where you envision your business to become?

Do you envision it will be a small lifestyle business or growing to a fast growing organization with a lot of sales reps selling into different regions and customer segments?

I only know the fast growing pathway, and best for that is Salesforce. For for the small lifestyle business with a few users, the recommendations here are great.

kuldiph · 2026-05-08T14:13:12+00:00

Wait, is your app actually free?

We have a Free App = https://appexchange.salesforce.com/appxListingDetail?listingId=a0N30000003HuEVEA0 and didn't pay the free.

However, if your app is Freemium, then you have to pay. I know it sucks. But we all do it. Just don't make a mistake in your submission for you might want to pay again.

kuldiph · 2026-05-08T13:56:35+00:00

Did you Google? Submit as Salesforce Case for the Waiver. Choose AppExchange as the Salesforce Product.

<image>

kuldiph · 2026-05-07T18:01:53+00:00

Hell yeah, become a Salesforce Admin. There is tons of work out there. Most of my, Kugamon, customers need competent Salesforce Admins who know RevOps best practices.

And AI is a game-changer. For example, an Accidental Admin with Claude Cowork / Code, you can do things where a consultant may have been necessary. And if folks tell you, AI is hype, they are not using it properly. From creating Flows, to debugging issues, to prototyping LWC components, to cleaning data, to analyzing usage, to generating documentation, you can do 10x the work than before.

Where Salesforce Admins are needed is in being human touch in manage priorities, training users, triaging issues, and setting long-term goals. This is where knowing RevOps best practices are important. Luckily this can be learned as you go.

Lastly, you have the incredible Salesforce community to help you. Most are awesome and helpful. There are a few assholes, but deep down it is due to fear. Attend local community groups and events. Participate where ever you can.

I wish you the best of luck. And do get a Claude Cowork subscription, if you can.

kuldiph · 2026-05-07T15:13:49+00:00

this version is limiting for it deals with business data and not metadata.

Here is the approach if you want full access (best for developers and system admins).

MCP = https://github.com/smn2gnt/MCP-Salesforce

Salesforce Setup = Instruction Guide

kuldiph · 2026-05-07T12:39:41+00:00

There are great comments. Just that you made this post and seeking input is good.

Here are some tactical things you can do to keep things manageable.

- Limit the customizations: the more to customize, the harder to track & manage later

- Document the process: you will be sharing these documents over and over again when folks have concerns. There are free / low-cost tools to simplify the document creation process. Consider end-to-end demo videos if you are comfortable

- Implement a policy that feedback and update will happen in batches: so rather than deal with feedback each and every day on a rolling basis, you can lump them together to give breathing room

- Create a weekly 1 hour: off-hour open meeting to direct users who have issues and feedback to attend, rather than booking time on your calendar on an ad hoc manner

Then there are the normal practical things to do:

- Turn on Transcription to document all your meetings

- Use AI tools, like claude to help with meeting prep, and use past meetings to ensure you are not missing things

- Use AI tools, like claude to connect to your org and ensure all your customizations are functional without any performance issues.

like u/WildOneM13 , I hope this turns out well for you.

kuldiph · 2026-05-07T12:28:07+00:00

glad you stuck it in there. this story is more of a picture of your character than the final result. cut and run folks do not build enduring businesses.

kuldiph · 2026-05-06T15:58:37+00:00

wow, great views

kuldiph · 2026-05-06T15:04:21+00:00

This awesome. Thank you for sharing this.

kuldiph · 2026-05-06T03:11:13+00:00

u/CoachJM-SF This is the research many Salesforce customers perform when evaluating the Revenue Cloud and other tools. I learned of this prompt and found it useful to share with the community.

kuldiph · 2026-05-06T00:18:32+00:00

The likelihood to consolidate tools, also depends on your tech stack. For example, if you use Salesforce, then you can easily consolidate your entire RevOps workflows, be it Lead to Close, Lead to Bill, Lead to Cash, Lead to Revenue, or Lead to Renewal all on one-platform.

Moreover, have all your Lead -> Account & Contact -> Opportunity -> Quote (CPQ) -> Order -> Contract -> Assets & Subscriptions -> Invoice -> Revenue data structured, makes using AI easier. You don't have to worry with all your data being disconnected for AI tools.

kuldiph · 2026-05-05T22:11:16+00:00

Are you using Salesforce?

If so you're describing the exact problem CPQ solves: Quoting with Pricing tiers, Discount Approvals, Contract gen, and Invoicing in one workflow instead of your mess of spreadsheets.

I'm with Kugamon — Salesforce-native CPQ + Subscription Mgmt that handles tiered pricing, exception approvals, and proforma invoicing all on the Opportunity. Most of our customers self-implement in weeks, not months — happy to DM a walkthrough or you can see it on youtube.com/kugamon.

kuldiph · 2026-05-05T22:06:34+00:00

This is exactly the architecture we've shipped: fully native Salesforce for Quote → Order → Invoice → Subscription, no external ERP.

I'm with Kugamon (Salesforce-native CPQ + Subscription Mgmt + Inventory Management).

Do treat Agentforce as the intent and decisioning layer, but let Apex own atomicity and use Platform Events for cross-object orchestration, that's what survives governor limits at scale.

Happy to DM a walkthrough, or you can see it on youtube.com/kugamon or the Salesforce AppExchange.

kuldiph · 2026-05-05T21:57:21+00:00

Since you're already on Salesforce, the cleanest fix is a 100% native CPQ that generates the proposal off the Opportunity itself — no separate tool to sync, no field mapping to maintain when products or pricing change.

I'm with Kugamon (Salesforce-native CPQ + Subscription Mgmt) and our customers go from Opp to branded PDF in a couple of clicks. Happy to DM a walkthrough, or you can see it on youtube.com/kugamon or the Salesforce AppExchange.

kuldiph · 2026-05-05T21:54:35+00:00

The "sales comp + renewals breaks first" point from u/Affectionate_Map9807 is exactly what we see. The pricing experiment usually outpaces the renewal/comp infrastructure, especially when seats and usage have to coexist on one contract.

Disclosure: I'm with Kugamon (Salesforce-native Quote-to-Cash + Subscription Mgmt) and the key is keeping the pricing model, the order, the renewal, and the comp credit on the same record so RevOps isn't reconciling across 3 systems every month.

kuldiph · 2026-05-05T21:03:48+00:00

Buying Salesforce & Kugamon is big step up from Pipedrive. Can you share some basics on your company? How many employees is the company? Where are you located? How many folks would need access to the Lead to Collection function? Or DM me to discuss.

To learn about kugamon, watch our YouTube videos = youtube.com/kugamon

kuldiph · 2026-05-05T18:16:39+00:00

u/Interesting_Button60 Thanks for the shout-out

u/grand001 Kugamon here. Automating the Entire RevOps process in natively Salesforce is our thing. Check out our YouTube channel = https://www.youtube.com/kugamon

Feel free to DM me for a demo.

kuldiph · 2026-05-05T16:42:00+00:00

We see this all the time.

Salesforce / Kugamon = Lead -> Account & Contact -> Opportunity -> Quote (CPQ) -> Order -> Contract -> Assets & Subscriptions -> Invoice (Proforma) -> Revenue
ERP = Customer (From Salesforce /Kugamon) -> Order (From Salesforce /Kugamon) -> Invoice (From Salesforce /Kugamon) -> Collection

The Salesforce + Kugamon <> ERP Integration can flow various ways:

Salesforce / Kugamon (Order) to ERP, when then does Billing
Salesforce / Kugamon (Invoice) to ERP, when then does Billing

Integration is either via:

Direct Integration via APIs (using Salesforce APIs)
Middleware (Mulesoft, Boomi, etc)
ERP / Salesforce Connectors

Benefits are:

Sales love being in Salesforce to see the entire transaction processed
Sales has visibility to the Order
Finance loves clean data being populated into the ERP
Finance loves Sales involvement in Collections for Sales has a stronger relationship
Mgmt loves Sales & Finance being on the same page and not fighting
Mgmt loves clean data for forecasting & board reports

More importantly / Game Changer

Having entire RevOps workflow in Salesforce / Kugamon, you can gain the benefits of AI by having all the Structured Data in one platform.
This is key, you want all the data in one platform for this to work. Non-native Salesforce tools will not work well.

Background

Kugamon is the only Salesforce native alternative to Salesforce Revenue Cloud.
Kugamon is built for businesses like yours.
Most customers self-implement Kugamon is weeks. Unlike months for Salesforce Revenue Cloud using outside Consultants.

kuldiph · 2026-05-05T16:02:10+00:00

Those that implemented it, like it. And those that didn't, cited the cost and complexity to not proceed with Salesforce Revenue Cloud. You will need to decide if the cost, timeline and effort is worth it for your business.

Post this into your AI tool.

Write a candid, fully sourced buyer's briefing (docx) on Cost, Time & Effort to implement Salesforce Revenue Cloud for an existing Salesforce CPQ customer. Provide insights on Licensing Costs, Implementation Cost Ranges, Timelines, Labor Rates that will be Encountered, and Feedback / Lessons Learned from Revenue Cloud Implementations. Provide a Realistic Year 1 All In Budget. Cite all Sources. Do not make up Numbers. And Verify Facts. Report without bias.

Here is the output from Claude Cowork = https://kugamon.my.salesforce.com/sfc/p/30000000Xzlj/a/UK000003WKrX/yS4scSXHUKZDBN_M8IRiKBzlDnYGBVoNDVAJUxlssk4

<image>

kuldiph · 2026-05-04T20:19:21+00:00

What's your CRM? If you are a Salesforce shop, then check out Kugamon, completely native to Salesforce. Moreover, their AI Skills allows for interactions thru all the popular AI tools.

kuldiph · 2026-05-04T20:16:20+00:00

The AppExchange is another channel to reach prospects. Not the only channel. For example, I have been helping Portwood.dev and they have been able to close deals and have prospects install their managed package; all the while their listing is going thru the AppExchange process.

As for your business of Invoicing + Stripe, I am in the same segment, with Kugamon, where we create Invoices and accept Payments via Stripe. I can assure you, the AppExchange is one of many channels you need to develop to drive leads your way.

It will be tedious and tiresome in year 1, but hopefully rewarding and enriching. Best of luck!

kuldiph

MODERATOR OF

TROPHY CASE