Case Studies

Real Salesforce problems. Practical technical outcomes.

Selected examples of complex Salesforce problems I have worked on across automation, performance, data operations and enterprise platform maintainability.

Selected Work

Enterprise Salesforce is rarely as tidy as the architecture diagram

Production Salesforce environments accumulate years of automation, integrations, business rules and operational workarounds.

The case studies below focus on situations where the technical problem required more than simply implementing another user story. Each example looks at the underlying issue, the approach taken and the measurable outcome.

Automation & Performance

01

Simplifying complex Salesforce automation in financial services

A heavily customised Salesforce environment had accumulated overlapping automation, making important business processes harder to troubleshoot and increasingly vulnerable to Salesforce platform limits.

View full case study →

Challenge

Large debug logs, overlapping Process Builders, SOQL and CPU pressure, and increasingly difficult production troubleshooting.

Approach

Reviewed the automation chain, consolidated duplicated logic and moved appropriate functionality toward cleaner Apex and Flow-based implementations.

Outcome

Reduced debug log volume from approximately 10 MB to around 100 KB while significantly improving maintainability and troubleshooting.

ApexFlowProcess BuilderSOQLGovernor LimitsDebug Logs

Product & Data Operations

02

Accelerating large-scale Salesforce product creation

Creating hundreds of Salesforce products together with dependent catalogue records meant building each one by hand across Products, Price Books, Price Book Entries, Features and related configuration.

View full case study →

Challenge

The business supplied around 200 products as a list in business terms, with no Salesforce IDs. Each product was then built manually, often by cloning an existing one: several days of repetitive, error-prone work.

Approach

Designed a structured Excel-based framework for preparing relationships, validating catalogue data and orchestrating repeatable Data Loader operations.

Outcome

Approximately 200 products and related records could be loaded in around one hour of Data Loader operations after preparation.

Salesforce ProductsPrice BooksData LoaderExcelData MappingValidation

Engineering Approach

The recurring pattern behind the work

Different Salesforce problems require different implementations, but the engineering principles behind them tend to remain remarkably consistent.

Understand the real problem

Technical symptoms such as CPU limits, failed automation or repetitive data operations usually point to a broader process or architecture problem.

Simplify before adding

The best Salesforce solution is not automatically more Apex, more Flow or another layer of automation. Sometimes the useful work is removing complexity.

Design for production

Solutions need to survive real data volumes, existing customisation, platform limits, deployments and future maintenance.

Products & Accelerators

Some of these problems became reusable solutions

Recurring operational challenges helped shape the Org Change Monitor and Product Catalogue Accelerator currently being developed.

Explore Products

Your Salesforce Environment

Dealing with a similarly complicated Salesforce problem?

Whether the issue is automation, performance, integrations, technical debt or complex data operations, I can help analyse the problem and determine the most practical technical approach.

Discuss a Project