Who does the work · all of it
Serhii Skrypnyk.
One person, named.
There is no agency layer and no junior doing the configuration. Where a scope needs more hands than one pair, I bring people I have delivered with before, and the accountability stays with me. The person who answers the first email is the person who writes the data model, builds it, and hands it over. That is the whole argument for the prices on this site, and the whole risk in them, so both are set out below.
Verifiable
Seven Salesforce certifications.
Issued by Salesforce, and every one of them checkable on the Trailblazer profile rather than on my word. Certifications prove that somebody sat an exam, which is worth exactly that much: they are a floor, not a promise.
Platform Administrator
Platform Administrator II
Platform App Builder
Platform Foundations
Agentforce Sales Consultant
Account Engagement Specialist
Account Engagement Consultant
Evidence
What one engagement actually looked like.
Certifications say an exam was passed. This says what happened when the work met a real business, including the decision that mattered most and is usually got wrong.
Who and how long
A general insurance agency in South Carolina, United States. February 2024 to January 2025, twelve months, remote throughout. Sales Cloud and Service Cloud, implemented and then grown as the team grew: one user at the start, thirty-five by the end.
How support was built
Email-to-case at the front, so nothing arrived as somebody's personal inbox. Cases landed in a queue rather than on a named person, and managers pulled from the queue when they had capacity. That one choice is what stops work disappearing into an individual's backlog when they are on leave.
The decision that mattered
Time on each case was tracked with non-working hours excluded. It sounds like a detail and it is the whole difference between a dashboard leadership believes and one they quietly stop opening. Raw elapsed time counts nights, weekends and holidays against the team, so a case opened at 17:00 on Friday looks like a three-day failure. Exclude the hours nobody was working and the same case reads as one hour, which is what actually happened.
What it produced
Live figures on response and resolution that matched what the team experienced, so they could be used to make decisions rather than to argue about the tool. On the sales side, accounts structured and Sales Cloud configured around how the agency actually sells, which is what the seats were added onto as headcount grew.
The client is not named here because the terms on this site promise that nobody is referenced publicly without written consent. The engagement itself is listed on LinkedIn with dates.
Scope
What the work actually is.
Eight years of doing this narrows what you are good at rather than widening it. Here is where the line falls, in both directions.
Done here
- Sales Cloud and Service Cloud implementations and rebuilds, 10 or more of them in mid-market B2B since 2018
- Nonprofit Cloud, where constituents and giving are modelled properly rather than as accounts and opportunities
- Marketing Cloud Account Engagement: scoring, sync, attribution, and migration to Marketing Cloud Next
- Audits that end in a costed order of work, 10 or more across mid-market B2B
- Documentation written as the work happens, so your team can change the system without me
Not done here
- Managed services, or anything that runs indefinitely. Support is sold by the month with an end date, not open ended
- Staff augmentation, where a body is billed by the hour into someone else's plan
- Commerce Cloud, Field Service and Industries clouds. Other people know them better
- Anything above roughly 300 seats, where a partner genuinely delivers better
- Reselling licences. They are bought direct and never marked up
The honest part
When a partner is the better answer.
One person is faster and cheaper right up to the point where it becomes a liability. That point is not a secret, so here it is.
Above roughly 300 seats
Past that size the coordination load stops being technical. You need a project manager holding four workstreams, and that is a role, not an extra hour in my week. A partner does this better and I will say so rather than take the work.
When procurement requires a partner on the invoice
Some organisations cannot buy from an individual, whatever the individual delivers. That is a real constraint and arguing with it wastes everyone's quarter.
When you need cover, not a project
If the requirement is somebody available every day for a year, that is a hire or a managed service. Neither is what this is. A named engagement with a written scope ends; a dependency does not.
Questions
Asked often enough to answer here.
Is a solo Salesforce consultant a risk for a serious project?
It is a real risk and worth naming. There is no bench, so illness or a family emergency moves dates. What reduces the risk is that everything is documented as the work happens rather than at the end, the build lives in your own org from day one, and nothing depends on access only I hold. If I disappeared halfway, another consultant could read the change log and continue.
What happens if the consultant becomes unavailable mid-project?
The written scope, the data model and the running change log are yours and sit in your own systems, not mine. Any competent Salesforce consultant can pick them up. That is the point of writing them during the work instead of after it, and it is why documentation is in the price rather than an addition.
Why work with an individual rather than a Salesforce partner?
Because at mid-market size you are paying a partner for a delivery manager, a solution architect who writes a document a junior then configures, and a margin on top. Removing those three is why the prices on this site sit at the bottom of the published band. Above roughly 300 seats the calculation reverses and a partner is genuinely better.
Where is the business registered, and who is the contracting party?
Serhii Skrypnyk, a sole trader registered in Ukraine as an individual entrepreneur, invoicing in euro. Work is remote, worldwide. For engagements involving personal data the Data Processing Addendum applies and is written to satisfy GDPR Article 28, which is what procurement usually asks for first.
The fastest way to judge this is to use it.
Every tool on this site produces a real number without a form, a call, or an email address. Whether the person behind it is any good is a question the output answers better than a biography.
Serhii Skrypnyk · Senior Salesforce Administrator and developer · 7 Salesforce certifications · on the platform since 2018