The platform is built for it – but that does not mean you always should
ServiceNow is not just a collection of ready-made products. The platform is also a development environment where you can build your own applications with your own tables, flows, portals and permissions. That is a major strength, but also a source of unnecessary complexity if you build when you should configure.
We usually think in three levels.
1. Use the baseline
If ServiceNow already has a product for the need – such as customer cases in CSM or HR cases in HRSD – the starting point is to use it. Baseline features are upgraded by ServiceNow, gain new capabilities automatically and are where new AI functionality lands first.
The question to ask: Is our need really unique, or is it our current way of working that is unique?
2. Configure and extend
Often configuration is enough: adding fields, adjusting forms, building flows in Workflow Studio and creating catalogue items in the portal. It is cheap to maintain as long as you do not rewrite ServiceNow's own logic.
3. Build your own scoped app
A custom application is right when:
- The process has no equivalent in the baseline. Typical examples are business-specific processes in manufacturing and supply chain, such as deviation handling, internal ordering flows or quality cases.
- You want to bring together a process that today lives in spreadsheets, email and small standalone tools.
- You need a clear boundary with the rest of the platform in terms of data, permissions and ownership.
Build it as a scoped application. A scope gives the application its own namespace, so its tables and code are protected from other applications unless you explicitly allow access. That makes it easier to maintain, move between instances and upgrade.
Low-code or pro-code?
- App Engine Studio is a guided low-code tool for creating tables, portals, flows and permissions. A good fit for simpler applications and for builders close to the business.
- ServiceNow Studio and the SDK for pro-code development, when the application has more logic, integrations or high demands on structure and version control.
In practice, many applications start in low-code and grow. So plan for governance from the start: who may build, how changes are reviewed and how applications are moved to production.
Our experience
The best custom applications we have built have one thing in common: they replaced something that used to be manual and scattered, and they were built close to the people who actually use them. The worst ones tried to recreate baseline functionality with small differences.
A good rule of thumb: if you cannot explain in one minute what makes your process different from the baseline, start with the baseline.
Read more about how we work with application development on ServiceNow.