People sometimes come to Canviz knowing they want custom software. As we talk through the problem, we find an existing product that may do what they need at a sensible cost.
When that happens, we think it deserves a serious look.
We build software for a living. We’ve also spent enough time helping clients live with it to know that the build is only part of the decision. The question is whether the solution will fit your business, your budget, and the people who will look after it.
Start with the work, then look at the options
By existing software, we mean a product or platform you can adopt and configure rather than build from scratch. It could be a subscription service, a licensed application, or a platform your company already uses.
During discovery, we work with clients to understand the work that needs to happen and examine whether an existing solution can handle it. Where does it fit? Where does it fall short? Are those gaps essential requirements, or preferences we could reasonably change?
The test needs to go beyond a feature list. Walk through a real task, including the awkward exceptions. Check how information gets in and out, who needs access, and what happens when something goes wrong.
Sometimes that leads to buying a product. Sometimes it means adding a small integration or custom workflow around one. Sometimes it confirms that a custom application is worth building.
That discovery work is useful even when it leads to a smaller project for us, or no custom build at all.
A good fit also has to make financial sense
An existing product is not automatically good value. Its price may rise with the number of users, transaction volume, or the features you actually need. Implementation, administration, and integrations can add to the bill.
Compare both options over the same period, using realistic expectations for growth.
For a product, include licensing, setup, data migration, integrations, and the internal effort required to use it. For custom software, include discovery and development, hosting, third-party services, maintenance, and the people responsible for operating it. Account for any period when you will be paying for both the old and new systems.
A product that fits well at a manageable cost can be a strong choice. One that requires expensive licenses and extensive workarounds deserves a different conversation.
What experience taught us about the cost after launch
Earlier in our work, we had projects where we discussed maintenance costs, but the practical meaning of that responsibility still surprised the client near the end of the build.
They understood that someone would need to support the application. The surprise came when that became actual hiring decisions, engineering salaries, and the work of keeping a business system running.
We learned that mentioning maintenance was not the same as helping someone plan for it.
Over time, we’ve become much better at making that conversation concrete during discovery. Who will handle routine changes? Who will investigate a failed integration? Will the client use an existing team, hire people, or need ongoing help from us?
Those answers can change which solution makes sense. They should be part of the decision while there is still room to choose.
The size of the solution changes the answer
A few workflows on an established automation platform are a very different commitment from an application that runs a large part of the business.
A small, stable tool may be manageable by a capable technical person already on your team. They might have lacked the time or experience to build it initially but be comfortable looking after it once it is documented and handed over. Some projects need only occasional help, perhaps a few hours every couple of months.
A larger application may need a dedicated team of two to five people or more. The right staffing depends on its complexity, how often it changes, and how quickly someone needs to respond when it fails. These are examples of scale, not a staffing formula.
Even a small workflow needs an owner. If it handles something time-sensitive or business-critical, a low volume of maintenance does not necessarily mean a low need for support.
Buying and building can work together
Consider a hypothetical company whose document-management product already handles storage, permissions, and search well. Its problem is a particular approval process.
Replacing the whole product would mean taking responsibility for capabilities that already work. A focused workflow or integration may solve the problem with much less custom software to maintain.
The reverse can also be true. If every essential task needs a workaround, and the licensing costs remain difficult to justify, a custom application may offer a better fit.
The amount of software you can build is rarely the most useful starting point. Define the smallest useful scope, then test whether it delivers enough value to justify owning it.
AI-assisted development may reduce some implementation effort. It does not remove the need to support the resulting system, so a faster build still needs a realistic operating plan.
Think about ownership as well as features
There is a useful comparison with owning or renting a home. Buying gives you more control, but the roof, windows, and leaking sink become your responsibility. Renting places more of that upkeep with someone else, within the terms of the arrangement.
Software has a similar tradeoff, though the analogy has limits. With a hosted product, the vendor takes care of much of the underlying platform and product upkeep. Your business still has responsibilities for its data, access, configuration, and any custom connections. Microsoft’s shared-responsibility guidance illustrates that distinction.
Custom software gives you more say over how the application works. The contract and design determine what you own and how easily another team can take over. Check access to the code, accounts, documentation, and data before committing.
Make the choice with the support plan in view
Before deciding, ask:
- Can an existing product handle our essential work at an acceptable total cost?
- Could a small addition close the gap?
- If we build, who will maintain it and what will that require?
- Have we tested the important assumptions with a real workflow?
We’re comfortable recommending an existing product when it is the better answer. Experience has taught us that a successful launch is only the beginning of a useful system.
If you’re weighing the options, talk with Canviz about the work you need to support. We can help you examine the fit, the gaps, and the ongoing commitment before you decide what to build.
