Salesforce Platform & Experience · Design Systems · San Francisco
I create the foundation for distributed teams to build on and deliver value.
I work the whole stack of a Salesforce experience — the Apex and API integrations that feed it, the design system and tokens that shape it, and the component patterns distributed teams build against — so what ships is responsive, accessible, on-brand, and wired to real data. Not bolted together after the fact.
What I own
The foundation — set once, set right
When the foundation is solid, everything built on it stays consistent and the team moves fast. When it isn't, you get rework, drift, and desktop-only UI in a mobile-first world. I own the former so you never ship the latter.
Design system bridging · tokens · components
Bridging whatever platform design system is in play — SLDS, a
client's own DS, or both — applying tokens
(var(--), never hardcoded hex) and reusable
component patterns so teams stop rebuilding the
same things on every project. Consistent everywhere, fighting
neither the platform nor the brand.
Responsive, accessible, mobile-first
Salesforce has historically optimized for desktop data entry. Your users are on their phones. I make mobile-first and accessibility non-negotiables from the first commit — not a retrofit at the end.
Data-to-experience translation
Turning a data model into a customer workflow. Turning 40 fields into a wizard. Deciding what's primary, what's secondary, what the empty state looks like. The UX decisions no platform makes for you.
AI-accelerated UI, kept clean
AI lets teams spin up UI fast. I help teams choose the right tools and hold the quality line — so velocity produces a maintainable system instead of a mess of one-off components.
Platform-side depth · Apex · API integration
The experience layer is only as good as the data reaching it. I write the Apex that connects the Salesforce Platform to enterprise APIs — consuming MuleSoft-exposed services, wiring Data Cloud into the experience, and mapping raw payloads into UI that makes sense. I build the consuming side end to end, partnering with integration teams on the middleware they own.
A full-stack career, a deep front-end specialty. I started my career building across the full stack — Adobe AEM component development paired with enterprise Java commerce for Whirlpool and KitchenAid, IBM WebSphere Commerce for a medical-device manufacturer, and a native iOS paint-locator app shipped to the App Store in 2011. On Salesforce, that range still shows up: Apex and API integration work alongside the experience layer. Project after project, my passion kept pulling me toward the UI — the place where design intent either survives or dies, where a token system either holds or falls apart. I now own that layer with conviction, and because I’ve built the layers underneath it, I partner with platform and data architects fluently — never bluffing where it matters.
How I work
The order matters — most technical debt is created before a line of code is written
This is a real sequence, not a menu. Skipping the early steps is exactly how teams end up rebuilding the same thing twice — the UI, the integrations behind it, all of it.
Partner with design on feasibility
I sit with the designers — mine or the client's — and pressure-test what's buildable before it's locked — in the UI and in the data that has to reach it — flagging the real cost of each choice before anyone's committed to it.
Audit the design and the codebase
Before anyone builds, I review what already exists — the design intent, the codebase, and the data model underneath — so the foundation is informed by reality, not assumptions.
Surface dependencies early
I work with product owners and delivery leads to name what has to happen first — so the build order is right and the team isn't blocked mid-sprint.
Set the foundation
Global and foundational styles, token mapping, responsive accessible defaults — and the API contracts the experience will consume — the layer everything else inherits from, whether the platform is Salesforce, AEM, or something else entirely.
Enable the offshore team
Reusable component patterns, clear standards (tokens over hardcoded values), and a fast answer when global-styling questions come — so distributed delivery actually ships consistent UI.
Steer the AI tooling
I guide teams on which AI tools to use and how, so the speed AI provides builds on the system instead of quietly working against it.
Selected work
Closing the data-to-experience gap across 12 years
Salesforce Experience Cloud and Platform, Adobe AEM, enterprise commerce (Hybris, WebSphere Commerce), enterprise portals — a long arc across stacks, industries, and team models. Across Whirlpool, KitchenAid, Steris, Intel, Marriott, and more. Current client names kept general; happy to talk specifics.
Data visualization
The long arc, era by era
An interactive timeline of the platform eras behind the work above — built with D3.js, rendered from a JSON data file, and re-themed live by the same design tokens as the rest of this site. Hover or tab through the bands.
Get in touch
Does your Salesforce org feel like a database with a UI on top?
Tell me a little about where you are — a new build, a modernization, a design system that doesn't exist yet, or screens that shipped but nobody loves. I'll get back to you.
Or email directly — dooleyfawn@gmail.com