Implementation, custom development and agent builds on Salesforce, including work alongside an existing Dynamics estate.
We map the systems and processes you have now, agree the scope worth doing first, and put a phased plan against it.
We configure and build what is in scope, then wire it to the systems either side of it.
Data is migrated and reconciled against source totals, then tested and signed off before anyone relies on it.
We run the cutover, stabilise it, document what was built and hand it to your team.
Order of magnitude, not a quote. We will not price your programme before we have read your configuration, but you should be able to tell from these whether we are in your range before you spend a meeting finding out.
2 to 3 weeks
$8k to $15k
We go through the estate and the processes around it, and come back with the gaps, the options and what each one costs to close. You own the output whether or not we do the work.
8 to 16 weeks, phased
$40k to $200k, by platform
A defined piece of work with a fixed scope, a named team and a go-live date: a module, a migration, an integration set or a reporting layer. Where the work sits inside one country and one operating model, this is usually the right shape and the cheapest way to prove the platform.
9 to 18 months, phased in country waves
From $350k
A multi-entity or multi-country rollout run with programme governance: a global template designed once, then deployed in country waves with the localisation, statutory reporting and tax obligations sequenced ahead of each go-live. It comes with a programme lead, a template change process and a deployment lead per wave, because a rollout of this shape fails on governance long before it fails on configuration.
Rolling, minimum 3 months
$14k to $28k per month
Ongoing senior capacity that sits inside your programme under your delivery lead, extending and maintaining the estate alongside your own team.
Usually not. Most orgs need a subset removed, a subset rebuilt and the rest left alone. The review tells you which is which, with the cost of each, before anyone commits to a rebuild.
Yes. We take a defined workstream with its own scope and release train, so there is no ambiguity over who owns what.
Sometimes not, and we will say so. It earns its place where there is a repetitive task with a clear completion signal. Where there is not, it produces demos rather than results.
Related
Bring the process that is breaking and we will tell you what it takes to fix it, including when the answer is not a project.
