In-house or consultancy? Rewriting your Salesforce resume for the other world

One of the most common moves in a Salesforce career is crossing between two very different worlds: the in-house seat at an end-user company, and the consulting partner that implements for many clients. People jump both directions all the time — and then wonder why the applications go quiet. The reason is that the two worlds reward nearly opposite things, so a resume tuned for one reads as a risk to a hiring manager in the other. An in-house CV full of "maintained the org" scares a consultancy; a consultant CV full of short engagements worries an in-house team. The experience is real either way — this is about reframing it for the reader you're now facing. It's a different axis from contract vs permanent: that's about engagement type, this is about the kind of employer.

What each world actually values

They optimise for different things, and your resume has to speak the local language:

• In-house rewards depth: institutional and business-process knowledge, long-term ownership, stakeholder relationships, a roadmap you steward, and continuous improvement of one org you know cold.
• Consultancy rewards breadth and delivery: ramping fast on unfamiliar orgs, scoped implementations shipped on timeline, discovery and requirements across clients, certified range, and billable throughput.

Going in-house → consultancy

The fear a consultancy screens for is: can this BAU admin actually deliver a scoped project to a deadline for a paying client? So foreground delivery, not maintenance:

• Lead with projects: implementations, migrations, redesigns — framed as discovery → build → go-live, the way the consultant guide lays out.
• Show client-facing work: requirements gathering, stakeholder workshops, demos.
• Prove you can ramp fast and work across multiple orgs or business units.
• De-emphasise pure keep-the-lights-on BAU; reframe it as ownership of outcomes, not ticket queues.

Going consultancy → in-house

The fear an in-house team screens for is: will this consultant job-hop, and can they go deep instead of parachuting out after go-live? So foreground ownership and staying power:

• Show depth in one domain or industry — that you can own a roadmap, not just ship and leave.
• Emphasise stakeholder relationships and business-outcome knowledge, the in-house currency.
• Frame engagements as owned outcomes ("ran the org for this client for 18 months"), not a parade of logos.
• Signal you want to go deep and stay — the opposite of project-hopping.

Metrics change by world

Quantify in the terms each world cares about. Consultancy: projects delivered, on-time/on-scope rate, clients served, go-lives, utilisation. In-house: adoption and process improvements, cost or time saved, roadmap outcomes, users supported, uptime of what you own. Same career, different scoreboard.

From in-house to consultancy — a reframe

Before (in-house voice): "Maintained and supported the Salesforce org for a 500-user company — handled user requests, built reports, kept data clean."

Reads as BAU-only — a consultancy can't tell if you can deliver a project.

After (consultancy voice): "Owned end-to-end Salesforce delivery for a 500-user org: led a Service Cloud redesign from discovery to go-live across 4 departments, shipped Flow automation on a fixed timeline, and drove 40% adoption lift — scoped delivery a client engagement would recognise."

Same work — now it reads as deliverable, client-ready, quantified.

Read the posting and match the world

Before sending anything, decide which world the role lives in and tailor to it — delivery-and-breadth language for a partner, ownership-and-depth language for an end user. The same bullet can be written either way; the skill is knowing which reader you're writing for. Mixing both voices in one resume is what makes it read as unfocused to both.

Certifications

The cert stack is largely the same across both worlds, but it's weighted differently:

• Consultancy treats certs as a badge of billable range — breadth signals you can be staffed on varied engagements, so a spread (Admin + the consultant certs for the clouds you deliver) earns its place, per the certification roadmap.
• In-house cares most about the specific clouds that org runs — depth in their stack beats a long badge list.

List the same credentials; order and emphasise them for the reader.

Keep both versions in one place

The friction in switching worlds is maintaining two tellings of the same career — the delivery-forward one and the ownership-forward one — without starting from scratch each time. In the SFCV builder your roles, certifications, and quantified outcomes live in one place, so you can keep a consultancy-voiced and an in-house-voiced version in sync and aim the right one at each role on the jobs board.

Crossing between in-house and consultancy is a smart, normal career move — but the resume has to cross with you. Decide which world you're applying to, speak its language, answer its specific fear, and reframe the same real experience to fit. Do that and the jump reads as a natural next step instead of a risky misfit.