Not sure where to start?

A five-day Health Check

Fixed price. One honest report on your org, ranked by cost and risk. Yours to keep whether or not you hire us.

Request a Health Check

Selected work

Quotes from six days to four hours

How a components manufacturer moved tacit pricing rules out of one person’s head and into CPQ.

Read the case study

Salesforce consulting & CRM engineering

Salesforce that people actually use

Most CRM projects don’t fail at go-live. They fail in month seven, when the workarounds start and the reports stop matching reality. We build Salesforce around the way your teams already make decisions — then we stay to keep it that way.

Certified consultants · Sales · Service · Experience · Marketing · Data Cloud · Agentforce

A customer record travelling through its lifecycle Four record cards — Lead, Opportunity, Account and Case — sit on an elliptical orbit. A single token moves between them, pausing at each stage, with a small chart and checklist panel floating above.

Why ZeptGlobal

We’re judged on what your team does on Tuesday

Anyone can ship a configuration. The question is whether the people who have to live in it will choose it over a spreadsheet.

Adoption is the deliverable

We define success as usage before we define scope. Every engagement carries an adoption target, measured in the org and reported monthly.

How we measure it

Architecture that survives version 2

Declarative first, code where it earns its place. Documented objects, bulk-safe automation, and an org you can hand to anyone.

Our standards

One team, build through run

The consultants who design it are the consultants who support it. No handover cliff, no fresh discovery six weeks after go-live.

Managed services

Cloud coverage

The clouds we build in every week

We don’t claim the whole product suite. These are the six we run in production, with certified consultants on each.

Sectors

Nine sectors, nine sets of constraints

A nonprofit’s data model is not a manufacturer’s with different labels. We start from the constraint that actually binds you.

Measured, not claimed

What our engagements have moved

140+

Salesforce orgs delivered or rescued

↑ median
31%

Lift in weekly active CRM users, 90 days after go-live

4.2 hrs

Average weekly admin time returned per rep

<30 min

Median first response on a P1 support ticket

94%

Client retention into a second year of managed services

Figures aggregated across engagements and rounded. Individual results vary by scope and starting maturity.

How we run it

Six stages, and you can see all of them

No black-box phase. The backlog, the burn and the risk log are shared from week one.

  1. 01

    Discover · 1–2 weeks

    Sit with the people who’ll use it

    Process mapping, systems inventory, data profiling, and a written statement of what “better” means in numbers.

  2. 02

    Design · 2–3 weeks

    Decide the shape before anyone builds

    Data model, security model, automation map, integration contracts. You approve a solution design document, not a slide.

  3. 03

    Build · two-week sprints

    Working software every fortnight

    Declarative first, code where it earns its place. Demo at the end of every sprint, in your org, with your data.

  4. 04

    Migrate & validate

    Two rehearsals before production

    Cleanse, map, dry-run, reconcile. Nothing loads live without a reconciliation report and a tested rollback point.

  5. 05

    Launch & enable

    Make the first week uneventful

    Role-based training, floor-walking in week one, a named person to ask, and a 30-day hypercare window.

  6. 06

    Improve · ongoing

    Stop the slow decline

    Monthly release train, adoption reporting, and a quarterly review of what the org should stop doing.

Selected work

Three problems, three orgs, three scorecards

“We’d already paid for one implementation. They spent the first fortnight telling us which half of it to keep — that alone paid for the engagement.”
ODOperations Director · Precision components manufacturer
“They talked our advisers out of two features they’d asked for and explained why. That’s when I started trusting the roadmap.”
CTChief Technology Officer · Wealth management firm

Illustrative examples. Replace with real, permissioned client work before publishing.

Common questions

Before you get on a call

How much does a Salesforce implementation cost?

For a first implementation on one cloud, most of our engagements land between a 6-week and a 16-week build. We price by sprint, so the honest answer after a 30-minute call is a range and the two variables that move it — usually data quality and how many systems have to talk to each other.

How long before we see anything working?

You’ll see working configuration in your own sandbox at the end of sprint one, typically week three. We don’t do six-week analysis phases with nothing shipped.

We already have Salesforce and it’s a mess. Do we start again?

Almost never. A re-implementation throws away years of accumulated business logic along with the mess. Our Health Check separates what’s load-bearing from what’s abandoned, and most rescues are cheaper than a rebuild.

Do you work with our existing admin or replace them?

We work with them. Your admin knows things about your business we’d take months to learn. Where the gap is capability rather than capacity, we train rather than displace.

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