Custom Apex Implementation
Build and ship business-critical Apex logic, services, triggers, and asynchronous processing that behaves predictably under load.
View details
Specialist Support
High-impact Salesforce development services
Focused implementation support for teams that need complex Apex and LWC work delivered correctly, quickly, and with production reliability in mind.
Where I provide the most value
Development-heavy work where senior implementation depth materially improves delivery speed and quality, with integration delivery as a core pillar.
LWC Feature Delivery
Develop robust Lightning Web Components for real product workflows with maintainable structure and production-ready behavior.
View detailsIntegration Delivery
Implement and harden Salesforce integrations with reliable callout patterns, clear failure handling, and maintainable endpoint contracts.
View detailsDevOps and Reliability
Reduce release risk and improve delivery reliability with CI/CD pipelines, deployment automation, and environment management tailored to Salesforce teams.
View detailsCodebase Refactoring and Stabilisation
Refactor brittle Apex and LWC modules and resolve high-impact defects, performance issues, and governor-limit failures before releases.
View detailsProof from real delivery work
Detailed case studies showing real implementation outcomes across service areas.
Case Study: Converting Aura to LWC Cut Record Load Time from 10s to 0.1s
An anonymised Salesforce case study showing how migrating a complex Aura match-management interface to LWC reduced first usable load time from about 10 seconds to around 0.1 seconds.
Read full case studyHow engagements work
Scoped delivery
Every engagement starts with a clear scope. I focus on specific deliverables — features, fixes, or modules — not open-ended retainers.
Senior implementation depth
I write the code directly. No delegation, no handoff. Complex Apex, LWC, and integration work delivered by the same person who scoped it.
Production-grade standards
Code ships with test coverage, failure handling, and documentation. Optimised for low-maintenance operation, not just passing acceptance.
Ready to discuss an engagement?
I work best with teams that have a clear deliverable in mind. If you have Apex, LWC or integration work waiting, send me the scope and I will say whether I can take it on.
Discuss an engagement Or browse technical articlesRelated articles
Technical deep-dives that support the services above.
How Big Is Too Big? Downloading Large Files From an External System Through an LWC
Where the size ceiling sits when an LWC downloads a file through Apex, and the signed URL pattern to use beyond it.
sf project deploy start: flags, dry run, test levels and errors
What sf project deploy start does, the flags that matter, dry run vs validate, the test levels, what report, preview and resume do, and what each error means.
How to Diagnose Intermittent Salesforce Callout Failures (Read timed out, 503s and silent retries)
Why Salesforce callouts fail intermittently when the endpoint looks healthy, the exact exceptions to search for, and a classified retry design in Apex.
sf project deploy validate vs start: which to run and when
Validate then quick for production, start for sandboxes: which sf project deploy command fits each environment and test level, what fails, and how to recover.
Salesforce CLI JWT auth in GitHub Actions: no browser login
Set up headless Salesforce CLI authentication in GitHub Actions using JWT so CI can deploy without browser login prompts.
Salesforce CLI DevOps Playbook: Auth, Deploy, CI/CD Fixes That Actually Work
Salesforce CLI reliability playbook: JWT auth for CI, validate then quick deploy, test levels by org, sandbox deploys without tests, pending deployments.
Why 301 Redirects Break Salesforce Callouts
Learn why 301 redirects cause Salesforce HTTP callouts to fail and discover practical solutions to prevent integration failures.
How to Fix Null Pointer Exceptions in Apex Collection Workflows
Learn how to prevent Apex Null Pointer Exceptions in collection-heavy code with defensive initialization patterns, trade-offs, and a production debugging checklist.