James Hickey

Salesforce Consultant (Managed Services)

Blue Ocean Group

OtherConsultativeRemote📍 Remote (multiple approved states)
Posted by James Hickey

Overview

You work at a Salesforce Summit Partner managing 8-10 client engagements at once. Your job is discovery conversations, requirements gathering, and translating business needs into clear specs for the delivery team. Light configuration on Sales Cloud, Service Cloud, and Experience Cloud.


Role Snapshot

AspectDetails
Role TypeSalesforce Consultant (Managed Services)
Sales MotionN/A - Post-sales consulting
Deal ComplexityConsultative
Sales CycleN/A - Client delivery
Deal SizeN/A - Managed services retainer
Quota (est.)N/A - Measured on client satisfaction and project delivery

Company Context

Stage: Growth-stage Salesforce Summit Partner

Size: Team is growing, poster has placed 1/3 of the team

Growth: Actively hiring, stable revenue from managed services model

Market Position: Mid-tier Summit Partner competing on consultative approach vs transactional implementation shops


What You'll Actually Do

Time Breakdown

Client Meetings (40%) | Requirements/Documentation (30%) | Light Config (20%) | Internal Coordination (10%)

Key Activities

  • Discovery Calls: Lead 3-5 client discovery sessions per week. You're asking "why" before anyone builds anything. Digging into their current processes, pain points, and what success actually looks like to them.
  • Requirements Translation: Turn messy client requests into clear technical requirements. Write user stories, document workflows, create process maps that delivery teams can actually work from.
  • Client Management: Juggle 8-10 active engagements. Some clients need weekly check-ins, others are on maintenance mode. You're the main point of contact managing expectations when timelines slip or scope creeps.
  • Light Configuration: Do basic declarative builds in Sales Cloud, Service Cloud, Experience Cloud. Not heavy code. Mostly fields, flows, page layouts - enough to understand what you're asking developers to build.

The Honest Reality

What's Hard

  • Context Switching: You're jumping between 8-10 different companies, industries, and Salesforce orgs. Hard to stay deep on any one client when you're constantly shifting gears.
  • Scope Management: Clients always want more than what's in the SOW. You're constantly saying no diplomatically or negotiating change orders. Gets exhausting.
  • Dependency Hell: You can't move forward until the client sends you data mappings, or their IT team grants access, or legal approves the contract change. Lots of waiting and chasing.
  • Delivery Team Coordination: You don't build it yourself. You hand off to developers/admins who may interpret requirements differently. Time spent in handoff meetings and QA reviews.

What Success Looks Like

  • Clients renew their managed services contracts because they trust your guidance
  • Projects delivered on time without major scope blowouts
  • Delivery team gives you clear requirements docs they can work from without constant clarification questions
  • You can spot a bad requirement before it gets built

Who You're Working With

Primary Stakeholders:

  • Department heads and operational leaders at client companies (Marketing Ops, Sales Ops, Service managers)
  • Salesforce admins at client orgs who need strategic guidance

What They Need From You:

  • Help figuring out what they actually need vs what they say they need
  • Clear documentation they can reference after you're gone
  • Someone who pushes back when their idea won't work
  • Steady presence managing their engagement without constant escalations

Requirements

  • 3+ years experience at a Salesforce Partner (not in-house)
  • Salesforce Admin certification required
  • Strong BA instincts - can ask discovery questions and document requirements
  • Experience with Sales Cloud, Service Cloud, Experience Cloud
  • Located in approved states: AZ, CO, CT, DC, FL, GA, IN, MA, MD, MN, MO, NC, NE, OH, PA, SC, TX, VA, WA
  • Comfortable being client-facing and managing multiple stakeholder relationships
  • Can context-switch between different industries and business models