CUSTOM DEVELOPMENT
Code where it earns its place
Declarative first. When the platform can’t do it, we write Apex and LWC that is bulk-safe, tested, documented and yours.
Every line of custom code is a liability you maintain for as long as you own the org. That’s not an argument against code — it’s an argument for writing it deliberately, and for a documented reason.
We use a simple test: if configuration can meet the requirement within acceptable performance and complexity, it wins. Where code is genuinely needed — complex calculation, high-volume processing, integration orchestration, a UI the platform can’t render — we build it to standards that make it safe to hand to any competent engineer later.
What you get
- A written justification for every custom component, kept with the code.
- Bulk-safe by default: no SOQL in loops, no hard-coded IDs, governor limits respected at 10× current volume.
- Test coverage above 85% with meaningful assertions, not coverage padding.
- Source control, CI and automated deployment from day one.
- Documented, readable, and free of one-person dependencies.
- Performance tested against realistic data volumes before release.
Features
Apex classes, triggers and batch/queueable jobs · Trigger frameworks and separation of concerns · Lightning Web Components · Platform Events and async patterns · Custom REST endpoints · Managed and unlocked packages · Jest and Apex test suites · CI/CD with GitHub Actions, Copado or Gearset · Static analysis (PMD) and code review standards · Performance and LDV optimisation
How we run it
01 Requirement challenge — can this be declarative? · 02 Technical design and review · 03 Build with tests · 04 Peer review and static analysis · 05 Volume and regression testing · 06 Release, monitor, document
What you receive
Technical design note per component · Source-controlled code with tests · Static analysis report · Deployment pipeline configuration · Performance test results · Developer documentation and README · Knowledge transfer session
Common questions
Will you take over code someone else wrote?
Yes, after an assessment. We’ll tell you honestly what’s salvageable and what should be rewritten before it’s extended.
Do you use packages?
Unlocked packages for modular org work; managed packages only for products intended for distribution.
How do you keep us from being locked in?
You own the repository from commit one, and every component ships with documentation and tests. Lock-in is a business model, not an engineering necessity.
Can you work in our existing pipeline?
Yes — we’ve worked in Copado, Gearset, Jenkins, GitHub Actions and Azure DevOps.
Start here
Tell us what your CRM is getting wrong
Thirty minutes with a consultant, not a salesperson. You’ll leave the call with at least one thing you can fix yourself — whether or not you hire us.
Prefer email? hello@zeptglobal.com · Typical reply time: one business day