10+ years as a Salesforce consultant moving fluidly across admin, business analysis, product ownership, and hands-on configuration — whatever the platform actually needs, not just what a title implies.
I'm a Salesforce Consultant with 10+ years working across Sales Cloud, Service Cloud, and CPQ — the person teams bring in because I move fluidly across whatever the platform actually needs, not just one lane. On a given engagement I might run requirements discovery like an analyst, configure and secure the org like an admin, write Apex triggers and SOQL alongside engineers, or own the roadmap and prioritization like a product owner. The title changes; the ownership doesn't.
My work sits across the full Quote-to-Cash lifecycle: requirements workshops, gap analysis, CPQ solution design (bundles, price rules, approvals), integration analysis, and UAT/SIT coordination with Sales, Finance, and Revenue Operations. I currently own requirements intake and solution design for a platform supporting 1,500+ Sales Cloud and Service Cloud users, plus 100+ community users.
Titles like "Systems Analyst" and "Administrator" undersell how much of this work is genuinely cross-functional — I'm usually the person in the room translating between engineering, sales leadership, and finance, and I stay hands-on with configuration rather than handing it off.
Five things that show up in every engagement — from the first requirements conversation to a system that's actually adopted.
Lead discovery workshops and gap analysis with Sales, Finance, and Revenue Operations, then translate what's said into documented, buildable requirements — not just a wish list.
Design product bundles, price/product rules, and approval logic across the Quote-to-Cash lifecycle, then configure it myself rather than handing off to another admin.
Design security and sharing models from org-hierarchy analysis so access holds up as headcount grows — not a patchwork of one-off permission fixes.
Facilitate sprint planning, backlog grooming, and retrospectives, and write the user stories that keep engineering pointed at real business outcomes, not just tickets.
Identified where root-cause investigation was slowest and built a workflow across Jira, Confluence, Salesforce, and Git history that cut that time by up to 90%.
Three systems from my current role at Motive, chosen to show range across AI-driven process improvement, platform expansion, and CPQ ownership.
Root-cause investigation for platform issues was manual and slow, requiring cross-referencing Jira tickets, Confluence documentation, Salesforce configuration, and Git commit history by hand — every time.
Motive's push into Canada, Europe, and Mexico required quoting capability the existing CPQ configuration didn't support, with requirements spanning Sales, Finance, and Revenue Operations.
Motive needed a company-wide CPQ rollout to standardize quoting and pricing accuracy — with no existing governed approval process for Renewal, New, and Expansion quotes.
The roles that built the foundation — Salesforce administration, security architecture, and business analysis across enterprise environments.