Eight engagements. You end up owning it, every time.

The build, done so your admins can still change it.

Every engagement starts by watching the process before we touch a field. Then we build it — objects, flows, Lightning Web Components, integrations, migrations — in a shape your team can read six months later. Over-customised orgs are the other half of this work: we untangle trigger conflicts and redundant automation as readily as we add to them.

1. 01WorkshopWe sit with the people doing the work and map what actually happens, not what the process document says.
2. 02Architecture noteWhat we will build, what we will not, and what it costs to change our minds later. You approve this before any code.
3. 03Two-week incrementsYou see it working in a sandbox at the end of each one. No six-week silences.
4. 04HandoverRepository, deployment runbook, and a working session with your admins on the parts they will own.

StackCRM customisation · Flows & automation · Lightning Web Components · REST / SOAP / Platform Events · Data migration

Shape

Fixed-scope project

Typical length

6–12 weeks

Priced

Fixed scope, or time & materials

Starts with

A workshop, not a proposal

You keep

Repository, runbook, admin training

The Heroku side, built so it outlasts the roadmap.

Heroku Connect at the volume you actually have, Postgres as the scale tier, and the long-running jobs Apex was never going to run. We build that side and we hand back the mappings, the runbook and the cost baseline. Since February 2026 the platform ships no new features, which changes nothing about whether your app works and everything about how long you should expect to own it — so every engagement here ends with that question answered in writing rather than left for a board meeting.

1. 01Estate reviewWhat runs, what it costs, what it syncs, and which part of it is one traffic spike away from a bad afternoon.
2. 02Integration designREST, Platform Events, RabbitMQ or Heroku Connect — chosen per workload, with the reason written down and the failure mode named.
3. 03BuildDynos, workers and the queue between them; Connect mappings with external IDs chosen before the first sync; Postgres indexed for the reads you will actually make.
4. 04Scale & cost passRun it under load, then size it. Dyno plans and add-ons reviewed against real usage, sync lag and error counts put on a dashboard.
5. 05HandoverRepository, runbook, the Connect mapping document, and the written answer on whether to stay, invest or plan the move.

StackHeroku Connect · Heroku Postgres · Web & worker dynos · RabbitMQ / Redis · Platform Events · Node.js / Java · Puppeteer

Shape

Fixed-scope project

Typical length

8–16 weeks

Priced

Fixed scope, or time & materials

Starts with

An estate review

You keep

Repository, runbook, Connect mappings, cost baseline

Get through Security Review the first time.

Building for the AppExchange is not org work with a namespace on it. Packaging tier, namespace, edition compatibility and subscriber lifecycle are decisions that are expensive to reverse, and Security Review is where the unprepared lose a quarter. We have shipped managed packages and know which of those decisions bite.

1. 01Packaging decision1GP or 2GP, namespace registration, and how the package splits — settled before the first commit.
2. 02BuildMulti-edition patterns, CRUD/FLS on every query and DML, scratch-org CI from day one.
3. 03Review preparationPMD static analysis on an AppExchange-tuned ruleset, then a manual pass for XSS and SOQL injection.
4. 04SubmissionWe fill out the form, answer the reviewer, and coordinate resubmission if it comes back.
5. 05Listing & licensingLMA, trials that expire gracefully, seat enforcement, and the listing copy buyers respond to.

Stack1GP & 2GP · Namespace strategy · PMD + manual audit · LMA & entitlements · Scratch-org CI/CD · Release readiness

Shape

Project, then retainer at launch

Typical length

12–24 weeks

Priced

Per phase

Starts with

A packaging decision

You keep

Package, CI pipeline, submission record

One API layer, so your systems stop talking point-to-point.

Point-to-point integrations are cheap to build and expensive to own: every system you add multiplies the connections, and nobody can say what breaks when one goes down. API-led connectivity puts three named layers between your systems, so a change lands in one place instead of six. We design the layers, build them, and document the Exchange portal well enough that your team adds the next API without calling us.

1. 01Connection auditEvery system, every integration that already exists, and what each one actually moves. Usually the first honest map anyone has had.
2. 02System APIsOne per source of record — Salesforce, ERP, HCM. Nothing business-specific, so they outlive the processes built on top of them.
3. 03Process APIsWhere the business logic lives. Order-to-cash, lead-to-quote, composed from the system layer rather than wired to it.
4. 04Experience APIsShaped for whoever consumes them: the mobile app, the partner portal, the Salesforce org.
5. 05HandoverExchange portal with specs and examples, API policies applied, Anypoint Monitoring dashboards and dead-letter queues wired, runbook written.

StackAPI-led connectivity · Anypoint Platform · Anypoint MQ · Platform Events · Change Data Capture · RAML / OAS · Exchange

Shape

Fixed-scope project

Typical length

8–16 weeks

Priced

Per layer, scoped from the audit

Starts with

A connection audit

You keep

Anypoint repo, API specs, policies, dashboards, runbook

Automate the systems that never got an API.

