Practice 03 · Web, software & digital solutionsCustom business software: one tool for one precise process

The workshop schedule lives in a shared workbook that three people edit at the same time. Quotes are prepared in a document template copied from the last one. Case tracking runs through an inbox and the memory of one manager. These arrangements hold as long as activity stays stable; they break the moment someone is away or volume increases. Custom business software replaces the arrangement with a tool designed for that process alone.

Get a first opinion on my software project

Feasibility and an order of magnitude within 48 hours

See the practice

Before and afterFrom a patchwork of files to a single tool

The same process, before and after. On the left, information exists in several copies and moves around by copy and paste. On the right, it is entered once, in a single database, and each person finds it on the screen that matches their role. What disappears above all is the question “who has the right version?”.

BeforeA process scattered across several media

Workshop_schedule_v7_FINAL.xlsx
RE: FW: RE: quote to review
Workshop_schedule_v7_FINAL (2).xlsx
Quote_template_copy.docx
Who has the latest price grid?
Typed again into accounting
File on hold: call the client back
Schedule changed (see attachment)

AfterA tool designed for that process

Case trackingRole: manager

Cases
Schedule
Quotes
Dashboard

24Open cases
5To approve
3Overdue

Case	Stage	Owner
D-0418 · North site call-out	Receipt	AL
D-0417 · Workshop quote	Review	MB
D-0415 · Quality inspection	Approval	CM
D-0412 · Customer claim	Closed	AL

History: D-0415 moved to Approval by C. M., 10:42

Single database

One single database
Permissions by role
An up-to-date dashboard
A history of every change

Illustration. The real screens are designed and then tested with your teams, on their own cases.

Who it is for, and whenWhen custom business software becomes necessary

The need shows up as one specific process that swallows a disproportionate amount of time.

Quoting and estimating: your quotes depend on grids, coefficients and options that only two colleagues master, and each one is rebuilt by hand.
Scheduling and resources: you assign technicians, vehicles or machines in a spreadsheet, and conflicts surface the same morning.
Case tracking: every client file passes through stages (receipt, review, approval, closure) without anyone knowing who is waiting for what.
Production and quality: work orders, inspections and non-conformities are recorded on paper and then typed up again.

The scopeWhat Kopus builds into a business tool

A model of the target process Stages, states, actors, deadlines and the documents produced at each step.
Working screens for each function Fast entry for the field, a supervision view for the manager, a dashboard for leadership.
Calculation and validation rules (price grids, consistency checks, alerts) coded once and applied everywhere.
Role-based access rights and an audit trail Who changed what, and when.
Document generation Quotes, work orders, job sheets, reports, in the format your customers expect.
Exchanges with the tools already in place (accounting, CRM, ERP, email) so that double entry genuinely disappears.
Migration of existing data, spreadsheets included, with duplicates cleaned out.
A mobile or tablet version when the process happens away from the desk.

The methodHow a business tool is built with your teams

Observing real work
We spend time with the people doing the job, look at the current files and note the workarounds, which reveal the true needs.
Ranking the friction
The most repeated tasks, the costliest errors and the bottlenecks are ranked; the first version deals with the top of the list.
Prototyping with the team
Clickable screens are tested by future users on their own cases before any development.
Building and gradual switchover
The software is developed in batches, each replacing part of the old file, with a period where both coexist.
Supporting adoption
Desk-side training, quick adjustments in the first weeks, official retirement of the old files.

Our positionOur conviction about business tools

A business tool is only worth anything if the people on the floor use it, and those people already have a method that works, however clumsy. Code alone is not enough: the tool must be faster than the spreadsheet for the daily task, speak the vocabulary of the workshop or the office, and its first users must have had a say in the screen design. A brilliant feature that is slower than the old way will be bypassed by the second week.

Your questionsFrequently asked questions about this service

What is business software?

A tool designed to support one specific operation of an activity (estimating, scheduling, tracking, producing), as opposed to a general-purpose product such as a spreadsheet or an email client.

Can we replace a spreadsheet without losing everything?

You can. Existing data is migrated and cleaned, and the spreadsheet’s calculations are reimplemented as verified rules. The old files remain available read-only during the transition.

How long do teams take to adopt the tool?

It depends on how far it departs from their habits and how involved they were in the design. Users who tested the prototypes move over without resistance, because the tool reflects the way they already work.