Article/Custom Software
Custom Software

When Nothing Else Fits: Custom Software vs. SaaS Products

Custom SoftwareCustom Software

When a business needs new software, the first instinct is usually to see what's already out there. And that makes sense. There are SaaS products for almost every business function imaginable, and if you can find one that does what you need it to do, it can be a relatively easy way to solve the problem.

But finding software and finding software that actually fits your business are two different things.

For a lot of companies, the challenge comes when their processes become too complex or unique to fit neatly into an existing product. They've tried SaaS products but find themselves spending too much time trying to force them to fit their needs and still coming up short.

That's when teams start making compromises. They adjust their processes, add another tool, build a spreadsheet or create a manual workaround for whatever the software can't handle.

None of those things necessarily seem like a big deal at first. Over time, though, they can add up to a much bigger problem.

So how do you know when it makes sense to keep working with off-the-shelf software and when it's time to consider something custom?

SaaS Works Until the Compromises Start Getting in the Way

There are plenty of situations where an existing SaaS product makes sense.

“If an existing product can get you 90% of the way there without preventing growth or increasing costs, go for it. Custom software starts to make sense when you’re spending too much time working around the limitations of what’s already available.”— Jacob Dahl | VP of Sales & Marketing at Onsharp

SaaS also gives businesses the opportunity to solve a problem without making a large upfront investment. It's relatively easy to implement and, importantly, lower risk. You can try a product and move in another direction if it doesn't work. When you're still figuring out what you need, “good enough” can be better than making the wrong call on a large custom software project.

The problem comes when the compromises required to use that software start affecting the business.

Maybe employees have to enter the same information in two different places because your systems don't communicate. Maybe a spreadsheet has become a permanent part of a process because your primary software can't handle it. Or maybe you've added several different products over the years, each solving one small part of a larger problem.

At some point, you aren't really using an off-the-shelf solution anymore. You're using an off-the-shelf solution plus all of the things your team has built around it to make it work.

That's an important distinction.

Look at What It Takes to Make Your Software Work

It's easy to look at a SaaS subscription and know exactly what you're spending. What is harder to see is everything happening around that subscription.

Let's say employees need to export information from one system, clean it up in Excel and then enter some of that information into another system. Doing that once doesn't seem particularly significant. But if it's happening every day across several employees or departments, the amount of time spent compensating for the software can become substantial.

Those workarounds are important because businesses don't always put a price tag on them. One of the first things worth doing is putting a number on the time employees are wasting working within the limitations of the software.

The same thing happens when businesses add more technology to solve individual gaps. Companies can end up stringing multiple solutions together because individual products can't conform to their unique use cases. One platform handles one part of the process, another handles something else, and an integration connects some of the information between them. Before long, a process that should be fairly straightforward depends on four systems, a spreadsheet and a person who knows how everything fits together.

That's why the cost of SaaS isn't always just the subscription price. It's also worth looking at the employee time, manual work, additional software, integrations and other processes required to make it fit your business.

And as a company grows, those gaps usually become harder to ignore.

Growth Can Expose Problems That Weren't Problems Before

Software that worked well when your business was smaller isn't necessarily going to work the same way forever.

One of the points where a business should start questioning its existing software is when costs are increasing while its usefulness is decreasing, or when the software begins preventing the business from growing beyond its current stage.

You may have more employees using it, more customers moving through it or more data that needs to be managed. You may have added locations, services or entirely new business processes. An acquisition might introduce another system that now needs to work with everything else.

Even small inefficiencies can become much bigger at scale. A manual task that takes a few minutes isn't necessarily a concern when it happens occasionally. When it happens hundreds or thousands of times, it becomes a different conversation.

Eventually, it can be worth asking whether adding another product is actually simplifying the process or just adding another layer to it.

Frustration Alone Isn't a Reason to Build Custom Software

There is a difference between being frustrated with software and having a business case for replacing it.

No system is going to be perfect. Before making a significant investment, you need to put a number on the time being wasted because employees are working within the limitations of the current software.

Then look at the bigger operational impact. Are those limitations slowing down customer service? Are they making it harder to get accurate information? Do you need more people to support processes that aren't scaling efficiently? Is there something the business wants to offer or change but can't because the current technology won't support it?

Once you start putting numbers and business outcomes around those problems, the conversation becomes much more useful than simply saying, "We don't like our software."

That's Where Custom Software Changes the Conversation

The biggest difference with custom software is that you don't have to start with the question, "How can we make this product work for us?"

You can start with how the business actually needs to operate.

That means looking at the entire process. What are employees trying to accomplish? Where are the bottlenecks? What information needs to move between teams or systems? Which manual steps could be automated? What does the business need today, and what is likely to change as it continues to grow?

From there, the software can be built around those needs instead of forcing the process into whatever features happen to be available in an existing product.

That doesn't mean recreating every existing process exactly as it is. In fact, replacing software can be a good opportunity to question why certain steps exist in the first place. Some may be necessary. Others may only exist because an old system required them.

The goal is to understand what the business actually needs and build around that.

The Financial Comparison Isn't as Simple as SaaS vs. Custom

It's important to be realistic about cost. Custom software is a significant investment, and if you're comparing only the price of SaaS licenses to the cost of building a custom system, SaaS may remain less expensive for a long time.

That's why we don't think license savings alone are usually the strongest reason to build custom software.

Maybe employees are spending hours every week entering or moving data manually. Maybe you're paying for several different products because no single solution handles the entire process.

Those costs aren't always as easy to see as a monthly software bill, but they matter when you're looking at the bigger picture. Employee time, manual processes, additional tools, integrations and missed opportunities can all factor into what your software is really costing the business.

Custom software comes with its own ongoing investment, too. It needs to be maintained, secured and updated as technology and your business change. That should be part of the decision from the beginning.

The difference is that you're investing in software you own and can continue evolving around your business, rather than continuing to add tools or workarounds to make an existing product fit.

So, When Is Custom Software Worth Considering?

There isn't one universal answer, but there are some good questions to ask.

How much of your process happens outside of your main software? How much employee time is spent working around system limitations? How many different solutions have you had to string together because none of them conform to your unique use cases? Are those limitations making it harder to grow, serve customers or introduce new capabilities?

And maybe most importantly, are you still choosing software based on how your business works, or has your software started determining how your business is allowed to work?

If your existing tools are doing what you need them to do, there may not be a reason to change them. But if you've tried SaaS products and continue spending too much time force-fitting them to your needs while still coming up short, that's a good indication that it's worth looking at the problem differently.

Another off-the-shelf product may solve another piece of it. Custom software gives you the opportunity to step back and solve the larger problem.

Start With the Problem, Not the Software

Deciding between SaaS and custom software doesn't have to begin with knowing which direction you want to go.

It starts with understanding what's happening in your business today.

Where are people losing time? Where are processes more complicated than they should be? What's preventing the business from doing something it wants to do? And are those problems significant enough to justify doing something differently?

Those are the conversations we have with businesses at Onsharp before deciding what should be built. Part of that conversation is helping businesses evaluate their options, and if we believe they'd be better served by something other than custom software, we'll tell them.

Because sometimes the problem isn't that you haven't found the right software yet.

It's that the right software for your business doesn't exist yet.