What does a Salesforce consultant do (and when to hire one)

You paid for Salesforce licenses, someone on the team "set it up," and six months later sales still runs the pipeline in a spreadsheet. We hear this story constantly, and the cause is almost always the same: the company bought the tool without anyone translating it into the business. That translator is the Salesforce consultant.

The actual job of a Salesforce consultant

A Salesforce consultant takes a business process (sales, service, collections) and turns it into a system people actually use. In practice that means four fronts:

1. Process diagnosis

Before touching the platform, the consultant maps how you sell today: where leads come from, who handles them, where they get dropped, what reports management needs. If a consultant starts configuring objects on day one without asking these questions, be suspicious.

2. Solution architecture

Salesforce can solve almost anything in three ways: standard configuration (objects, flows, validation rules), code (Apex, Lightning Web Components), or an AppExchange app. The consultant's judgment lives in choosing the cheapest option to maintain, not the most impressive one. Our own rule: if a Flow solves it, we don't write Apex.

3. Implementation and data

Configuring the org, migrating clean data (deduplicated, with owners assigned), and connecting Salesforce to what you already run: website, WhatsApp, invoicing, ERP. Dirty data migration is where most implementations die, because a CRM full of garbage records loses the team's trust within weeks.

4. Adoption

The least technical part and the most decisive. Training users, trimming page layouts so logging a call takes seconds instead of minutes, and measuring real usage during the first weeks. A CRM nobody fills in is not a software problem, it's a process design problem.

Consultant, admin, and developer are not the same role

These three get mixed up constantly, which is why so many hires go wrong:

• Administrator: runs the org day to day. Users, permissions, reports, minor tweaks. An internal or recurring-support role.
• Developer: writes code when configuration isn't enough. Apex for complex logic, LWC for custom interfaces, API integrations.
• Consultant: decides what gets built and why. Talks to leadership in process terms and to the technical team in platform terms.

In small and mid-size company projects these roles often live in one person or a small team. That's how we work: process consulting first, and when the project calls for it, Apex and Lightning Web Component development done in-house, not subcontracted.

Signs you need a consultant

Not everyone does. These signs say you do:

1. You bought licenses and the team doesn't use them. The problem is rarely the tool; it's that the system doesn't reflect how your team actually works.
2. Your org grew by patches. Everyone added fields and flows for years and now nobody knows what's safe to delete. That's fixable, but it takes an audit, not more patches.
3. You want Salesforce connected to the rest of your operation. A website that creates leads automatically, WhatsApp tied to opportunities, invoicing in sync. Badly built integrations duplicate data; well built, they eliminate manual entry.
4. You're starting fresh and want to skip the mistakes above. Implementing well from the start costs a fraction of rescuing a broken org later.

What to ask before you hire

Four questions that filter fast:

• Can they explain the proposal without jargon? If they can't translate "we'll use a custom object with an approval Flow" into "discounts above 15% will need your manager's sign-off," they'll build something nobody understands.
• Do they ask about your process or only about your licenses? Whoever starts with licenses is selling configuration hours, not outcomes.
• Configuration or code, and why? The right answer depends on the case, but an explicit criterion must exist. Unnecessary code is debt you pay on every release.
• What happens when the project ends? Documentation, training, and an exit plan. If the answer implies permanent dependency, keep looking.

Where we stand

We do Salesforce consulting for companies in Mexico with a deliberately conservative approach: process before platform, configuration before code, and Apex or LWC only when they add something the standard platform can't. And since we also build websites and WhatsApp automation, connecting your CRM to your sales channels is part of the same project, not an add-on from another vendor. If you're weighing whether to build something outside the CRM entirely, we also do custom software.

Not sure whether your case needs a consultant, an admin, or a developer? Tell us what's going on with your org and we'll give you an honest answer about which role you need, even if it isn't us.