Trace what is live
Map active Flows, legacy automation, report logic, access rules, and dependencies before changing anything.
I help teams untangle inherited automation, unreliable reporting, permission issues, inconsistent data, and undocumented admin work without forcing a full reimplementation.
Project-based and fractional Salesforce support for teams that need practical fixes, clear documentation, and maintainable changes.
I am most useful when ownership has changed, documentation is thin, reports no longer match expectations, and every configuration change feels riskier than it should.
I trace what is live, resolve the highest-value issue, and leave the team with a clear path forward.
Map active Flows, legacy automation, report logic, access rules, and dependencies before changing anything.
Resolve the problem blocking trust without turning a focused engagement into a full reimplementation.
Provide verification steps, admin notes, and plain-English explanations so someone else can confidently maintain the work.
Bring me the symptom, not a perfect brief. I can trace what is running, prioritize the safer fix, and explain the tradeoffs in plain English.
Audit outdated automation, fields, record types, permissions, and admin clutter. Prioritize what to keep, retire, consolidate, or document.
Untangle and repair overlapping or unreliable automation, simplify logic, improve error handling, and reduce unnecessary complexity.
Verify source reports, filters, formulas, folders, dashboard components, and fiscal logic so the numbers can be clearly explained.
Experienced administration for cleanup, reporting, Flow fixes, data work, documentation, and user support without adding a full-time hire.
Client names and sensitive org details are removed. Each example reflects Salesforce work I completed, verified, and documented.
Pipeline dashboards depended on target records, workbook assumptions, and divisional rollups that no longer aligned. I traced the live logic, preserved intentional business exceptions, corrected report filters and rollups, and verified the final numbers in production.
What I left behind: rollout checklist, verification summary, admin runbook
View case studyOpen opportunities were tied to inactive users or missing key assignments. I repaired broken report logic, rebuilt the dashboard around actionable exception counts, and used reversible update files to clean only the safe records.
What I left behind: admin dashboard, runtime checklist, rollback-ready updates
View case studyAdmins needed a clearer way to create users from employee and training data. I built guided flows that surfaced only ready records, blocked incomplete data, avoided duplicate links, and documented the process for future admins.
What I left behind: screen flows, setup guardrails, verification checklist
View case studyStart with the symptom, inspect the relevant metadata, and identify what is actually running before touching the setup.
Handle the part blocking trust without creating a mystery downstream: Flow logic, report filters, dashboard wiring, field clutter, access, or admin workflow.
Leave plain-English notes, verification steps, and caveats so the next admin is not stuck reverse-engineering the fix.
I am Justin Pena, a Salesforce Consultant based in Houston. I specialize in inherited systems, operational cleanup, and making complex Salesforce work understandable to the people who have to maintain it next.
A short note is enough: the unreliable report, risky Flow, access issue, data cleanup, or admin work that keeps getting pushed aside.