Deploy Joy - Salesforce Solutions Services
About Jasmine
I spent years watching the same thing happen. Salesforce sells a vision, a partner scopes a build, and somewhere between the two the organisation ends up with a system that answers a question nobody asked. I've been on both sides of that — pre-sales and solution engineering inside the ecosystem, then implementation, QA and delivery — and the gap is almost always in the room before anyone writes a line of config.
So I set up on my own. I don't resell licences, I'm not a partner, and I don't get paid more if your project gets bigger. That's the whole point.
Where I came from
I am originally from New Zealand and I live and work in the UK. I have built a career across different countries, teams and cultures, and it taught me to pay as much attention to organisations as to systems — the same configuration lands very differently in two places with different habits.
Over a decade in the Salesforce ecosystem, and on both sides of it: pre-sales and solution engineering on Salesforce’s side of the table, then implementation, QA and delivery on the customer’s.
That is why I can read a proposal and tell you which parts of it are real.
Certifications
I hold five active Salesforce certifications.
Platform Administrator, Platform App Builder, Experience Cloud Consultant, Agentforce Sales Consultant and Agentforce Service Consultant.
You can verify all five on my Trailblazer profile, along with what I am working through now.
The Agentforce ones matter for a specific reason. They are also why I will tell you when AI is not the answer to your problem, and that is easier to say from the inside of the training than from outside it.
How I work
I do not do fixed-cost projects. Every engagement is timeboxed: you buy an agreed number of days, and when those days are used the engagement ends.
That is blunt written down, and it is the fairest arrangement I have found. You know your maximum before you commit, and neither of us ends up in the argument about whether something was in scope.
In practice that means:
- Scope agreed in writing before anything is built
- A list of what I need from you before day one — sandbox access, the relevant documents, and half an hour each with the people who actually know the process
- Documentation and training as part of delivery, not an afterthought
- Named people only — if someone else is doing the build, you know who before they start
- An honest no when the work is not something I am right for
I am independent, not isolated. Where a build genuinely needs specialism or capacity I do not have, I bring in people I trust.
The point of all of it is that your team owns the system after I have gone.
You don’t need to be a Salesforce expert. My role is to help you understand your options and make confident decisions before anything is built.
If you’d like to understand whether I’m the right person to support your organisation — or simply want to talk through a challenge — get in touch.