Salesforce Development
Custom LWC, Apex services and Flow automation — bulk-safe, test-covered, architect-reviewed and documented, so the next person to touch it does not start by rewriting it.
01
The problem
Why people call us about this.
A
Deployments fail and nobody is confident enough to fix the failing tests.
B
A contractor built something clever that only they understood.
C
Governor limits bite every time volume goes up.
02
What’s covered
The Salesforce we actually configure.
Custom code is where Salesforce projects quietly accumulate debt. Everything below is built to survive a developer handover and a seasonal release.
03
How it runs
Five phases, and what you see at the end of each.
01 · Week 1
Inventory
What exists, who owns it, and which system is really the source of truth. Almost always surfaces something nobody knew was live.
A written map
02 · Weeks 2–3
Contract
The design in writing, with each decision and its reversal cost named. This is where we argue with the brief — before money is spent.
A signed scope
03 · Middle
Build
Built against the contract and reviewed against it. You see working software every two weeks, in your own sandbox.
Fortnightly demos
04 · Late
Prove
Volume testing at twice expected load, deliberate failure injection, and a replay run with your team watching.
A test evidence pack
05 · Final week
Hand over
Runbook, monitoring, escalation path and a named owner on your side — then a month watching it together before we step back.
Runbook and owner
04
First call
Thirty minutes. Three answers.
You speak to a certified architect, not a sales engineer. No deck, no discovery fee, and no obligation to go further — you leave the call with three things whether you hire us or not.
Whether this is even the right line
About a third of the time it is not, and we say so. Usually the ask is custom development when the real problem sits in the data model underneath.
A shape and a range
Roughly how long, roughly how many people, and the band it falls in. The firm number follows discovery about two weeks later, and it holds.
The two risks we would flag
The things most likely to blow the timeline on a project like yours — named on the call, before anyone has signed anything.
Book it for this week.
Pick a slot directly in the calendar — most questions get answered inside the thirty minutes.
05
FAQ
Asked on nearly every call.
Will we be able to maintain this after you leave?
That is the whole point of how we build. Bulk-safe patterns, real test coverage above 85 per cent rather than gamed coverage, and documentation written for your next admin instead of for us.
Can you work in our existing repository?
Yes — your repo, your branching model, your CI. We follow your conventions rather than importing ours, because the alternative leaves you with two ways of doing everything.
Do you write code when configuration would do?
We argue against code first. About a quarter of the development requests we get are better solved in Flow or with a permission-set change, and saying so early is cheaper for everyone.
How do you handle governor limits?
Everything is bulk-tested at twice expected volume before handover, with limit profiling included in the evidence pack so you can see the headroom rather than take our word for it.
Other lines