Optimized Flow Design
Your Salesforce org is running automation nobody fully understands.
Workflow Rules and Process Builder hit end-of-life on December 31, 2025. Most orgs accumulated automation over years — built by people who've since moved on. Before you migrate anything, you need to know what you actually have: what's broken, what's redundant, and what to migrate first.
Legacy Automation Inventory
$1,200 fixedEvery Workflow Rule, Process Builder, Flow, validation rule, and Apex trigger in production — object, trigger condition, active status, last-modified date.
What fires in what sequence on record save, for up to five client-designated objects — so you can see what's actually happening and in what order.
Every item rated on business impact and fragility. Inactive, redundant, and orphaned automation identified. A recommended path to record-triggered Flows, with effort estimates per batch.
A 60-minute video call to walk through every finding together — not a handoff, a conversation. Delivered day 12–14.
Sample output — automation register
| Object | Name | Type | Status | Last Modified | Risk |
|---|---|---|---|---|---|
| Lead | Lead Assignment — Round Robin | Workflow Rule | Active | 2019-03-14 | High |
| Opportunity | Stage Change Notification | Process Builder | Active | 2021-08-22 | High |
| Lead | Welcome Email Series | Process Builder | Inactive | 2018-11-30 | High |
| Opportunity | Close Date Reminder | Workflow Rule | Active | 2020-04-17 | Medium |
| Contact | Duplicate Email Check | Validation Rule | Active | 2023-01-05 | Low |
| Account | Territory Auto-Assign | Flow | Active | 2024-06-18 | Low |
Dummy data for illustration. Your actual register covers every automation in production across all objects.
Accuracy guarantee
Every active automation in your production org, documented — or we keep working until it is.
How it works
You provision a dedicated named integration user with read-only access. I never share credentials or use a shared login.
Nothing changes in your org. No configuration is modified, no automation is touched, no data leaves your environment.
We do a 30-minute intake call at kickoff to align on which objects matter most, then I deliver findings in two weeks.
You deactivate the integration user on acceptance. The engagement closes clean.
Pricing and scope
Up to 50 combined Workflow Rules and Process Builders
50% at signing · 50% at delivery · Net 15 · Remote, no expenses
Non-profit organizations: $600 — same scope, same terms.
Price adjustments
Over 50 combined WF/PB: revised fees by change order before proceeding — not a surprise at delivery.
Multiple production orgs need a separate statement of work.
What's not included
Migration, rebuilding in Flow, data cleanup, Apex refactoring, managed package review, deployment, testing, end-user training, or ongoing support. Every one of those is a separate engagement — and the inventory report names exactly what each one would touch.
About
Steve Huls — 15 years of hands-on Salesforce experience, Kansas City, MO.
I've spent 15 years working directly in production Salesforce orgs — not just documentation, not just sandboxes. That means I know what legacy automation actually looks like in the wild: the rules that contradict each other in ways no surface-level scan catches, the Process Builders that fire on every save but only matter three times a year, the automation chains built across five admins over a decade that nobody has ever fully mapped.
Getting a real picture of what you have takes real-world experience with how it breaks. Remote engagements only. One at a time.
Let's talk about your org.
Send a message and I'll follow up within one business day.