Software and business toolsYour software has aged, or never really matched the way you work?

A tool installed ten years ago, a package configured for a different organisation, files that make up for what the software cannot do: teams adapt, until the day the workarounds cost more than the tool. Kopus helps you decide what to keep, replace or build, and develops business software that fits the way you work.

Decision diagramReading the signs before choosing the route

The same signal can lead to three different decisions: a spreadsheet kept beside the tool sometimes reveals a simple gap, sometimes a foundation that has to be left behind. That is why every sign is read through the same four criteria before we give an opinion, and the migration is only prepared when replacement is genuinely justified. Maintaining what exists remains a full outcome, not a default choice.

Observed signs

  • Spreadsheets live beside the official tool
  • Data re-keyed across several screens
  • Requested changes never arrive
  • Only one person, or one vendor, can keep it running
  • No exchange with the other software

Reading on four criteria

  1. Technical foundationsoundfragile
  2. Cost of workaroundscontainedhigh
  3. Risksunder controlcritical
  4. Ability to evolverealblocked

argues for keepingargues for replacing

Cursor placed during the analysis, on facts

Three outcomes

  1. RepairImprove and maintain what existsWhen: Sound foundation, limited gaps
  2. ComplementA component connected to the tool in placeWhen: One precise gap, a core that holds
  3. ReplaceSoftware designed for your businessWhen: Costly workarounds, evolution blocked

Under "replace": the migration, without interrupting the business

  1. Data take-overWhat is taken over, cleaned or archived
  2. Consistency checksBefore any switch
  3. Parallel runIf needed, while everything is verified
  4. Training on your casesThe users, on their own files
  5. SupportThe first weeks
  6. Success measured by adoptionWorkarounds gone, information shared
Illustrative reading: the signs and criteria are the ones we examine; where the cursor lands on each criterion depends on your tool and your business.

What we seeThe signs that software is holding the company back

Teams keep spreadsheets alongside the official tool. Some operations require several screens and re-keying. The changes requested from the vendor never arrive, or come at a prohibitive price. The tool only works on one workstation, does not open up to other software, and only one person still knows how to keep it running.

These signals do not all mean that everything must be replaced. They indicate that it is time to look closely at what the tool really does, and what the business expects of it.

Our approachRepair, replace or complement: decide on facts

We analyse the tool in place, the data it holds, the processes it covers and the workarounds that surround it. Three outcomes are possible: improve and maintain what exists, complement it with a connected component, or replace it with software designed for your business.

The choice is made on the technical base, the real cost of the workarounds, the risks (security, dependence on one person or one vendor) and the tool’s ability to evolve with the company.

How we workSoftware that fits the business, not the other way round

When replacement is justified, we design the tool from the real work: the screens follow what users actually do, the business rules are yours, the connections with your other software are planned from the start. The scope is split so as to deliver a first useful set quickly, then extend it.

The code and the data belong to you, the documentation exists, and the tool can evolve without depending on a single supplier or a single person.

What you gainMigrate without interrupting the business

Data migration is prepared with care: what is carried over, cleaned or archived, the consistency checks, the period of parallel running if needed. Users are trained on their own cases, and the first weeks are supported.

Success is measured by adoption: workarounds that disappear, information finally shared, teams that no longer need to outwit their tool.

An iPad app for the field sales force iPad app

An iPad app for the field sales force

See the project

ProjectProject: from files and paper catalogues to a single application

For the sales representatives of a major international sports brand, every store visit relied on files, paper catalogues and email exchanges with head office. Kopus designed an iPad application that brings together everything a representative needs to know and do in store, the outlet’s profile, key products, restocking, promotions, and feeds the information back to head office. A tool suited to the job in place of a pile of makeshift means.

Your questionsFrequently asked questions

Ask a question

Do we have to replace everything at once?

Rarely. A component connected to the existing system, or a first module that replaces the most painful part, is often safer. A full replacement is prepared in stages.

Our data is in an old system. Can it be recovered?

In most cases, yes, by export, by direct access to the database or by processing the files. Feasibility and the clean-up work are assessed during the framing phase.

Isn’t custom software more expensive than an off-the-shelf package?

At purchase, sometimes. Over time, you have to compare licences, adaptations, workarounds and the cost of a tool nobody uses well. We do that calculation with you before recommending a route.

Who maintains the software afterwards?

Kopus can provide maintenance and further development, or hand over the documented code to your team or to another provider. You are not locked in.

Related servicesThe services that address this challenge

Let’s bring your projects to life

A tool that works for your teams, not against them.

Tell us about your current software, what it does not do and the files that make up for it. We will tell you what it is reasonable to keep, complement or replace.