Some systems cannot be integrated, only operated: a supplier portal with no API, a mainframe screen, a PDF somebody rekeys into Salesforce every morning. RPA drives those the way a person does, except at 3am and without transcription errors. We build the bots in MuleSoft RPA so they run on the same Anypoint platform as your integrations — one place to monitor, one place to alert — instead of becoming a second automation tool nobody governs.

1. 01Process captureWe sit with whoever does the work today and record it. What looks like one process is usually three, and one of them should not exist at all.
2. 02Bot buildWe record it in RPA Builder and write the exception paths deliberately, instead of discovering them in production.
3. 03Attended or unattendedAttended runs beside a person for the judgement calls; unattended runs on a schedule. Most processes want one of each, split at the decision point.
4. 04Wired into AnypointBots triggered by, and reporting into, the same integration layer — so a bot failure raises the same alert everything else does.
5. 05HandoverBot definitions in your own tenancy, an exception runbook, and the process documentation the capture produced.

A bot breaks when somebody changes the screen it drives. That maintenance is real and it is ongoing — it belongs in the retainer below, not hidden inside this project’s price.

StackMuleSoft RPA Builder · RPA Manager · Attended & unattended bots · Document processing · Anypoint triggers

Shape

Fixed-scope project

Typical length

4–8 weeks per process

Priced

Per process automated

Starts with

A process capture

You keep

Bot definitions, exception runbook, process docs

The workloads that do not belong inside Salesforce.

Heavy compute, long-term storage, cross-system analytics, and anything that would eat your API limits belongs next to Salesforce rather than inside it. We architect that side properly the first time — VPC, IAM, infrastructure as code — so the account is auditable and the bill does not surprise you in month four. Cost work is part of the design here, not a clean-up engagement we sell you afterwards.

1. 01Architecture reviewWhat you run now, what it costs, and which parts of it Salesforce should stop doing.
2. 02FoundationVPC, subnets, IAM roles and guardrails, written as Terraform or CDK so the account can be rebuilt from the repository.
3. 03WorkloadsServerless processing of Platform Events, a migration off a legacy system, or the analytics layer — whichever the review picked.
4. 04Reporting layerQuickSight, Athena or Snowflake, reading the cross-system view Salesforce alone cannot give you.
5. 05HandoverInfrastructure repository, budgets and cost alerts set, access model documented, runbook written.

StackVPC & IAM · Terraform / CDK · Lambda · Platform Events · S3 lifecycle · QuickSight / Athena / Snowflake · Cost alerts

Shape

Fixed-scope project

Typical length

4–12 weeks

Priced

Scoped from the architecture review

Starts with

An architecture review

You keep

Infrastructure repo, cost alerts, access model, runbook

Move data between Salesforce and everything else, on a schedule that recovers itself.

Salesforce API limits make naive syncs brittle the moment volume arrives. Airflow gives the job a dependency graph, automatic retry with backoff, and an audit trail of every run. We write the DAGs, hand you the repository with its CI, and train your team to extend them. We build them idempotent, so a re-run is always safe, and to carry 50M+ records a day with sub-30-minute incrementals.

1. 01Source auditWhich systems, which objects, what volume, and how fresh the data actually has to be.
2. 02Bronze — raw extractBulk API 2.0 into S3 or PostgreSQL. No transformation, full fidelity, timestamped for point-in-time replay.
3. 03Silver — cleansedDeduped and typed. Salesforce IDs resolved to business keys, picklists normalised, field validation applied.
4. 04Gold — business-readyPipeline by account, case resolution, conversion funnels — loaded into Snowflake or Redshift for the BI tools you already have.
5. 05HandoverDAG repository with CI/CD, RBAC configured, failure and SLA alerts wired, runbook written.

StackBulk API 2.0 · Bi-directional sync · Heroku · AWS MWAA · Self-hosted K8s · Snowflake / Redshift

Shape

Fixed-scope project

Typical length

6–10 weeks

Priced

Fixed scope, per pipeline

Starts with

A source audit

You keep

DAG repository, CI/CD, alerts, runbook

Keep the org healthy between projects.

Salesforce ships three releases a year, your business changes more often than that, and integrations rot quietly. A retainer buys named response times, hours that flex between fixing and building, and a quarterly review that tells you what is accumulating before it breaks. Bugs come back with a written root cause, not just a patch.

1. 01Org health reviewWe read the org first: profiles, sharing, automation debt, governor-limit trends. You get the report whether or not you continue.
2. 02Triage & responseEvery ticket triaged against a named response window. P1 emergency response is unlimited on every tier.
3. 03EnhancementsRetainer hours flex — the same hours cover a broken flow this week and a new report next week.
4. 04Release testingSandbox testing ahead of each Salesforce release, so Spring does not surprise you in production. Then it repeats.

Initial response, written into the contract — not the sales deck. Unlimited P1 on Essentials, Growth and Enterprise alike.

TiersEssentials, 10 hrs/mo · Growth, 20 hrs/mo · Enterprise, 40+ hrs/mo · Quarterly health review · Release management

Shape

Monthly retainer

Term

Rolling month

Priced

By tier, hours flex within it

Starts with

An org health review

You keep

Health reports, ticket history, runbooks