Home/Services/Implementation

Build it once, properly.

Sales, Service and Experience Cloud builds that start from your process map rather than from Setup.

Most implementations are judged on whether they went live on time. The ones that matter are judged two years later, when somebody has to change something.

So we design for that day instead. Process mapping before configuration, a data model that survives the second and third use case, and a written record of why each decision went the way it did — because the next engineer inherits your reasoning, not just your object schema.

A configured org is not the deliverable. The deliverable is an org your team can change six months later without calling us.

SCOPE

What the engagement includes

Process mapping before Setup

We map what the business actually does before anyone opens Setup. Half the stated requirements change once that is on paper, and it is far cheaper to change them there.

A data model built for year five

Objects, relationships and a sharing model designed around the use cases you have not asked for yet. Retrofitting those later is where implementations go over budget.

Architecture decision records

Every significant choice written down with the alternatives we rejected and why. Three pages that save your next developer a fortnight of guessing.

Configuration first, code where it earns it

Flow where Flow is right, Apex where it is not. We do not write code to look clever, and we do not avoid it to look cheap.

UAT your business team actually wrote

Test scripts in the language of the people signing off, not a list of API field names. If they cannot read the script they cannot approve the build.

A handover that is a handover

Runbooks, a working session with your admin, and 30 days of warranty while your team finds the questions nobody thought to ask during UAT.

PROCESS

How we work

Org read

Ninety minutes in your Setup with an architect — or in a blank org if this is greenfield. We write down what we see.

Design

Process maps, data model and the architecture decision record, agreed before anyone builds anything.

Build

Configuration and code in a sandbox, in two-week slices you can see, with tests that run in CI.

Go live

Staged cutover with a rollback path, then 30 days of warranty while your team settles in.

FAQ

Questions we get asked

How long does an implementation usually take?

For a single cloud with a clear process, typically 10–16 weeks from the org read to go-live. Multi-cloud or a migration alongside it pushes that out. We would rather give you a range we can hold than a date we cannot.

Can you work alongside our existing admin?

Yes, and it usually goes better when we do. They know the business; we know the platform. The handover at the end is shorter because they were in it from the start.

What if we already started and it has gone wrong?

That is a large share of what we get called in for. We start the same way — an org read — and then tell you honestly what is salvageable and what is cheaper to rebuild. Sometimes the answer is less rework than you fear.

ALL SERVICES

Implementation Support Managed Services

casperlogic

Not sure it needs a full build?

Bring us the process. If it is three fields and a Flow, we will tell you that rather than scope a project around it.

Book a working session

Implementation scoping checklistPDF · 4 KB

NO SLIDE DECK, NO DISCOVERY INVOICE

Let us open Setup and tell you what we actually see.

Ninety minutes with an architect who has shipped on this platform since 2011. You leave with a written read on your org whether or not you hire us.

Book a working session See what we do