Own delivery on mid-size Salesforce implementations, from the first discovery workshop to the handover nobody has to redo.
This is the role at the centre of the business. You take a client from a rough idea of what's wrong to a platform their team actually uses, and you stay close enough afterwards to know whether it worked.
You'll usually run one substantial engagement and a smaller one at the same time, with a developer or two beside you and an architect on call for the decisions that deserve one. Nobody will hand you a specification to administer. Working out what the client actually needs, including the parts they haven't said out loud, is the job.
What you would be doing
- Run discovery: workshops, process mapping, and the awkward questions about how the work really gets done
- Design the solution and write it down clearly enough that a developer can build it and a client can approve it
- Configure Salesforce yourself for the parts that don't need code
- Hold the scope, and say so early when a request has moved outside it
- Take the client through user acceptance testing, training and go-live
- Hand over to support properly, with documentation that survives you being on leave
What we are after
- Three or more years consulting on Salesforce, agency or client side
- Sales Cloud or Service Cloud to a level where you aren't guessing
- Evidence you've run a workshop with people who didn't want to be in it
- Writing that a non-technical executive can read without a translator
- The judgement to recommend less than the client asked for
Nice, not necessary
- Experience in financial services, professional services or NDIS providers
- Any integration platform, even at a shallow depth
The part people find hardest
Holding a line with a client you like. The scope conversation is the part of this job people find genuinely uncomfortable, and we would rather you had it in week two than in the week before go-live. You'll get backing from a delivery lead every time, but you have to be the one in the room.
#J-18808-Ljbffr
