Custom business software: creation, steps and price

What is custom business software?

Business software, or a business application, is a tool that serves one specific activity: scheduling jobs, tracking cases, managing an equipment fleet, approving orders, producing reports. It is “custom” when it is designed for your company, built from your business rules, your roles and your data, rather than bought as-is and configured.

In practice, it takes what already keeps your organisation running today — often scattered across spreadsheets, emails and paper — and makes it reliable: a single version of the truth, clear permissions, a history and useful exports. Our guide What is business software? sets out the difference with off-the-shelf software and a no-code tool.

• It applies your rules, your approvals and your exceptions, not those of a generic template.
• It shows each person the information they need, with the right permissions.
• It belongs to you: the code, the data and the accounts are in your name.

Examples of custom business software, by industry

Business software takes the shape of the work it serves. The examples below are common use cases, not client references: they show the kind of rules that custom software handles well and that a generic tool handles badly. Yours will start from your own documents, your roles and your exceptions.

Our own software, Trackary, is a public example: equipment fleet management software for construction equipment, with inspection tracking, defects, job scheduling and an offline mobile app for field technicians.

Custom software or off-the-shelf software: which to choose?

Custom business software becomes worthwhile when the same information circulates between files, emails and tools with no one sure which version is authoritative, or when your approval rules, your access permissions and your exceptions do not fit an off-the-shelf package. The aim is not digitising for its own sake, but making a process more reliable.

Custom is not always the right answer. If your business fits an existing package well, that package will be simpler to adopt and maintain. If a single spreadsheet still does the job, it may be better to keep it: our guide Replacing Excel with business software helps you decide. We compare these paths during scoping, before quoting anything.

The table below compares the two paths criterion by criterion. The table of three options further down adds no-code and spreadsheets.

Off-the-shelf, no-code or custom: three options

Between standard software and custom development, a no-code tool or a well-kept spreadsheet can be enough as long as the process stays simple. Here is when to favour each path.

The steps to create custom business software

We start with a day on site with the people who will use the tool. We look at the documents, the screens and the cases that cause problems, then write up the roles, the rules, the exceptions and the scope. This scoping document stays yours even if you then choose another provider. You do not need a full requirements specification to get started; if you want to prepare one, our software requirements specification template gives a plan to copy.

A first usable version arrives early and is deliberately incomplete. Your teams use it, flag what was missed and help reorder what has not been built yet. We handle data migration from the start, because new software without a reliable history does not really replace the old way of working. Training and operating documentation are part of the delivery. Details are on the Method page.

1. Observe and scope with the users, on site
2. Examine the data and produce the quote
3. Have a first usable version tested
4. Migrate the data, train users and go live
5. Evolve the software at the pace of the business

Creating business software: what to prepare

You do not need a requirements specification to start creating business software. A few things gathered before the scoping day, however, save a lot of time and make the quote more accurate.

• The list of people who will use the tool, and what each one needs to see or change
• The documents and files used today: spreadsheets, forms, exports from an old package
• Three or four real cases that cause problems, with their exceptions
• The tools to connect to: accounting, ERP, email, a client's or supplier's software
• Field constraints: working without a network, tablets or phones, photos
• The data to migrate and the history to keep
• What absolutely must work in the first version

What business software must cover

A business application is more than a form. It must show the right information to the right person, apply your business rules, accept legitimate special cases and make sensitive actions understandable. Depending on your business, it links data entry, approval, consultation and export, and can exchange data with other applications through an API if needed.

We distinguish what must exist in a first version from what can wait. This distinction protects your teams' time and avoids rebuilding an old package, flaws included, from day one. If your teams also work on site, the software can be complemented with a field app that works without a network.

• Roles and permissions suited to your organisation
• Explicit rules, exceptions and approvals
• History, search and exports useful day to day
• Migration of existing data (spreadsheets, old software)

Migrating your data without losing history

Data can come from spreadsheets, an old package or paper files. Before promising an import, we examine their shape and quality: duplicates, missing fields, contradictory values and links between files. You decide which information to keep, correct or drop; we then prepare the migration.

A file that looks clean can hide rules your teams apply without ever writing them down: a colour that flags an urgent case, a column added for one particular client, a comment that avoids an error. Scoping brings these practices to light before translating them into the new tool. If the software being replaced was built by another provider, also see our Software takeover page.

What price and timeline for custom business software?

There is no standard price, because there is no standard scope. The budget depends on the number of user profiles, the rules and exceptions to cover, the state of the data to migrate, exchanges with other tools and whether an offline mobile app is needed. A figure given without looking at these elements would be wrong one way or the other. Scoping is billed separately and you keep its results. Our guide How much does custom software cost? breaks down each item and explains how to compare two quotes.

The timeline follows the same logic. A first version can be put in users' hands before every function is finished, but the go-live date depends mostly on data migration and the scope chosen. The schedule is set after scoping, in batches, so you know what arrives first.

The schedule splits into phases. Their length is set after scoping; here is what makes it vary.

A concrete example: Trackary, built in-house

THE LEVEL CODE publishes its own business software, Trackary, equipment fleet management software for construction equipment. It brings together the equipment fleet, VGP inspection tracking, maintenance, defects and mechanics' scheduling, on the web and on mobile; the technicians' app works even without a network and syncs entries once the connection returns.

We designed it, built it and run it in production. It is the public proof of how we build business software: start from users' actual work, connect the field to the office, take care over migrating history. The page Trackary, our case study details what it does and does not do. Your software will not copy Trackary's features: we start from your own rules.

Your code, your accounts, and a possible exit

The source code is pushed to your repository from the first commit. Third-party service accounts are opened in your name; scoping deliverables and documentation remain yours. There is no licence, no exit fee, no code buyback, and no mandatory maintenance to keep using it.

Maintenance remains useful: live software needs fixes and changes. It is covered by a separate scope, chosen to suit your needs. We work from Lille for companies across France: scoping happens on site, then development and check-ins can happen remotely. See also Software development in Lille.