What Is Solution Selection?

Key points

  • There are multiple ways to build a system: SaaS, package software, scratch development, low-code, and no-code.
  • Which one you choose has a big impact on cost, development time, how customizable the result is, and how easy it is to maintain.
  • Comparing your options against clear decision criteria — rather than picking "whatever feels right" — is the first step toward a solution selection that doesn't come back to bite you.

Teacher Pochi uses tools like this at work every day, too

💼 Using office tools 📊 Business systems
SaaSI heard this time-tracking tool we use at work got rolled out really fast — how? Package SoftwareThis business system is customized a bit just for our company — how was that built? Scratch DevelopmentA system with unique features no competitor has — how do you build something like that entirely from scratch? Low-CodeHow did someone who isn't an engineer put this internal app together so quickly? No-CodeThis form was apparently built by someone with no programming knowledge — how does it work without a single line of code?

Why you need to choose a "way to build it"

When people hear "system development," many picture writing a program from scratch. In practice, though, there are many ways to bring a system to life — using a product or service that already exists, or doing only part of the development work yourself, to name a couple.

The budget, timeline, and team you'll need vary hugely depending on which approach you pick. Choose poorly, and costs or deadlines can balloon far beyond what was planned — or, in the opposite direction, you might end up with a system missing features it actually needs.

Teacher Pochi's hintIt's similar to the ways you can get a place to live. Build a custom home from scratch, buy an existing house and renovate it, or simply rent one as-is — the right choice depends on your goals and budget, just like it does here.

Decision criterion #1: Cost and development time

The first thing to weigh in solution selection is "cost" and "development time."

You need to think about upfront costs (development and setup) and ongoing costs (monthly fees, maintenance, and other costs that accrue as you keep using the system) separately. Generally speaking, the closer an option is to an off-the-shelf product, the faster and cheaper it is to get started — but the narrower the room you have to customize it.

Decision criterion #2: Customizability and maintainability

Another key criterion is "customizability" and "maintainability." You need to think about how much your company's operations differ from the norm, and how you'll handle spec changes down the road.

⚡ Speed & cost-focused No-code Low-code SaaS
🛠️ Freedom & uniqueness-focused Package Scratch

The more customizable an option is, the more freedom you have to build it exactly the way you want — but the heavier the maintenance and operational burden falls on your own team.

The big picture: five options

The ways to build a system can be organized into roughly five categories. From using an off-the-shelf product as-is to building something entirely custom, freedom and development time tend to scale together as you move along this spectrum.

No-code
Low-code
SaaS
Package
Scratch

The further right you go, the more freedom and customizability you gain — but cost and development time tend to grow along with it.

Comparing the five options at a glance

Here's each option summed up in a sentence. Each gets a deeper dive on its own topic page.

🧩 No-codeBuilt entirely through on-screen operations, no code required. The lowest freedom of the five.
🔧 Low-codeSome code is written for efficient development. Can handle more complex processing.
☁️ SaaSAn off-the-shelf cloud service used as-is. The fastest to adopt.
📦 PackageA business package extended with add-ons. Can be tailored to your company.
🛠️ ScratchBuilt entirely from scratch. The most freedom, but also the highest cost and longest timeline.

How to think about choosing

When actually choosing a solution, working through the following steps can help keep the decision organized.

Check how unique
the work is
Check budget and
time constraints
Narrow down
the candidates
Check maintenance &
operations setup

The basic idea is: for work that's fine being "the same as every other company," lean toward an off-the-shelf option; for work where your company's unique strengths really show, consider a more customizable option.

Common failure patterns

Some common mistakes people make in solution selection include:

  • Defaulting to highly flexible scratch development, only to see cost and timeline balloon far beyond expectations.
  • Choosing SaaS or no-code purely for low cost, only to discover afterward that a needed customization isn't possible.
  • Adopting a system without planning for maintenance and operations, then being unable to keep up once the person responsible for it leaves.

Teacher Pochi's hintIt's like renting an apartment for no reason other than "it's cheap," only to later realize there's not enough storage, or that you're not allowed to renovate. It's important to check whether an option actually fits your needs before you commit to it.

Summary

Solution selection is the work of weighing cost, development time, customizability, and maintainability, then picking the best fit among five options: SaaS, package software, scratch development, low-code, and no-code.

You can learn more about each option's characteristics on its own topic page below.

Related topics:

🏠 Back to top