Hi, I'm Chris Doyle
I'm a Salesforce consultant. I untangle messy orgs, build things people actually use, and try very hard not to say "synergy" in meetings.
A bit about me.
I've been working with Salesforce for over twelve years now. Most of that has been Sales Cloud and Service Cloud — sales teams who want a straight answer about what's actually in the pipeline, service teams quietly drowning in cases — plus a fair chunk of Nonprofit Cloud, which is the same set of problems with a tighter budget and better reasons.
The job is less technical than people expect. Most of it is sitting with the people who use the thing every day and working out what they actually need, as opposed to what got written down in a requirements doc eighteen months ago. I build declaratively first — Flow handles far more than most people give it credit for — and only reach for code when there's genuinely no other way. I'm fussy about data, because a report nobody trusts is worse than no report at all. And I'd rather ship something simple that people use than something clever they quietly work around.
Twelve years in, the bit I still like is the moment someone realises they can stop keeping their own spreadsheet on the side.
What I'm good at
Clouds I live in
The certification pile.
Business Analyst
Earned Mar 2025AI Associate
Earned Mar 2025Platform Foundations
Earned Feb 2025Platform App Builder
Earned Feb 2025Platform Administrator
Earned Feb 2025Platform Developer
Earned Nov 2017Where I've been.
Oct 2017 — now
Solutions Consultant
Hyphen8 — Salesforce Consulting Partner
Eight years and counting on the partner side, taking clients from first conversation through to a working org. Mostly Nonprofit Cloud — discovery and requirements at one end, build and handover at the other.
Jan 2014 — Sep 2017
Salesforce Developer
Accenture · Newcastle upon Tyne
Three client projects across four years, all of it hands-on Sales Cloud and Service Cloud. Built consumer-facing pages and agent consoles in Apex and Visualforce, wrote the design docs and test plans, and ran the regular deployments. That included a year as the sole developer on an implementation that turned out to be considerably larger than anyone had scoped for.