Commercial Real Estate Firm

Migrated a legacy dataset of 350,000+ leads into Salesforce by splitting oversized CSVs into smaller, owner-based batches that stayed under API and governor limits

Used spreadsheets (filters, formulas, scripts) to batch and clean data before import, preventing failed loads and partial migrations

Standardized Salesforce IDs for external tools by generating 18-character IDs from 15-character IDs so VLOOKUPs, joins, and bulk operations worked reliably in Google Sheets and import tools

Designed and executed a bulk plan to reassign ~188,000 leads from an inactive owner to active sales reps, using exports, mass updates, and verified re-imports

Evenly distributed 4,000+ leads across a team of brokers by using quota-based formulas and owner mapping to ensure a fair, balanced workload

Planned and ran a quota-based reassignment of 200k+ leads, allocating fixed volumes per broker and rep, and routing the remainder into a shared lead pool

Built validation checks around all imports using SOQL queries, pivot tables, and spot checks to ensure data integrity after each large batch

Cleaned and normalized ~230k legacy leads by backfilling a company-domain field from email addresses so downstream automation and deduplication could work

Exported a full user roster (IDs, usernames, emails) and built crosswalk sheets to map owners during every bulk update and reassignment project

Implemented domain-based lead-to-account matching, enforcing a "one company, one account" model to reduce duplicates and support account-based selling

Built custom automation that auto-converts leads to accounts/contacts based on company domain, eliminating manual conversion for repeated companies

Implemented logic so that when certain call or task outcomes are logged, the system automatically converts the lead and updates related records

Built flows that update lead status automatically when specific activities or call outcomes are recorded, removing reliance on manual status changes

Debugged and fixed recursive / looping automation where flows and triggers were firing multiple times on the same record and causing errors

Added guard conditions and entry criteria to automations to prevent infinite loops, duplicate updates, and save failures

Replaced legacy Process Builder automations with modern record-triggered flows and lightweight Apex logic to improve performance and maintainability

Ensured that call counts / activity counts roll up correctly from tasks to leads, contacts, and accounts for accurate reporting

Fixed misaligned WhoId / WhatId relationships so that activities attach to the correct person/company objects in the CRM

Identified validation rules that were blocking automated test data and preventing deployments, then refactored the rules to allow automated scenarios while preserving business rules

Refactored complex SOQL queries to avoid unsupported patterns (like semi-joins with OR) by splitting logic into multiple, safer queries and in-memory joins

Designed and wrote Apex test scenarios that generate realistic data sets (leads, tasks, users, queues) for controller and automation coverage

Achieved required test coverage for new logic and controllers, resolving deployment failures caused by untested or partially tested code paths

Navigated around failing legacy tests by adjusting deployment strategies (e.g., running targeted test sets) where platform constraints allowed

Troubleshot list-loading failures between Salesforce and an external dialer platform, identifying dependencies on report refreshes and documenting the correct refresh/sync workflow

Standardized authentication into the dialer platform by enforcing login via Salesforce OAuth, ensuring activity and identity stay aligned

Audited and corrected field mappings for call dispositions between the dialer platform and Salesforce so reporting and status-based automation remained accurate

Followed data from dialer → CRM → external project/board tool to identify sync gaps, then repaired mappings so status and activity flows are kept in sync across systems

Troubleshot a managed-package lead conversion error that only affected non-admin users by tracing it through debug logs into a managed trigger

Identified missing field-level permissions on managed-package fields and fixed access so that non-admin users could convert leads successfully

Planned and configured single sign-on with Google for Salesforce, including federation IDs and login policy changes to centralize authentication

Reduced password sprawl and login friction by moving users from password logins to SSO with a unified identity provider

Redesigned cluttered page layouts across key objects to be role-based, removing unused fields and re-grouping sections for faster, cleaner data entry

Created separate opportunity "types" via record types with unique layouts and processes so different deal categories follow appropriate workflows and reporting

Built role-specific layouts for broker profiles, exposing only the fields and sections relevant to their workflow on leads, accounts, and contacts

Developed a standard report-based analytics dashboard for leads, showing totals, new leads, unassigned leads, converted leads, and active leads

Built dynamic variants of lead reports filtered by company size (e.g., under vs. over a certain employee count) to support segmented go-to-market views

Designed and implemented a custom Lightning dashboard UI using Lightning Web Components and a JavaScript charting library to go beyond standard Salesforce charts

Aggregated real-time KPIs via server-side logic, including counts for active leads, converted leads, available leads, assigned leads, daily calls, weekly calls, calls per user, dispositions, and leads per user

Packaged and integrated a client-side charting library as a static resource and wired it into the Lightning component so charts render inside Salesforce securely

Implemented defensive coding on the dashboard so null/missing values, empty datasets, and chart-loading failures don't break the UI

Styled the dashboard with a modern, card-based layout and responsive charts, turning raw data into a visual executive overview instead of generic Salesforce widgets

Set up and used the Salesforce CLI and DX project structure for controlled, repeatable deployments of components, Apex, and metadata

Deployed selectively to sandbox and production using CLI-based commands, managing test execution levels and handling production-only constraints

Packaged external JavaScript libraries as zipped static resources with correct internal paths and metadata so they could be loaded at runtime inside Salesforce

Resolved naming conflicts between older Aura components and new Lightning Web Components by renaming bundles and updating references

Worked within org-wide coverage requirements and deployment rules, including minimum coverage thresholds and production test policies

Maintained detailed internal documentation for every major change: what was done, why, how it was validated, and how to troubleshoot it later

Documented complex workflows (e.g., lead conversion automation, mass reassignment processes, dashboard data pipelines) in a non-technical format that leadership could understand

Scheduled and executed high-risk operations overnight, including large imports, code deployments, and automation rewrites, to avoid impacting business users

Monitored overnight jobs, validated results before business hours, and rolled back or corrected any anomalies before teams logged in

Designed and built a custom web-based lead assignment tool that connects to Salesforce via OAuth to manage bulk ownership changes without the 200-record UI limit

Gave admins a live view of lead pools and ownership and the ability to run bulk reassignments in real time without spreadsheets

Coordinated across stakeholders (sales, leadership, operations, admins) to translate business pain points into concrete technical solutions in the CRM

Acted as the bridge between data, automation, and day-to-day workflows, ensuring that technical changes actually matched how the revenue team works