“Clicks — not code” is one of salesforce.com’s catchy phrases. It drives home the message that you can do a lot with Force.com to deliver rich functionality before resorting to custom development. But many people (from companies and implementation firms alike) are still unaware of when best to use custom development and when best to use clicks using Force.com.
The Manufacturer’s Guide to Marketing Through Partner Enablement in 2021
Learn how partnerships allow manufacturers to scale revenue growth beyond what’s possible with direct sales alone.
So — how can you tell when each may be appropriate?
Our experience working with customers over the past 6 years using both options extensively highlights what to consider. In ranked order:
- Who will support the code on an ongoing basis?
- What is the ROI versus using native features?
- How much will it cost?
- One of our clients (a large public company with over $1B in revenue) gave this directive during implementation: “If we cannot accomplish it natively, we will change our business process.”
- Another one of our clients (a small private company of about $30m in revenue) developed thousands of lines of code because they wanted to get the best possible technology fit with their business processes.
- Understand the full product’s native capabilities. Have you exhausted all native options? Don’t rush to code just because you can.
- Be open to tweaking business processes to use native functionality.
- Weigh what you get (automation, cool user interface, etc.) in the business context of how important the business process is and how often it is used.
- Think about who will support the work post-deployment.
- Consider working with an implementation partner like Perficient who has the product knowledge, development experience, and insight into the salesforce.com product roadmap to utilize what’s available now and know what’s coming down the pike.