Services · Sales, Service and Marketing Cloud
Five things get asked for.
They are not the same job.
Measuring an org, building one, moving one and repairing one need different work, different sequences and different prices. Below is each of them with its figure, its duration and a tool that scopes it in your browser before you speak to anybody.
Measure
Agentforce readiness
Four measures against reports you already have: stale pipeline, duplicate account identity, activity capture and source attribution. A verdict of A, B or C and the dollar exposure of whatever is broken.
Free in the browser · €500 for the full check
Repair
Something is already broken
Six faults that account for almost everything people arrive with: scoring, sync, attribution, automation, adoption, and an org nobody can change. Each names the cause it usually turns out to be and a check you can run yourself.
From €2,000 · 2 to 4 weeks per fault
Build
Sales Cloud implementation
Written data model, objects and stages, sharing, reports, migration and integrations. Base covers 25 seats and six weeks; everything above that is a line you can strike out.
From €8,700 · 6 to 27 weeks by scope
Build
Service Cloud implementation
Case model, queues, routing and SLAs, priced per channel because a portal costs seven times what email-to-case does. Knowledge base scoped separately, and it matters more than it looks.
From €7,250 · 6 to 37 weeks by scope
Build
Nonprofit Cloud implementation
Constituents and households rather than accounts and contacts, recurring and restricted giving, programme delivery and the funder reports somebody else decided the format of.
From €7,250 · 7 to 25 weeks by scope
Move
Pardot to Marketing Cloud Next
Prospect history, programs, forms, scoring and the connector. Includes an honest answer on whether this is the right quarter, and sometimes on whether to move at all.
From €6,000 · 7 to 25 weeks by scope
Fix
What if none of those is the problem?
A large share of the work that arrives here is not an implementation at all. It is a system that was built correctly three years ago and has drifted since, and it needs a diagnosis before it needs a project.
Lead scoring nobody trusts
The most common single complaint. Scoring tuned for a buying process that has since changed, awarding points for behaviour that no longer indicates intent, with the top-scoring prospects accumulating value from 2023 activity. Back-testing against closed-won deals is what fixes it, not adding rules.
Sync that fails silently
Prospects that never reach Salesforce, conversions that drop records, an error queue nobody watches. It is rarely one cause, and the fix begins with measuring how many records are actually affected rather than guessing.
Automation that fights itself
Workflow rules, process builders and flows written by four people over five years, all firing on the same record in an order nobody has traced. This is what makes a rebuild cost more than a greenfield build, and it is why an audit belongs in front of one.
Reporting the CFO does not believe
Marketing reports one number, finance reports another, and the board is shown a third. Almost always an attribution and data model problem rather than a reporting one, which is why building more dashboards does not solve it.
All four are scoped the same way: measure, price the repair, then decide. The €500 readiness check produces that in one working day, arrives within three, and is credited in full against whatever follows.
Which one
How do I know which service I need?
Three questions settle it more reliably than a discovery call, which is why they are on the home page rather than in a meeting.
Do you already run Salesforce?
If not, this is a build and the question is which cloud first. If yes, the next question matters more than this one.
Is what you have trusted?
If the numbers are believed and the team uses it, any new work sits on a sound base. If not, measure before building anything on top, because a new layer inherits whatever is underneath.
Is there a date attached?
A renewal, an end of life notice, a board commitment. A real date changes the sequence rather than the price: anything with an external dependency moves to the front and anything that can slip moves behind it.
Common to all of them
What every engagement includes.
Always
- A written scope agreed before anything is built
- Discovery that ends in a data model document you keep
- Sandbox first, with your access from day one
- Documentation written as the work happens
- Sixty days of support after handover, never invoiced separately
Never
- A retainer, on any engagement
- Hourly billing inside the signed scope
- A proprietary layer that stops working when invoicing stops
- Hand-off to a junior consultant mid-project
- A price that moves upward after signature
Scope it before you speak to anyone.
Every service above has a tool that produces an itemised figure and a phase plan in your browser. Bring the document to the call and we start from the number.
Serhii Skrypnyk · Senior Salesforce Administrator and developer · 7 Salesforce certifications · on the platform since 2018. Reviewed 20 August 2026.
Questions
Asked often enough to answer here.
Which Salesforce service do we need?
Three questions settle it: whether Salesforce is already running, whether the numbers in it are trusted, and whether a date is attached. No Salesforce means a build. Running but not trusted means measure before building anything on top. A real date changes the sequence rather than the price.
What is included in every engagement?
A written scope agreed before anything is built, discovery ending in a data model document, sandbox-first delivery with client access from day one, documentation written as the work happens, and sixty days of support after handover at no extra charge.
What if the problem is not an implementation?
Much of the work is repair rather than build: lead scoring nobody trusts, sync failing silently, automation written by four people over five years, or reporting the CFO does not believe. All four are scoped by measuring first, pricing the repair, then deciding.
Is there a retainer or support contract?
No retainer is offered on any engagement. Every piece of work has a written scope, a fixed price and an end date, and nothing stops functioning when the engagement ends because everything is built inside the client's own org.