Website, custom software or a SaaS product: which one do you actually need?

"We need an app" can mean a five-page company website, an internal tool for ten employees or a subscription product for thousands of customers. These are very different projects in cost, timeline and long-term responsibility. Naming the right category early is one of the most useful decisions you can make.

A website: your public presence

A website explains who you are, what you offer and how to reach you. Its main jobs are clarity, trust and being found. Content is mostly the same for every visitor; the interactive parts are usually forms, galleries, maybe a booking request or a blog. A modern website should be fast, accessible, work well on phones and be easy for your team to update.

Choose a website when the main goal is to present your business and turn visitors into enquiries. Many businesses that ask for "a system" actually need a very good website first.

Custom software: your own way of working, automated

Custom software supports how your business operates: managing orders, bookings, stock, customers, approvals or reports. It has users with different roles, data that changes every day and rules specific to your company. An admin panel behind a website, a customer portal and an internal operations tool all belong here.

Choose custom software when spreadsheets, messages and manual steps are slowing you down, and when off-the-shelf tools force you to change a process that is actually a strength of your business.

A SaaS product: software you sell

A SaaS product is software that other companies or people use and usually pay for by subscription. Besides the core features it needs accounts, onboarding, billing, permissions, support tools and a plan for growth. It is a business in itself, with ongoing development long after the first launch.

Choose a SaaS product when the software is the thing you sell. Expect to start with a focused first version and improve it based on how real users behave.

Questions that separate the three

• Who uses it: anonymous visitors, your own team, or paying customers?
• Does each user see different data after logging in?
• Does it replace a manual process, or present information?
• Who will be responsible for it in two years, and how often will it change?
• Is it a cost of running your business, or a product that earns revenue itself?

Mixed projects are normal

Many projects combine categories: a website with a booking module, a store with a custom admin panel, a product with a marketing site in front of it. That is fine. What helps is knowing which part carries the most risk and value, and building that part with the most care. Sometimes the right first step is a website plus one small, well-built tool, rather than a large platform.

Avoid paying for complexity you do not need

Every login, role, integration and automation adds design, development, testing and maintenance. Before adding one, ask what happens if it is left out of the first version. Often the answer is "we handle it manually for a while", which is a perfectly good starting point. A smaller, solid first release that you can extend is usually better than a large one that is hard to change.

If you are unsure which category your idea belongs to, describe the problem in the brief and say so. Sorting this out is exactly what a discovery conversation is for.