Custom software examples for small businesses

The most common examples of custom software in a small business are five: an orders and stock system, a job or case tracker, a quote generator, a booking system with its own rules and a dashboard that brings data from several programs together.

These are types of project, not client cases. And all of them share a prior condition: that a ready-made tool does not solve the same thing.

Almost every project starts from the same place: a process of your own that no catalogue tool covers without bending it.

Orders and stock

A system where the order arrives, is prepared and deducts stock without copying data between programs.

Jobs or cases

A tracker for each job with its status, its owner and what is missing, instead of a spreadsheet that everyone fills in their own way.

Quotes

A generator that applies your rates and your rules and leaves the document ready to send, with a history of what was sent.

Bookings with their own rules

A booking system for when your availability rules do not fit a standard calendar.

A dashboard that brings data together

A single screen with what is today spread across several programs, so you can decide without opening four windows.

Among what the founder has built are websites, applications, content managers, ERP systems and automations, for IT, advisory firms, restaurants, the automotive trade, ports, retail, real estate, events, tourism and public bodies. Here we do not tell cases, but the type of project that tends to come up in each sector.

IT

A dashboard that joins alerts, inventory and tasks from several programs, or a portal where the client sees the status of their incidents.

Advisory firms

A tracker of cases and deadlines, or a document collection with reminders so it does not depend on chasing the client.

Restaurants

Orders and bookings with their own rules, stock control and a link between the till and the accounts.

Automotive

Workshop job sheets, quotes and service reminders to each customer.

Ports

A tracker of files and documents for each operation, with alerts on deadlines and on the status of each one.

Retail

A link between the shop, stock and invoicing, or an order dashboard with preparation and shipping alerts.

Real estate

A tracker of listings and viewings with alerts to the agent, or a portal where the owner sees where the handling of their property stands.

Events

A system for registrations, capacity and accreditation with automatic confirmation, or a dashboard of suppliers and tasks for each event.

Tourism

Bookings and availability with their own seasonal and rate rules, or a link between the sales channel, the accommodation or activity and invoicing.

Public bodies

A register of requests and case files with statuses and deadlines visible to those who process them, or an appointments and notices portal for citizens.

Often the right answer is to build nothing. Before commissioning software, check whether a ready-made tool is enough.

• If your process is the standard one in your sector, an off-the-shelf program already solves it and is easier to maintain.
• If a well-built spreadsheet covers what you need, nothing more is needed.
• If all you need is for two programs you already use to talk to each other, what you need is a connection, not a new program.
• If nobody has written down how the process works yet, that comes first: software only fixes what is already clear.

A good project starts by understanding the problem, not by choosing technology.

• Describe the process as it is today, with its exceptions, before thinking about how it should be.
• Ask what is delivered and what is put in writing: scope, deliverable and fee, agreed before starting.
• Ask for the system to connect with what already works, rather than replacing everything at once.
• Clarify who maintains it afterwards and what happens if the project stops.

The usual starting point is a preliminary analysis: understanding the process, seeing what options there are, including those that do not involve building, and deciding with data.

Custom software

How we work and what is delivered

What examples of custom software are there for a small business?

The most common are an orders and stock system, a job or case tracker, a quote generator, a booking system with its own rules and a dashboard that brings data from several programs together. These are types of project, not client cases.

When is custom software worth more than an off-the-shelf one?

When the process is your own and is what sets you apart, when catalogue tools force you to work in a way that is not yours, or when several tools do not talk to each other and someone stitches them together by hand. If your process is the standard one, buying is usually simpler.

Does custom software replace what I already use?

It does not have to. The usual approach is to build a piece that connects to what already works and solves only what is not covered. Replacing everything at once is riskier and is almost never needed.

Can a custom ERP be built for a small business?

It can, in modules, but it rarely makes sense to start with a full ERP. First it is compared with an off-the-shelf ERP and with extending the one you have; if building is worth it, it is done piece by piece and connected to what exists.

How do I know whether my case needs custom software?

Describe your process and check whether a catalogue tool, a well-built spreadsheet or a connection between programs already solves it. If none fits without bending your process, a preliminary analysis will tell you clearly whether building makes sense and where to start.

How much custom software costs and what drives it

What the price of custom software depends on, how to estimate it rigorously and how to compare two proposals without being sold an invented number.

When the spreadsheet stops being enough

A four-step ladder to decide when to move from Excel or a spreadsheet to a tool, an automation or custom software.