Starting digital transformation: a 90-day path for small and mid-sized companies

Most companies do not fail because they picked the wrong software, but because they start in the wrong place. A 90-day path from seeing the current state to one piece running for real, with measurable results.

Starting digital transformation: a 90-day path for small and mid-sized companies

Most small and mid-sized companies do not fail at digital transformation because they picked the wrong software. They fail because they start in the wrong place: buying a large system before anyone inside the company agrees on how the current process actually works. This article lays out a 90-day path to begin without betting the whole budget on the first attempt.

Digital transformation is not a software purchase

Digital transformation means bringing company data into one place, so every number has a single correct version. Software is only the tool. If sales, accounting and the management team each look at a different revenue sheet, adding a fourth system solves nothing.

A quick test: ask three people in three departments the same question — "how many orders did we ship last month?" If the three answers differ, the problem lies in process and data, not yet in technology.

First 30 days: see the current state clearly

No code is written in this phase. What matters:

  • Map the process as it really runs, not as the handbook describes it. Sit next to the people doing the work and record every step they actually take, including the workarounds nobody reports.
  • List where the data lives: spreadsheets on personal machines, chat groups, notebooks, the accounting package, email. Note who holds the master copy.
  • Count the repeated keystrokes: how many hours each week go into retyping data from one place into another. This number convinces a management team far better than any technology pitch.
  • Pick one pain point to solve first. Not the biggest one — the clearest and most measurable one.

Next 30 days: make one small piece run for real

The goal of phase two is not a finished system but one piece running in the daily work of a real team. For example: digitise only the payment request process, or only project progress tracking.

Three rules for the first piece:

  • One team, one process. The fewer departments involved at this stage, the better — each extra department adds another round of debate about the rules.
  • Replace, don't run in parallel for long. A few weeks of double entry is fine; a few months and both sides are wrong.
  • Define the finish line up front. For example: "by the end of the month every payment request goes through the system, no paper forms left." Without that line the project never ends, it only cools down.

Last 30 days: measure, fix, decide whether to expand

By now you have real data to answer the most important question: expand or stop. Worth measuring:

  • Average time to complete one case, compared with before.
  • Share of cases redone because of bad data.
  • How many people actually log in daily — the most honest indicator of whether the system is used at all.

If the pilot team goes back to spreadsheets the moment supervision ends, do not expand. Find out why: usually the system asks for more input than it gives back, or a common exception is not supported.

What breaks the early phase

Transformation projects rarely fail for lack of features. They fail because nobody owns the data.

Four mistakes show up most often:

  • No data owner. The customer list and the product list need exactly one person allowed to change them. If everyone can edit, nobody is accountable.
  • Digitising a broken process as-is. If an approval step exists only because there used to be no other way to check something, remove it rather than encode it in software.
  • Training once and never again. People forget within two weeks. You need someone in-house who knows the system well enough to answer questions on the spot.
  • Expecting reports too early. Good reports appear only once the input data is clean, usually after several months of real use.

Preparing for the next step

Once the first piece is stable, expansion raises harder questions: one integrated system or several specialised tools connected together, how far back to migrate old data, how to handle permissions as the user count grows. That is the moment to discuss a full management platform — with real data in hand rather than assumptions.

If your company is at the first step and unsure which process to start with, the NinePlus team is happy to review your current state with you before talking about software.

Back to all articles

Need advice on your specific problem?

What is written here are general principles. Your business has its own context - let the NinePlus team talk it through with you directly.