Gusto: Salesforce Engineering

Success Story

Salesforce Engineering for Gusto's HR Operations

Zoolatech provided a 5-person nearshore Salesforce engineering team supporting Service Cloud, Sales Cloud, integrations, DevOps, Benefits Operations, and production reliability.

Nearshore delivery

with 5 senior engineers aligned closer to US product and engineering teams.

Reliable operations

across CRM operations, integrations, and deployments.

Technologies

Salesforce Service Cloud

Salesforce Sales Cloud

Apex

Lightning Web Components

Salesforce Flow

Salesforce APIs

MuleSoft

Kafka

Ruby on Rails

Buildkite

GitHub

SFDX

Datadog

Terraform

Claude Code

Jira

Notion

Slack

Expertise

Service Cloud

Integrations

CI/CD

Have a Similar Challenge?

Explore how we can support your team.

Contact Sales

Engineering capacity

Growing Salesforce workstreams required more senior engineering support across Service Cloud, Sales Cloud, Benefits team operations, and revenue systems.

Nearshore alignment

Gusto was replacing offshore capacity with engineers closer to US time zones to improve collaboration and responsiveness.

Complex integrations

Salesforce exchanged data with Ruby-based HR platforms through MuleSoft and Kafka, increasing synchronization and data consistency complexity.

Operational reliability

Support routing, email automation, case handling, Benefits workflows, and CRM records required continuous production improvements.

Have a Similar Challenge?

Explore how we can support your team.

Contact Sales

Nearshore collaboration

Zoolatech provided engineers closer to US teams, supporting faster communication, daily collaboration, and production responsiveness.

Senior Salesforce expertise

The team contributed across Apex, LWC, Flows, Omni-Channel, MuleSoft, Kafka, DevOps, bulk data operations, SEV response, and production support.

Zoolatech is a senior-heavy engineering firm with Silicon Valley roots and a Miami HQ, specializing in legacy modernization, system re-architecture, and AI deployment to drive long-term, compounding value.

2017

Year Founded

600+

Employees

96%

Client Satisfaction

Phase 1

Business analysis & backlog refinement

The business system analysts translated stakeholder requests into detailed Jira tickets supported by documentation, recorded walkthroughs, reports, and acceptance criteria. Before the development began, technical leads and engineers reviewed each requirement to validate feasibility, refine implementation approaches, and identify architectural considerations.

Phase 2

Salesforce development

Engineers enhanced Gusto's Salesforce platform following established engineering standards and reusable architectural patterns. Work included:

Apex development and automation
Lightning Web Components enhancements
MuleSoft and Kafka integrations
Omni-Channel routing improvements
Performance and reliability optimizations

Phase 3

Business validation

Completed functionality was demonstrated to the business system analysts in sandbox environments for functional validation. The feedback was incorporated iteratively until the solution met business requirements before entering technical review.

Phase 4

Quality assurance & code review

Every change passed through multiple quality gates before production:

Business validation
AI-assisted code review
GitHub peer review
Technical approval
Automated CI/CD validation

Phase 5

Production deployment

Approved releases were deployed through GitHub Actions, Buildkite, and SFDX pipelines. Following deployment, engineers monitored production behavior, supported SEV incidents when necessary, and continued improving platform reliability through incremental enhancements.

Nearshore engineering helped Gusto improve Salesforce delivery, integrations, and operational reliability.

Deployment automation

Replaced Gearset with Buildkite, GitHub Actions, and SFDX, enabling automated nightly production deployments and improved revenue-team version control.

Event-driven synchronization

Implemented Kafka-based ZenPayroll ↔ Salesforce synchronization through MuleSoft to support cross-platform data exchange and new-product workflows.

Support routing reliability

Restored live chat intake during a SEV, fixed after-hours case handling, improved Omni-Channel routing, added duplicate guards, fixed Tier-2 transfers, and improved auto-close stamping.

Benefits operations

Implemented ADR-006 email compliance changes, removed BCC behavior, fixed Email-to-Case threading, added weekend-send protection, improved Benefits automation, and optimized performance validation.

Option	Risk	Mitigation
AI-generated code affecting existing workflows	AI-generated code could satisfy a ticket while unintentionally affecting existing workflows.	Gusto combined AI-assisted reviews with human PR reviews, BSA validation, CI checks, and rollback procedures.
Incomplete process documentation	Incomplete documentation increased the likelihood of AI-generated implementation assumptions.	Engineers created Claude Code skills, requested implementation drafts before changes, and manually verified business logic.
Complex cross-platform integrations	Dependencies across Salesforce, MuleSoft, Kafka, and Ruby increased integration complexity and production risk.	Technical reviews, standardized integration patterns, sandbox validation, and staged releases reduced production exposure.
Salesforce deployment complexity	Revenue deployments required Salesforce-specific version control and release management.	Buildkite-based automation replaced Gearset and standardized deployments through GitHub and SFDX.