Projects

What we have built — and continue to maintain

The projects are described without client or brand names. All of them are in live operation and maintained by us.

Hospitality · Multilingual website

Boutique hotel site with direct bookings

A small hotel in Italy that until then had been filling its rooms almost entirely through booking aggregators.

Problem
Aggregator commissions were eating a substantial share of the margin, while room descriptions, rates and house rules were maintained in several different places and kept drifting apart. Guests arrive at any hour, late evenings included, and have to be able to get in without meeting anyone. Separately, the mandatory tourist-flow statistics were being filed by hand.
Solution
A multilingual site with direct bookings, wired into the hotel's booking system: rates, promo codes and availability are managed from one place, and the card payment is taken at the moment of booking. Self check-in — the guest registers in advance and opens the doors from their phone through a personal link, with entry instructions prepared in eight languages. Booking terms, the privacy policy and the cookie policy were written in six languages. Room descriptions and house rules are published simultaneously everywhere a guest can read them. Filing of the statistics to the government portal was automated, including cleaning up the inflated figures that had accumulated.
Outcome
The entire guest journey has been walked through live — from picking dates to a real card payment, online registration and receiving the key. Direct bookings carry no commission, manual reporting is gone, and inconsistencies between texts are now technically impossible.
Professional association · Platform, portal and migration

Leaving a rented system: platform, portal and archive for a self-regulatory organisation

An association with statutory delegated functions and around a hundred and forty active members. Its staff process court decisions daily and prepare documents on strictly defined templates under statutory deadlines, and part of the information the organisation is obliged to publish.

Problem
The work rested on a rented system from an outside vendor: the data and more than a hundred and thirty thousand files lived on the vendor's servers, and the platform underneath had long been out of support. Around a hundred and forty external users signed in through their personal accounts there every day. The website ran on a content management system more than a decade old — slow, with addresses that gave the CMS away, and with every edit going through a developer. Court decisions were read by hand, documents were assembled from the previous file, and deadlines were tracked by eye. The job started as a site migration and grew into leaving the rented system altogether.
Solution
A reporting platform with personal accounts of its own: each member sees their own documents from the archive, their applications and their correspondence, while staff see a shared queue with statuses. Court decisions are parsed automatically from PDF, documents are generated on the approved templates, the workflow has stages, roles and access rights, and the system itself warns about an approaching deadline and a newly arrived case. Separately from it — a public portal built around the organisation's four audiences: members, candidates, courts and creditors. Courts file their decisions electronically, the register of members is published from the platform's own database with a card for each member and a download as a table, and the figures on the front page are computed from the sources instead of being typed in by hand. All mandatory disclosures, news and documents were migrated off the old site with redirects from every old address, and an archive of more than a hundred and sixteen thousand files was moved into object storage.
Outcome
Preparing a set of documents went from hours to minutes, new cases are recognised and summarised on their own, and deadlines are tracked by the system rather than by someone's memory. The organisation is stepping out of renting someone else's system — the data and the archive return to its own perimeter. The public side lives separately from the application: mandatory disclosure stays available even when the application is down, and the register on the site cannot drift away from the reporting, because both read the same database. The portal is deployed and the switchover of the main address is being prepared.
On this project OPERCENTR OOD is the contractor for the digital product. The company does not practise law and does not act as legal representative.
Accounting · Document exchange

Handing source documents over to an external accountant

A company that passes its source documents to an external accounting practice every month, and until then had been doing it by email.

Problem
Email shows neither what has been handed over, nor what has been accepted, nor what is still missing: files get lost between messages, the same document arrives twice in different shapes, and the accumulated archive is effectively unsearchable. Contractual deadlines are tracked from memory, and handing over a period leaves no record to fall back on later. The two sides work in different languages.
Solution
A web service on our own server, where documents are uploaded once and then describe themselves: the system recognises the document type, the counterparty, the number, the date and the amount using its own rules, without the text of the documents ever leaving the server. A period moves through a clear cycle of states with contractual deadlines, requests for missing documents and per-document comments; notifications and reminders go out by email in two languages. The handover closes with a PDF transfer protocol, and the period can be downloaded as an archive with an itemised list. On top of that: full-text search across the whole archive, two-factor sign-in, an append-only action log, and backups with a nightly restore check.
Outcome
Handing over a period takes one action instead of a thread of emails, and its state is visible at any moment — what has been accepted, what is being waited on, which deadline is approaching. A re-uploaded document is recognised as a duplicate and shown to a person rather than counted twice. The archive is searchable, and every action stays in the log — when accounts disagree, there is something to go back to.
Technology

What we work with

We choose tools that will still be maintainable years from now — without extra layers that nobody but their author understands.

A similar task in your company?

Tell us what takes up most of your time — we will suggest what the solution should look like and roughly what it costs.

Describe the task How we work