Build a custom Salesforce app when an off-the-shelf AppExchange app covers less than about 70% of your requirements, or when the workflow is core enough that you need to own the IP.
For standard needs, buying is faster and cheaper. For a unique or regulated process, custom wins. This is the decision with real costs and the trade-offs nobody tables.
Most articles on this frame it as two options: build or buy. There's a third — no-code/low-code (Flow, App Builder, no-code ISV builders) — that covers a lot of internal needs for the least money. The right call depends on requirement fit, time, and who carries maintenance.
Build vs buy vs no-code, side by side
| Dimension | Custom build (Apex/LWC) | AppExchange app (buy) | No-code / low-code |
|---|---|---|---|
| Upfront cost | $20K–$300K+ (industry range) | Subscription, low entry | Lowest |
| Time to live | 3–12 months | Days to weeks | Days |
| Maintenance owner | You | Vendor | You (config-level) |
| Customization ceiling | Unlimited | Vendor-bounded | Platform limits |
| IP ownership | Yes | No | Partial |
| Best when | Unique/regulated process, <70% AppExchange fit | Standard need, fast rollout | Simple internal workflows |
The cost ranges above are industry figures, not a Salesforce-published number — treat them as a planning band: roughly $20K for an internal tool, $50K–$150K for a commercial-grade app, and $100K–$300K+ for complex enterprise builds. Onshore Salesforce developers bill $90–$170/hour depending on seniority, which is what moves the range.
The benefits that actually justify a custom build
Custom is worth the cost when these matter to you:
- Exact fit. The app matches your process instead of bending your process to the app.
- IP ownership. You own the code and the roadmap. No vendor sunsets your feature.
- Integration depth. Native access to your data model and external systems, not a bolted-on connector.
- A product you can sell. A custom managed package can be listed on the AppExchange and become a revenue line — the part most "build vs buy" guides leave out.
The maintenance reality
A custom app isn't a one-time cost. Salesforce ships three major releases a year, and each one means regression testing against your code. Partner development shops typically carry that as a retainer. Budget ongoing maintenance as a real line item over three years, not a footnote — it's where build-vs-buy math usually flips.
When custom is the wrong call
Don't build custom to re-create commodity functionality that a mature AppExchange app already does well. Don't build if your team can't staff the maintenance. And don't build if a no-code configuration gets you 90% of the way for a fraction of the cost. The fastest way to waste a Salesforce budget is rebuilding something you could have installed.
If you build it, you can sell it
A custom Salesforce app built as a managed package can go on the AppExchange — now part of AgentExchange after Salesforce unified its marketplaces in April 2026. That turns a cost center into a channel: the Salesforce ecosystem reaches 150,000+ customers, and IDC projects partners will earn $6.84 for every $1 Salesforce makes by 2028 (Salesforce/IDC). The gate is the security review — 6–9 weeks, with roughly half of first submissions failing — and a revenue share of 15% (ISVforce) or 25% (OEM) on what you sell.
| Commercialization factor | Detail |
|---|---|
| Security review timeline | 6–9 weeks (initial) |
| First-attempt fail rate | ~50% |
| Listing cost | Free; per-submission review fee for paid apps |
| Revenue share | 15% ISVforce / 25% OEM |
Frequently Asked Questions
What is a custom Salesforce app?
An application built specifically for your org using Salesforce's platform tools (Apex, Lightning Web Components, Flow) rather than installed from the AppExchange. It can be internal-only or packaged and sold.
Custom build, AppExchange app, or no-code — how do I choose?
Score your requirements against the best AppExchange option. If it covers 70% or more, buy it. Below that, or if you need to own the IP, build custom. For simple internal workflows, no-code/low-code is usually enough.
How much does custom Salesforce app development cost?
As an industry planning range: ~$20K for an internal tool, $50K–$150K for a commercial app, and $100K–$300K+ for complex enterprise builds. Onshore developers bill $90–$170/hour by seniority.
How long does it take to build a custom Salesforce app?
Typically 3–12 months depending on scope, versus days to weeks to install an AppExchange app.
What's the ongoing maintenance burden?
Salesforce releases three times a year, each requiring regression testing against your code. Budget maintenance as a recurring cost over the app's life.
Can I sell a custom Salesforce app?
Yes — package it as a managed package and list it on the AppExchange (now AgentExchange). It must pass the security review, and Salesforce takes a 15% (ISVforce) or 25% (OEM) revenue share.
When should I not build a custom app?
When a mature AppExchange app already covers the need, when you can't staff ongoing maintenance, or when no-code gets you most of the way for far less.
Key Takeaway
Build a custom Salesforce app when an AppExchange app covers under ~70% of requirements or you need to own the IP; buy when the need is standard; use no-code for simple internal workflows. Custom builds run an industry range of ~$20K–$300K+ and 3–12 months, with ongoing maintenance across Salesforce's three annual releases. A custom managed package can be sold on the AppExchange (now AgentExchange) after passing the 6–9 week security review, at a 15% (ISVforce) or 25% (OEM) revenue share.
Related Articles
- Salesforce app development cost in 2026
- Should you list your B2B app on the Salesforce AppExchange
- How to list your app on the Salesforce AppExchange
