Trace what is live
Map active Flows, legacy automation, report logic, access rules, and dependencies before changing anything.
I'm Justin Pena, a Salesforce professional focused on automation, reporting, and making complex systems easier to maintain. This site brings together my past work and practical Salesforce notes.
I’m currently employed full-time and am not seeking new roles or accepting independent consulting engagements.
My past work has involved inherited automation, unclear reporting logic, and configuration that needed better documentation.
I start by tracing what is live, verify changes carefully, and document the reasoning.
Map active Flows, legacy automation, report logic, access rules, and dependencies before changing anything.
Resolve the problem blocking trust without rebuilding parts of the system that still work.
Provide verification steps, admin notes, and plain-English explanations so someone else can confidently maintain the work.
Automation, reporting, data quality, and administration are recurring themes in my work and writing.
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.
My background includes cleanup, reporting, Flow fixes, data work, documentation, and user support.
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 study
Open 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 study
Admins 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 professional based in Houston. My work focuses on making complex systems understandable to the people who maintain them.
Read the case studies for implementation details, or browse the articles for Salesforce concepts and maintenance practices.