What this covers
Whether you're standing up Salesforce for the first time or inheriting an org that's been edited by a half-dozen part-time admins over five years, the work is roughly the same shape: get the data model right, get the user experience usable, and get the people on it.
I run both ends of that:
- New implementations — Sales Cloud, Service Cloud, Experience Cloud, Nonprofit Success Pack, or Health Cloud setups, including the data model, page layouts, security, and the first wave of automation.
- Existing-org cleanup — process builders converted to flows, redundant fields consolidated, profile and permission set sprawl untangled, validation rules and triggers audited, sandbox strategy reset.
- Org migrations — Classic to Lightning, Process Builder to Flow, sandbox refresh playbooks, and managed-package strategy.
- Optimization — for orgs that work but feel slow, expensive, or fragile.
How we typically engage
Most projects start with a paid two-week assessment. I spend that time in the org, with you, building a shared map of what's there, what's working, and what isn't. The output is a written diagnosis and a prioritized backlog you can either hire me to execute or hand to your internal team.
From there, the build is fixed-fee or T&M — your call.
What "done" usually looks like
- A documented data model and security model.
- Automation that's understandable to someone who didn't build it.
- A short, readable runbook for the admin who'll operate the org after I'm gone.
- A clear next-twelve-months roadmap so you know what to schedule and budget.