Client deployment

From a single outage to ongoing care of a studio’s system

Fixing the notifications uncovered more serious problems with payouts, staff access and billing. Today the system works in two locations, and I look after it and keep adding modules.

Client
Service studio · two locations in Switzerland
Duration
Ongoing care since February 2026
Illustrative image of the billing and payout panel — data changed for privacy reasons
Illustrative image of the application — for privacy reasons

Before

  • The same wages could be paid out several times
  • A new Google account immediately opened access to company data
  • Notifications stopped arriving
  • In rare combinations of dates, fees were charged twice

After

  • The payout and the zeroing of the balance happen as one operation
  • Every new person waits for approval and for the right access to be granted
  • Notifications work independently of the main platform’s limitations
  • Further modules added in stages, without stopping the studio’s work

Client testimonial · service studio, Switzerland

“We started with a single Telegram outage. Artur quickly understood the system and helped us put payouts, staff access, notifications and automations in order. Today the system runs more reliably and is easier for the team.”
Owner of a service studio · ongoing cooperation since February 2026 Translated from Polish

It started with notifications that did not work

The client runs a service company on a system that handles schedules, billing, payouts and messages to the team. They reported an outage of the notifications. While checking it, far more serious problems came to light — ones concerning money and access to company data.

What I found

  • A payout did not zero the balance. The same button could be pressed again, creating another confirmation.
  • A new person got access right after logging in with a Google account. The owner’s approval was missing.
  • Notifications from Telegram were blocked by the platform in use.
  • Some combinations of dates led to fees being charged twice.

I did not propose replacing the whole system. First I separated the critical bugs from the inconveniences and arranged the repairs so that the business could keep running without a break.

How the risks were removed

A payout either completes in full or does not happen at all

Creating the confirmation and zeroing the balance were combined into one operation. If any step fails, the change is rolled back. This way the system cannot leave half a settlement behind and allow the same amount to be paid out again.

Access only after the owner’s decision

A new user now lands in a waiting room. Only after approval do they receive the right role and see the data needed for their work. Having a Google account alone is no longer enough to get into the system.

Notifications independent of the platform’s limitations

Instead of fighting the block any further, I built a small intermediary module. It receives messages from Telegram, checks that they are valid and passes them on in a form the main system can accept. It runs separately, so updating one part does not switch off the other.

A history of operations the owner can see

The way fees are charged was put in order, and every change got a record of its time, source and type of operation. Thanks to this an unusual settlement can be checked without guessing what happened earlier.

The effect of the first repairs

The system stayed familiar to the staff, but stopped basing its safety on the hope that nobody clicks twice. The owner controls access, sees the history of settlements and again receives the notifications they need.

What came later

After the first repairs the cooperation turned into ongoing care. Every further module is a separate stage: the scope and the price agreed up front, then delivery without stopping work, and a warranty. Today two locations work on the same system.

  • Payouts in a few seconds

    Settling 210 items takes 3.9 seconds instead of over two minutes ending in an error.

    How I fixed it →
  • Nightly payout audit

    Every night the system checks the latest payouts in both locations by itself and raises an alarm only when something does not add up.

  • Lockers

    A locker calendar with a weekly or yearly fee. With one click the front desk adds it to the settlement or marks it as paid.

  • Meal orders

    Orders from the menu for each day, settled together with the payout. Whoever forgets to order gets a reminder.

  • Menu translations

    The weekly menu is entered once — the translations into the team’s languages are created automatically.

  • Telegram bots with a QR code

    An employee links their account to the bot by scanning a QR code instead of retyping a code by hand. Four bots in two locations.

A fix that found more

With one of the later changes, an automatic message was not going out for some new profiles. Four such cases were reported. Instead of fixing only the symptom, I added a separate view of incomplete data in the panel — and the system itself showed fourteen records with the same problem. Each went to the owner for review, and new profiles get the right settings from the start.

Part of the cause lay in an earlier change of mine, so I fixed it under the warranty, at no extra charge. That is how it works: if something within the agreed scope does not work, I am the one who fixes it.

The takeaway for a company

A tool built without traditional programming does not have to be thrown away when it starts serving a bigger company. But you have to know which elements can stay and which — especially money, permissions and personal data — need additional safeguards. After that, further parts can be added calmly.

Technologies in this project

Base44SupabaseDeno DeployTelegram APIOAuthRBACResend
Technical article

How a bug made it possible to pay out the same wages several times

Read article →

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