TECHNOLOGY
What we build with, and why
Salesforce is the platform. These are the tools around it that keep an org fast, testable and connected — plus an honest note on where each one earns its cost.
Section — Platform
| Technology | What we use it for | When we don’t |
|---|---|---|
| Sales Cloud | Pipeline, forecasting, activity capture, territory | — |
| Service Cloud | Cases, routing, console, knowledge, entitlements | — |
| Experience Cloud | Customer, partner and member portals | When a marketing site is all that’s needed — use a CMS |
| Marketing Cloud | High-volume, multi-channel, complex consent | Lower-volume B2B nurture — Account Engagement is cheaper |
| Data Cloud | Identity resolution, unified profile, activation | When two clean sources and a good match rule will do |
| Revenue Cloud / CPQ | Configurable products, governed discounting | Simple catalogues — price books are enough |
| Agentforce | Bounded, grounded agent tasks with escalation | Open-ended, high-risk conversation |
| Flow | Declarative automation, first choice | Very high volume or complex logic — Apex is cleaner |
| Apex | Bulk processing, orchestration, complex calculation | Anything Flow does adequately |
| Lightning Web Components | Task-shaped UI the standard pages can’t express | When a page layout change would have done |
Section — Integration
MuleSoft · Platform Events and Change Data Capture · REST, Composite and Bulk API 2.0 · Salesforce Connect / External Objects · Webhooks with signature verification · iPaaS (Workato, Boomi) · Message queues and Kafka bridges · SFTP for legacy batch · HL7 / FHIR for healthcare
Our rule: every interface gets a written contract — fields, direction, ownership, frequency, conflict resolution, error handling, replay, and a named person who is paged.
Section — Data & analytics
Snowflake · BigQuery · Databricks · dbt · Tableau · CRM Analytics · Salesforce reports and dashboards (still the right answer more often than people expect)
Section — DevOps & quality
Git (GitHub, GitLab, Azure DevOps) · Salesforce CLI / SFDX · Unlocked packages · Copado · Gearset · GitHub Actions and Jenkins · Jest · Apex test frameworks · PMD static analysis · Scratch orgs and sandbox seeding
Standards we hold to: source control from commit one · peer review on every change · 85%+ meaningful Apex coverage · no hard-coded IDs · bulk-safe by default · static analysis in CI · a documented rollback for every release.
Section — Security & operations
Shield Platform Encryption · Event Monitoring · Field Audit Trail · Permission set groups over profiles · Login IP and session policies · SSO / SCIM (Okta, Entra ID) · Backup and recovery tooling with tested restores · Sandbox data masking
Section — How we choose
Four questions before adding anything to a client’s stack:
- Does it remove work, or move it? Tools that relocate effort look like progress for a quarter.
- Who maintains it in year two? If the answer is only us, that’s a strike against it.
- What’s the exit? Every tool needs a documented way out.
- Is the cheaper option genuinely inadequate, or just less interesting?
Want a second opinion on your stack?
Bring your architecture diagram. We’ll tell you which parts are doing real work.
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