Custom software guide
Should you build on a platform or have custom software built?
Build on a platform such as Microsoft Power Apps when the need is modest, your own staff can do the building and you accept the limits and fees of the vendor for as long as the app runs. Have custom software built when the process is specific and central to how you operate, because over five years the platform keeps charging per user and a custom system you own carries only running costs such as hosting.
| What you are comparing | A product | A custom build |
|---|---|---|
| Cost over five years | A subscription for as long as the app runs, priced per user, per credit or by quote depending on the vendor, plus the staff time spent building and maintaining it. The total usually grows as use grows. | A one-time build scoped in writing, then running costs such as hosting, the database and email. There are no licenses, so the total does not climb with headcount. |
| Per-seat fees | Most platforms on our lists charge per user. A few charge by credits or by plan, and those have ceilings of their own. | None. A new employee, a manager who only reads reports and a customer login all cost nothing to add. |
| Fit to your process | As close as the platform and your builder can get it. Rules the platform cannot express stay in the heads of your staff or in a spreadsheet beside the app. | Written from your process, including the approvals, exceptions and handoffs that are particular to your company. |
| Time to launch | A first version can appear quickly, and sooner with an AI builder. Getting from that version to something a whole company relies on takes longer than the demo suggests. | Begins with discovery and a written scope, and the schedule is set in that scope. You see working screens throughout the build. |
| Who does the building | Your own staff, or a contractor who knows the platform. Someone inside the company maintains the app from then on. | The Black Badger team in the United States. Your people supply the knowledge of the process and review the screens. |
| What you own | Your data, which you can usually export. The app generally lives on the platform under the terms of the vendor. | The source code, the database and every account the system runs on, all in your name. |
| Limits and ceilings | Set by plan. Record counts, automation runs, API calls, credits and external users are all capped somewhere on the price list. | No plan tiers. The limits are those of the hosting you choose, and you can change them without changing vendors. |
When a low-code or AI platform is the right answer
Choose a platform when the app is small, the people who need it are few and someone on staff is keen to build it. A department tracker, an approval form or a simple portal does not need a software project.
A platform is also the right first step when you are not yet sure what you need. Building a rough version and watching people use it teaches you more than a planning meeting, and nothing stops you from having a custom system built later.
When custom software is the right answer
Have it built when the software will sit at the center of how the company runs. If several teams will depend on it daily and it has to agree with your accounting or ERP system, the limits of a platform turn into daily workarounds.
Have it built when nobody on staff should be a part-time software maintainer. A platform app depends on the employee who built it, and that person has another job.
How to compare the cost of a low-code or AI platform with a custom build
Compare the same span of years for both. On the platform side, add the subscription at the plan you will need, the add-ons, and the hours your own people will spend building and fixing. Staff time is the cost most comparisons leave out.
On the custom side the figure comes from a written scope. Black Badger does not publish a price, because it depends on what the system must do and how many other systems it must agree with. The scope gives you one number to set beside the platform total.
What a custom build involves, and how to ask about one
Questions buyers ask
Is a low-code platform a kind of custom software?
A low-code platform produces software shaped to you, so in a loose sense it is a kind of custom software. The difference is ownership and limits. You rent the platform and work inside its plans, while a custom build leaves you owning the code.
Can we start on a platform and move to a custom build later?
Yes, you can start on a platform and move to a custom build later, and it is a sensible path. The platform version becomes a working description of what you need, which makes the scope for the custom system quicker to write and more accurate.
Does an AI app builder make a custom build unnecessary?
AI app builders can make a custom build unnecessary for a prototype or a small internal tool. For a system that holds customer or financial records, someone still has to design the access rules, test them and stay answerable for the result. The tool does not take on that responsibility.