There's a difficult conversation that Salesforce consultants tend to avoid: sometimes, the right answer is "not yet."
Not because the company doesn't need it or wouldn't benefit from Salesforce. But because implementing the right tool at the wrong moment can be just as harmful as not implementing it at all. The numbers back this up: CRM implementation failure rates hover around 55%, and the root cause is rarely technical. It's lack of organizational readiness.
If you know what Salesforce can do, you've seen the potential, and yet things aren't quite clicking into place for the next step — this post is for you.
Why timing matters as much as the tool
Salesforce is not a spreadsheet you start using tomorrow. It's a platform that structures your sales, marketing, and service processes. And "structure" is the key word: to structure something, that something needs to exist in some form first.
Companies that implement Salesforce with sufficient maturity move ahead in months. Companies that implement prematurely spend the first months trying to define — inside the tool — things that should have been defined before: funnel stages, qualification criteria, each person's responsibilities.
The result is a configuration that doesn't reflect reality, low team adoption, and the feeling that "Salesforce doesn't work for us" — when the problem was never Salesforce.
Signs you're not ready yet
1. Your sales process exists only in people's heads
If the sequence of steps in the sales cycle changes depending on who you ask, you don't have a process — you have people with good intentions and different styles. Salesforce will reflect exactly that: a different system for each salesperson, with no comparable data and no collective learning.
What to do first: Document the current process, even if imperfect. Map the funnel stages, the criteria for moving between stages, the approval points. It doesn't need to be perfect — it needs to be written down and agreed upon.
2. You don't know where your best customers come from
Which channel generates the most revenue? Referrals, outbound, inbound, events? If you don't have a reliable answer to that question, you'll configure Salesforce without knowing what to measure. And what doesn't get measured doesn't improve.
What to do first: Even manually, classify your last 20 to 30 customers by source channel. This simple exercise will reveal where to focus energy — and will inform how to configure lead sources in the CRM.
3. Customer data is scattered across multiple places with no defined owner
Email, finance spreadsheet, sales spreadsheet, founder's personal calendar, business cards in a drawer. If that's the reality, data migration will be a project in itself — and it will delay or compromise the implementation.
What to do first: Consolidate customer and prospect data in a single place, even if it's a spreadsheet. Define who is responsible for keeping it updated. This data governance exercise, done upfront, saves weeks later.
4. The sales team sees every new tool as bureaucracy
Behavioral change is the biggest challenge in any CRM implementation — not the technology. If there's pre-existing resistance to using systems, or if the culture is "I sell, I don't fill out forms", the tool won't take off without cultural change that precedes the software.
What to do first: Involve the sales team before deciding anything about technology. Ask what their biggest pain points are in the current process. When people participate in the decision, adoption is much higher.
5. There's no internal owner for the initiative
Successful Salesforce implementations always have an internal "owner" — someone who cares about the outcome, who will enforce the processes, who will be the contact point with the consultancy and the reference point for the team.
If the expectation is that the consultancy configures everything and the team magically starts using it, without an engaged internal person, the chances of success drop dramatically.
What to do first: Identify who that owner will be. It doesn't need to be a technical role — it can be the sales manager, COO, or the founder themselves. It needs to be someone with decision-making authority and genuine interest in the outcome.
6. There's no approved budget beyond the license cost
Many companies calculate the cost of Salesforce as the monthly license fee — and are then surprised by the cost of implementation, training, and maintenance. A proper implementation has a cost, and cutting corners here creates expensive rework later.
What to do first: Understand the total cost of ownership: license + implementation + training + ongoing support. Well-planned budgets account for at least 12 months of operation before revisiting the model.
What to do while you prepare
Being "not ready yet" is not a permanent diagnosis — it's a to-do list.
The most efficient path typically looks like:
- Document the current sales process (2 to 4 weeks)
- Consolidate and clean customer data (1 to 3 weeks)
- Identify the internal owner (immediate)
- Align the team on the why of the change (a conversation, not a slide deck)
- Define the metrics you want to track before configuring anything
With these five steps done, the implementation goes faster, costs less, and has a much higher chance of being genuinely adopted.
When you're ready, the difference is enormous
Companies that arrive at an implementation with a defined process, organized data, and an engaged team complete projects in half the time and have significantly higher adoption rates. Salesforce, in that case, amplifies what already works — instead of trying to fix what doesn't.
If you're in this preparation phase right now, the work that looks "preliminary" is actually the most important work in the entire project.
Not sure where to start? That's exactly what we do.
Preparing a company for Salesforce is technical and strategic work — and it's one of the services we do most at Rangers League before a single line of configuration.
What we deliver in this preparation phase:
Readiness audit A structured assessment of the company's current state: sales process, data quality, team maturity, existing systems. The output is a clear diagnosis of what's ready, what needs attention, and what could derail the project if left unaddressed.
Process mapping and documentation We work with the company's stakeholders to map the sales process as it is today — and as it should be. This includes the sales funnel, qualification criteria, approval points, and edge cases. A documented process is invaluable before any configuration begins.
User story creation So that Salesforce is configured for the people who will actually use it — not a theoretical version of your team — we create user stories by profile: what each person needs to see, do, and record in the system to do their job well. This is the difference between a CRM the team uses and one the team ignores.
Data organization plan We map existing data sources, identify duplicates, missing fields, and inconsistencies, and create a cleanup and migration plan. Without this work, migration turns into chaos.
This preparation work typically takes 3 to 6 weeks, depending on the complexity of the operation. Companies that arrive at implementation having gone through this process finish faster, with higher adoption, and far less rework.
If you recognized yourself in the signs in this post and want to understand exactly where your company stands — and what needs to change — get in touch. The first conversation is free.
Marina Borges is founder of Rangers League, a Salesforce consulting firm for growing businesses in Brazil.
Frequently Asked Questions
How long does it take for a company to be "ready" for Salesforce? It depends on the starting point. Companies with a basic documented sales process and minimally organized data can be ready in 4 to 8 weeks of preparation. More disorganized companies may take 2 to 3 months — but the time invested here saves much more during implementation.
Can we implement Salesforce and define the process at the same time? Technically yes, but it's risky and more expensive. Every process change after the initial configuration creates rework. The ideal is to have at least a process outline before configuring.
My company is small. Do we need all this preparation? The scale is different, but the principles apply. A company with 5 people in sales needs a documented process, organized data, and an accountable owner just as much as one with 50. The preparation workload is smaller — but it can't be skipped.
What is an "internal owner" and what does that person need to know? They don't need to be technical. They need to understand the company's sales process, have authority to make decisions about how the system will be configured, and have genuine interest in the tool working. Often it's the founder, a senior sales manager, or the COO.
