How to choose the right path for functionality gaps in your CRM
Salesforce is powerful out-of-the-box, but every business eventually faces the same question:
“Should we build this inside Salesforce, buy an AppExchange product, or use an external tool?”
Choosing the wrong path can lead to high costs, slow adoption, or a tangled tech stack. Let’s break down the pros and cons of each approach and how to decide.
1) Build Inside Salesforce (Custom Objects & Config)
What it means:
You design your own functionality using Salesforce-native tools:
- Custom Objects
- Flows, Apex, or LWC components
- Reports and Dashboards
- Declarative features like Validation Rules and Dynamic Forms
Pros:
- Fully native: Data lives in Salesforce, no integration headaches
- Tailored to your process: You control design and user experience
- Lower long-term licensing costs: No extra SaaS subscription fees
Cons:
- Requires admin/dev resources
- Longer time-to-market if complex
- Harder to maintain if you over-customize
Best for:
- Unique business processes not covered by off-the-shelf apps
- When you have internal admin/developer capacity
- Needs that evolve frequently and require flexibility
2) Buy on the AppExchange
What it means:
You purchase and install a Salesforce-native app built by a third party. Examples:
- DocuSign (e-signature)
- Conga/DocGen (document automation)
- OwnBackup (data backup)
Pros:
- Fast implementation: Most are plug-and-play
- Battle-tested: Apps are vetted by Salesforce Security Review
- Support & updates included: Maintenance is the vendor’s job
Cons:
- Ongoing subscription costs
- May include features you don’t need
- Limited flexibility compared to custom builds
Best for:
- Commodity functions (e-signature, billing, project management)
- Tight timelines where speed-to-value is crucial
- When support and compliance are high priorities
3) Integrate an External Tool
What it means:
You connect Salesforce with an external SaaS or on-premise system using APIs or middleware (e.g., MuleSoft, Zapier).
Pros:
- Use best-of-breed tools outside Salesforce
- Avoid bloating Salesforce with unrelated data
- Scales independently of Salesforce limits
Cons:
- Integration complexity (security, data sync, latency)
- Multiple systems = multiple user experiences
- Higher total cost of ownership for complex ecosystems
Best for:
- Specialized systems outside CRM scope (ERP, marketing automation)
- High-volume data that would exceed Salesforce storage limits
- Companies with a mature integration strategy
How to Decide: A Simple Framework
Ask yourself these questions:
- Is this process core to Salesforce users?
→ If yes, consider Build or AppExchange - Do we have internal resources to build and maintain it?
→ If yes, Build may be cost-effective - Does an AppExchange app meet 80%+ of requirements?
→ If yes, Buy saves time and risk - Is this function better served by a specialized system outside Salesforce?
→ If yes, Integrate
Pro Tip: Avoid overbuilding in Salesforce. Start small and validate user adoption before scaling.
Conclusion: Build, Buy, or Integrate?
There’s no one-size-fits-all answer.
- Build when your needs are unique and you have in-house expertise
- Buy when a vetted app meets most of your needs and speed matters
- Integrate when Salesforce shouldn’t be the system of record for that function
Thoughtful evaluation upfront saves months of technical debt and thousands in costs later.
Need Help Deciding?
I help RevOps teams design smart Salesforce ecosystems: build where it makes sense, buy where it saves time, and integrate where it drives ROI.