Salesforce CI/CD & Release Engineering

I design, build, and own release pipelines for enterprise Salesforce orgs — GitHub Actions, SFDX, 1GP/2GP packaging, and quality gates an auditor can't talk their way around. This is the discipline I've applied at a regulated UK fintech, a Big-4 consultancy, and a global SaaS platform shipping to 400+ production orgs.

When You Need This

  • A compliance audit is approaching and your deployment history lives in a spreadsheet.
  • Releases are manual change sets — they take a full day, and they still break.
  • You bought a DevOps tool, but nobody wired it into a real branching strategy.
  • You ship managed packages and every release cycle is hand-cranked.

What Gets Built

  • CI/CD on GitHub Actions + SFDX: validate on pull request, delta deployments, automated Apex and Jest tests
  • Branching and environment strategy matched to your team size and release cadence
  • 1GP/2GP packaging strategy, including push-upgrade automation for managed packages
  • Non-bypassable quality gates: static analysis, coverage thresholds, protected branches, required reviews
  • Segregation of duties and audit-ready release logs
  • Runbook and full team handover — the pipeline is yours, not a dependency on me

Engagements

SF CI/CD Health Check

€1,500 – 2,500

Audit your pipeline, branching strategy, and release process. Written report + prioritised roadmap. Ideal before a major release cycle.

  • Pipeline + branching audit
  • Written findings report
  • Prioritised roadmap
  • 1-hour debrief call
Get in Touch
Start here

Release Governance Setup

€6,000 – 10,000

Production-grade CI/CD pipeline end-to-end. Branching strategy, automated testing, quality gates — built to survive audits.

  • GitHub Actions pipeline build
  • Branching + packaging strategy
  • Quality gates + test automation
  • Runbook + team handover
Get in Touch

Proof

At Ebury (UK fintech), I rebuilt CI/CD for a 1,500-user org under banking audit — the pipeline passed external compliance review on first submission.

Read the Ebury case study

At a global SaaS platform, I automated 1GP/2GP push-upgrades across 400+ production orgs on GitHub Actions.

Read the 400-org case study

The tooling is public: reusable GitHub Actions modules, Salesforce CI Docker images, and an enterprise SFDX template. Certified Development Lifecycle & Deployment Designer.

Frequently Asked Questions

Should we use Copado or Gearset instead of GitHub Actions?

If a licensed DevOps tool already fits your team, keep it — I make it governed. My default is GitHub Actions + SFDX because the pipeline lives in your repo: versionable, testable, license-free, and auditable as code.

How long does a Release Governance Setup take?

Typically 3–6 weeks part-time, working alongside your team. It ends with a runbook and a handover, not a dependency on me.

Do you replace our existing pipeline or fix it?

Audit first — that's what the CI/CD Health Check is for. I replace only the parts that fail the audit; working automation stays.

What does audit-ready actually mean?

Every production change traceable to an approved pull request, enforced by branch protection rather than policy documents — with segregation of duties between author and approver, and release logs an external reviewer can walk through.

Tell me about your release process

Book a 30-minute call — you'll leave with an honest read on whether I can help and what it would cost. No pitch, no pressure.

Book a Discovery Call Email About Scope

What happens next

  1. 1. A 30-minute discovery call about your situation.
  2. 2. A scheduled start date — typically within 2–4 weeks.

Related: Salesforce integration architecture · fractional technical leadership