CAPABILITY 01 / 05
Salesforce
We build on the platform the way Salesforce intends it to be built — declarative first, Apex where it earns its place, everything tested and audited.
THE POSITION
Salesforce work fails in one of two ways: an org automated into spaghetti by admins under deadline, or a platform treated like a generic database by developers who never learned it. We work the narrow path between — governor limits, bulkification, order of execution, and the Lightning Design System are the grammar, not the fine print.
Our flagship build, Meridian, is the pattern in production: flow orchestration for the visible logic, one Apex service for the decisions that need real code, an LWC console for the humans, and field history for the auditors.
We build in Salesforce’s design language, not against it.
Service ConsoleService Request
SR-00412 — Voucher Request
- Status
- In Approval
- Amount
- ₹ 48,200
- Entitlement
- Premier — Active
- Owner
- Approval Queue · Tier 2
- SLA
- 3 h 41 m remaining
- Coverage
- 92% · 40 scenarios
RENDERED IN OUR CODE, IN THEIR LANGUAGE — PATH, FLOW CANVAS & RECORD PAGE PER SLDS. SALESFORCE AND RELATED MARKS ARE TRADEMARKS OF SALESFORCE, INC.
CLOUD COVERAGE
- Sales Cloud
- Service Cloud
- Experience Cloud
- Platform / Custom Apps
CREDENTIALS
- Salesforce Certified Platform Developer I
- Salesforce Certified Administrator
- Trailhead — Apex & LWC specialist badges
The declarative backbone — visible logic the whole team can read
For decision engines and integrations — always bulkified, always tested
Native-feeling UI inside the platform, SLDS-compliant
Real-time messaging inside and out of the org
SFDX + GitSource-driven orgs — no change exists unless it’s in version control
PHASE 01
Org autopsy
We read the org before we touch it — automation inventory, limits exposure, debt map.
PHASE 02
Data model first
Objects and relationships are the foundation; we design them before any automation.
PHASE 03
Declarative + Apex split
Each rule is assigned a home — flow or code — with the reasoning written down.
PHASE 04
Test scenarios as spec
Named scenarios become the contract; coverage measures rules proven, not lines.