Find the technical debt worth fixing
Review outdated automation, fields, record types, permissions, reporting dependencies, and admin clutter. Separate what is merely untidy from what is creating real risk or maintenance problems.
Read related notesExpertise
Salesforce expertise and background.
My background includes automation, reporting, data quality, user setup, access, and administration. These are areas of experience, not services available for hire.
I’m currently employed full-time and am not seeking new roles or accepting independent consulting engagements.
Areas of experience
Topics that recur in my work.
The examples and notes on this site show how I approach configuration, maintenance, verification, and documentation.
Untangle unreliable automation
Trace active Flows, entry criteria, legacy automation, downstream updates, and error paths. Repair the problem without turning a focused change into an unnecessary rebuild.
Read related notesBuild reporting people can explain
Verify source reports, filters, formulas, folders, dashboard components, targets, and fiscal logic so leadership can understand where the numbers come from.
View reporting case studyClean CRM data with a rollback path
Find stale ownership, missing assignments, inconsistent values, duplicates, and other exceptions. Define safe update rules, preserve backups, verify the results, and document unresolved blockers.
View cleanup case studyCreate a safer admin and user setup path
Improve user provisioning, permission assignments, access troubleshooting, onboarding guardrails, and repeatable admin workflows without relying on tribal knowledge.
View user setup case studyAdministration and documentation
My experience includes reporting, Flow fixes, data work, user support, documentation, and recurring cleanup.
Read related notesCapabilities
Salesforce capabilities I work with.
- Sales Cloud
- Flow
- Reports
- Dashboards
- Permission Sets
- Profiles
- Sharing Rules
- Validation Rules
- Record Types
- Dynamic Forms
- Data Loader
- Workbench
- SOQL
- Approval Processes
- Lightning App Builder
- Conga
How I approach the work
Inspect the system. Make the safe change. Prove it worked.
The first useful deliverable is clarity: what is happening, why it matters, and which change is safe enough to make next.
- Understand the symptomIdentify the affected users, records, reports, automation, and expected business outcome.
- Inspect what is liveReview the relevant configuration, runtime behavior, dependencies, data, access, and business rules.
- Repair and verifyMake the narrowest useful change, test the result, and confirm the live behavior matches expectations.
- Document what changedLeave verification notes, maintenance guidance, and any remaining risks or follow-up items.
Explore the portfolio
Past work and practical Salesforce notes.
Read the case studies for implementation details, or browse the articles for Salesforce concepts and maintenance practices.