Custom software for your company: what it is and when it pays off

What “custom” means

A vendor writes an off-the-shelf program for thousands of companies at once. They guess how those companies work and ship a version that fits most of them more or less. A custom system I write for one company, after I have seen how the work is done there. It has exactly the screens, stages and names you use, and nothing else.

In practice that means a system that opens in a browser, on a computer, tablet or phone, with nothing to install. A panel for staff, a portal for customers, connections to the programs you already run, automatic documents and notifications. All of it built around your process, not around the process of a “typical company in your industry”.

When it pays off and when it does not

It does not pay off when an off-the-shelf program does what you need. Invoicing, email, time tracking: a custom system makes no sense there, and I say so on the first call. I would rather lose the job than build something you can buy on a subscription.

It pays off in four situations:

• The off-the-shelf program does most of your process and you handle the rest with workarounds. Why that is a double cost is on the page custom or off the shelf.
• Your process is your edge. Unusual stages, your own pricing rules, logistics no vendor has heard of. A ready-made program forces its own process on you, and you lose the thing you beat competitors with.
• Several programs do not talk to each other. Accounting, warehouse, shop, couriers. Each shows different figures and every week something does not add up. The system that ties them together is covered in the guide on connecting the programs in your company.
• You want to give customers online access. Job status, documents, bookings, payments, so the customer checks for themselves instead of calling. What such a customer portal looks like has its own guide.

If the company runs its process in spreadsheets and has outgrown them, that is a separate topic: a system instead of spreadsheets. A point-by-point comparison of when to pick a ready-made program and when to build is on the page custom or off the shelf.

What you get

The code, the documentation and every credential pass to you with each stage you pay for, not only after the last invoice. The system can run and grow without me, so if you ever wanted to change vendors, another developer could take it over. That is the difference between owning a system and renting one: stop paying for an off-the-shelf program and you lose access. Your own system keeps running.

You also get specifics in writing before we start: the process written down, the split into parts, the order, the timelines and the prices. That document is something you can take to another vendor to compare offers.

What the system is made of

Modules, meaning self-contained parts. Each module does one piece of the process and works independently of the others. Typical modules in the companies I build for:

• Order or job intake. One form for every channel: website, portal, email, phone.
• Staff panel. Lists, cards, statuses, roles and permissions, change history.
• Production, warehouse, schedules. Screens for a tablet in the field, on the shop floor or at a customer’s site.
• Customer portal. Status, documents, payments, repeat orders.
• Connections to other programs. Accounting, couriers, payments, shop, supplier systems.
• Automation. Email and text notifications, document generation, recurring reports.
• AI in the process. Reading documents, sorting requests, answering repeat questions. Where it pays off and where it does not is in the guide on AI in your company.

Modules go live one after another. You do not wait for the whole system to start using it.

How the work runs

1. A conversation. You tell me how the work looks today and what should change. You do not need a specification. What is worth having before the call is on the page how to prepare for a quote.
2. Scope and plan. I write the process down step by step, split the system into modules and give you the order, the timing and the prices. We start with what hurts most.
3. Building module by module. You usually get the first module to use after the first month. The team works on it for real, and their feedback shapes the next ones.
4. Launch and handover. The system sits on your server or with a provider we choose together. You get the code, the documentation and the credentials.

On larger projects I bring in people I trust for specific tasks. The system design, the decisions and the responsibility for the whole stay with me.

That is how the booking system for a kayak rental came about: online sales of trips, availability kayak by kayak, a rule for the vans that no ready-made program understood, and a panel the company has worked on for three seasons. And that is how the container tracking system at a terminal in Łódź works, where I have been responsible for the design and the build since the start in 2026.

How you pay

You pay for a module after accepting it, usually at month end. You do not pay up front for the whole system. Prices come in writing after the scope is agreed, separately for each module.

There is no price list on the site. A system for a company with three people in the office and a system for a company running production on two shifts are two different scopes and two different prices. What drives the price and how to bring it down is on the page how much custom software costs.

Risks and how I limit them

The biggest worry I hear from companies is “we will pay and the system will not get built, or will not work”. Three things in the way I work answer that directly.

Stages instead of the whole. You accept each module separately and pay after acceptance. If you change your mind along the way or the money runs out, you keep a working part, not a half-finished build.

A working piece, usually after a month. You do not get mock-ups and slide decks. You get a screen your team works on, and you see for yourself whether it is heading the right way.

Someone else can take over. Documentation, code and credentials pass to you with each stage you pay for. If I were unavailable, or if you wanted to change vendors, the work does not stop with one person.

If you want to check whether a custom system makes sense for your company, describe in the form below how the work looks today and what gets in the way. I will get back to you, including when the answer is “an off-the-shelf program will do”.