When a company decides to implement Salesforce, one of the first questions is: how do we do this? And the answer depends less on what you want and more on what your business needs right now.
There are two main engagement models. The first is faster and focused. The second is more comprehensive and transformative. Neither is universally better — the best one is the one that fits your moment.
Here's an honest guide to help you decide.
What a Quick Start is
A Quick Start is an accelerated implementation with a defined scope. Generally 4 to 8 weeks, the goal is to get Salesforce running for the core of your sales process as quickly as possible.
What's typically included:
- Sales Cloud setup (sales pipeline, accounts, contacts, opportunities)
- Essential customizations for the company's process
- Migration of the most critical data
- Basic team training
- Initial post-go-live support
What's not included:
- Integrations with external systems (ERP, marketing, support)
- Complex automations
- Advanced reports and dashboards
- Modules beyond sales (Service Cloud, Marketing Cloud)
The logic of a Quick Start is: start simple, learn by using, evolve with real data.
What a Full Implementation is
A Full Implementation is a more extensive project — generally 3 to 6 months — that covers multiple processes, teams, and modules. It's recommended when the company has more complex needs or wants to deploy Salesforce as a central operating system, not just for sales.
What it typically includes:
- Multiple modules (Sales + Service + Marketing, for example)
- Integrations with existing systems (ERP, e-commerce platforms, etc.)
- Complex automations and workflow rules
- Custom reports and dashboards by area
- Change management and in-depth training
The objective criteria for deciding
Consider Quick Start if:
Your sales team has up to 20 people In smaller teams, process complexity tends to be manageable in a focused implementation. There are fewer exceptions, fewer approvals, fewer variables.
You're implementing Salesforce for the first time Even if your company is large, if no one has prior experience with the platform, starting with a reduced scope allows the team to learn without being overwhelmed. You'll discover important things in the first weeks of use that will inform next steps.
You need visible results within 2 months If there's pressure for fast ROI — from internal stakeholders or the board — Quick Start delivers a functional system much sooner. A full implementation takes time to show value.
Your sales process is relatively linear Qualification → proposal → negotiation → close, without many detours, complex internal approvals, or frequent edge cases. The more linear the process, the faster and cleaner the implementation.
Your budget is more limited right now Quick Start costs less. If the budget is tight and you need to demonstrate value before investing more, this model lets you get started without straining cash flow.
Consider Full Implementation if:
You have processes across multiple departments that need to talk to each other When sales, marketing, and customer service need to be integrated in the same system, with shared data and cross-team flows, the scope goes beyond Quick Start. Implementing in parts in this case creates rework.
You have critical integrations with other systems If Salesforce needs to connect to your ERP, financial system, or e-commerce platform from day one, that changes the scope. Integrations add time, complexity, and technical decisions that need to be made carefully.
Your data volume is large and migration is complex Migrating history from previous CRMs, complex spreadsheets, or multiple data sources is a project in itself. Underestimating this is one of the most common mistakes.
You have an enterprise sales cycle with approvals and customizations Proposals that go through multiple approval layers, contracts with custom clauses, complex onboarding processes — all of this needs to be mapped and configured carefully.
You've used Salesforce before and know what you need Companies migrating from a legacy configuration or that have used the platform in another context arrive with clarity about what they want. That clear scope justifies a more complete implementation from the start.
The most common mistake: choosing by price, not by fit
The biggest trap is choosing Quick Start because it's cheaper when the operation clearly needs more — or choosing Full Implementation because it seems more serious when the company's current stage doesn't justify it.
Quick Start in a scenario that needed more results in an implementation that quickly becomes insufficient, generating an unplanned second phase that ends up costing more than doing it right the first time.
Full Implementation in a company that's still structuring its sales process results in months of project work during which the process keeps changing, requiring constant reconfiguration and increased cost.
An approach that works: Quick Start with a roadmap
A third path that many companies adopt successfully is Quick Start with a defined roadmap. The idea is simple: implement the essentials first, with explicit planning for subsequent phases.
This allows:
- Getting the system live quickly
- The team to learn by using
- The company to discover what it really needs before configuring
- Evolution based on real usage data
It's a way to have speed without abandoning the long-term vision.
How to make the decision
Three practical questions to guide your choice:
-
What's the minimum scope that already delivers real business value? If the answer is "just the sales pipeline", Quick Start probably covers it.
-
Which integrations are indispensable from day one? If there's more than one critical integration, the scope has already grown.
-
How quickly do you need to see a return? If the answer is "within 60 days", Quick Start. If it's "within 6 months", there's room for more.
There's no universal answer. There's the right answer for your company's current moment.
Marina Borges is founder of Rangers League, a Salesforce consulting firm for growing businesses in Brazil.
Frequently Asked Questions
Can I start with Quick Start and expand later? Yes — and that's the path many mid-market companies follow successfully. The important thing is that the initial architecture is built with growth in mind, so expansion is evolutionary, not a reconfiguration.
Is Quick Start enough for a company with 50 salespeople? It depends on process complexity. A large team with a simple process can work well. A large team with a complex process, multiple exceptions, and necessary integrations will likely need more.
How much does each model cost? Values vary considerably depending on the consultancy, complexity, and location. Quick Start implementations generally start around BRL 15,000–40,000 (roughly USD 3,000–8,000). Full implementations start around BRL 50,000 and can exceed BRL 200,000 for enterprise projects. Salesforce licenses are billed separately.
What is "go-live" and why does it matter? Go-live is the moment the system enters real use — when the team stops using the spreadsheet and starts using Salesforce. It's the most critical milestone in the project. The more prepared the team is for that moment, the smoother the transition.
