Client deployment

Recovering an abandoned, eight-year-old system

The system still served three points of sale and held the history of over 18,000 orders, but nobody wanted to develop it any further. After a four-day analysis I repaired it instead of building anew.

Client
Jerzy Czupik · company with three points of sale
Duration
4 days of analysis + 4 weeks of delivery
Illustrative image of the order system — data changed for privacy reasons
Illustrative image of the application — for privacy reasons

Before

  • Over 18,000 orders in a system nobody wanted to take over
  • No documentation and no verified procedure for backing up the data
  • Login dependent on an old external service
  • More than 10 defects and changes waiting for a contractor

After

  • All 21 agreed changes delivered
  • Order printout cut from about 15 seconds to under a second
  • The existing screen kept, so the staff did not have to learn the system again
  • Login under the client’s control, with no extra subscription
  • Data moved without stopping day-to-day work

Client testimonial

“The program works perfectly, and on top of that we are saving money thanks to the server change.”
Jerzy Czupik · owner of a company with three points of sale Translated from Polish

The system worked, but the company was left alone with it

Eight years earlier an external agency had built a system for handling orders at several points of sale. It replaced spreadsheets and paper binders, and over time became part of everyday work. When the original team stopped developing it, successive contractors looked at the code and walked away.

Meanwhile, the history of over 18,000 orders sat inside, and bugs and needed changes were waiting on the list. The client asked a sensible question: repair what is there, or throw everything out and start from the beginning?

First the analysis, then the decision

It could not be answered honestly after a short conversation. So I proposed a separate, four-day audit. I checked the code, the database and each of the 21 expectations. The client got a written report: what can be kept, what has to change, how much work each item needs and what risk further development carries.

The conclusion was simple: do not rebuild. The old system had its weaknesses, but its data and the working part of the screen were too valuable to pay for creating them a second time.

A repair without a revolution at the workstations

I replaced the part of the system the staff do not see, keeping the screen and the way of working they knew. The company got a safer base for development, but did not have to train the team or change habits overnight.

Within the agreed scope, among other things:

  • I fixed the reported bugs and removed unused elements,
  • I restored fast client search by phone number or surname,
  • I added safe changes of many prices at once, with a preview before approval,
  • I simplified printing of multiple orders,
  • I put staff roles and access to data in order,
  • I made login independent of the old external provider.

A move without downtime

The new part of the system was built next to the old one. Only after checking it on the same data did I switch the traffic over, and I kept the previous version for 72 hours as a way back. The change itself took about 15 minutes and happened outside working hours.

There was no need to retype data by hand or to stop the company for a day. The staff returned to the same address and a familiar view.

The result

  • 21 of the 21 agreed items were completed.
  • The order printout went from about 15 seconds to under a second.
  • The existing screen stayed unchanged, even though its back end was replaced.
  • The client regained control over user accounts and the further development of the system.
  • Data backups were made before every deployment change.
  • After acceptance the client commissioned further work, including the move to a new server.

What mattered more than the code itself

The biggest saving was not writing the new part faster. It was the decision about what not to rewrite. Keeping the working screen limited the cost, the risk and the disruption on the staff’s side.

The client received the full scope in writing, a fixed price for the delivery and the transfer of rights to the work done. With ambiguous decisions I asked the owner instead of hiding assumptions in the code.

For the technically interested

The new back end was built in Node.js and Express, keeping the existing way of exchanging data with the old React screen. The data stayed in MySQL. Login is based on passwords stored in a secure form and on signed sessions. The connection to the system is secured by HTTPS with an automatically renewed certificate.


Because of a confidentiality agreement I leave out the company’s name, its location, the data of staff and clients, and the details of the infrastructure. The numbers given come from the scope of the contract and the system’s data.

Technologies in this project

Node.jsExpressMySQLReact 15JWTbcryptCaddyPM2

A similar situation at your company?

Call and tell me what has to work.

You do not need to know the technical terms. The first conversation is free — I will tell you where I would start.

Before you pay, you see how it will work.

A free demo: a working demo, a mock-up, a cost calculation or a repair plan. Then a fixed price in writing and a warranty of at least 30 days on every stage.

If I don’t pick up, I call back the same business day.

← All case studies