From a number log to a single place for project documents
Ariadna is SATEL PrO LLC's internal B2E system where a number, project data and all documentation live in one project card.

Context
SATEL PrO LLC runs projects for large customers. Every project accumulates contracts, technical documentation, training and marketing materials, source code and contact details. The files lived wherever they happened to be: on one person's drive, in another person's inbox, with deals and contracts in 1C. Documents were getting lost.
Everything is connected by a decimal number, a code such as SABU.620112.022 assigned to a project and each of its documents. The rules are defined by GOST and internal regulations: two identical numbers break accounting.
The task
The business refused to use the service because the necessary functionality was missing.
The goal was to turn a number log into a place where every project holds customer and deal data, its number and all related documentation.
One system for two user groups
Technical writers create projects, assign numbers and attach documents. They work in the system every day. Project managers and leads visit less often with one task: find a document or number for their project.
I designed data entry for the first group and the home page and search for the second.
Customer and deal data comes from 1C
Customers, deals and contracts already exist in 1C. Before Ariadna, people copied them manually, creating typos and mismatches. Ariadna receives this data through an integration, so a project can be created without leaving the system.
System directories come from 1C and cannot be edited in Ariadna. User directories, including GOSTs, documents, organisations and chief architects, are managed by technical writers.
Number assignment rules moved into the system
Previously a person assembled a number manually. I turned the rules into directories for GOST, phase, code and volume. The person selects attributes and the system builds the number. It is assigned automatically when a project is created.
Three steps to add a document
Showing every field at once exposes numbering logic even when it is irrelevant. The first step therefore branches between a GOST document and another document. The next steps select a document from a searchable directory, then add volume and a link.
All project materials in one card
Previously, collecting project materials meant searching multiple places: a personal drive, inboxes and the memory of the project owner. Now everything is tied to a project. A document is attached by a source link or file upload; PDFs and images open inside Ariadna.
Search follows what people remember
In the first version, search did not work and users had to browse the registry. People rarely remember a number, but they remember a customer, deal or manager's name. Search therefore works by any attribute directly in the table: each column, dates and multiple statuses at once.
A number cannot be deleted
An assigned number already appears in customer documents and cannot be reused. Deleting a project therefore marks the record as deleted but leaves it in the registry.
Outcome
The product was presented to company leadership and handed over to technical writers. According to colleagues, they still use the system after post-launch bug fixes.
The interface uses Flowbite with components adapted for the system. The library covered typical elements, leaving time for tables, search and record states.
Next case
SIZAR: call recording and conversation analytics
A B2B call recording and analytics system for quality control. I designed the product from scratch: logs, filters, the investigation view and dictionaries.
READ CASE