Software that moves medicines every day

A cold-chain quality operating system: one loop from signal to investigation and recurrence prevention, plus field warehouse audits from a phone.

Our own temperature-control ecosystem: a line of thermal containers, sensors, data-collection gateways and a web portal. Temperature, location, opening and shocks are visible in real time.

AI parses the incoming request, the calculation runs on current cost and tariffs, and a finished quote comes out. A human checks it and sends it.

The driver self-registers, the system puts them in a fair queue, assigns a gate and guides them with notifications. No dispatcher at the barrier.

An approvals engine: route, deadlines, owners, document pre-check and a decision timeline. You can see who is sitting on it and what the wait already costs.

The central exchange bus between systems: one message envelope, versioned contracts, idempotency, retries with backoff, a dead-letter queue and end-to-end tracing. No new infrastructure — it runs on the database you already have.

An orchestrator for the development cycle: intake, routing across repositories, change preparation, deterministic checks, review and a draft change in the repository. Humans step in at the start and at the end.

Publishing and viewing interactive reports with a structured catalogue and access rights. It computes straight from the database, with no separate BI platform and no licences.

The layer through which assistants and agents get safe access to accounting systems, CRM and external APIs over the open MCP protocol: a set of permitted operations rather than raw database access.

Every instruction and policy in one search: the system answers in the documents' own words and always shows the source. If the documents have no answer, it says so.

Merges into one picture what is scattered across five disconnected systems: the issue tracker, repositories, time tracking, assistant requests and the project office. One registry of people, one event feed and dashboards on top.

Not tickets but a case: client, shipment, deadline, owner, evidence. Deadlines recalculate automatically, escalation raises itself, AI drafts the replies.

A warehouse execution system: receiving, put-away, picking, shipping and handheld-terminal work. Rewritten on a modern stack so it can be developed further, not merely operated.

Computes cost and margin per lane and brings a prioritised action list: what to raise, what to hold for volume and where to check the carrier.

An electronic transport documents gateway: a finished trip becomes an electronic consignment note and goes to the state system through an EDI operator.

Automated checking of actual-cost documents: the carrier tariff on the trip date, the amount formula, mileage, duplicate requests and double payments. The result is a traffic light with an explanation; the decision stays with a person.

Takes a request from any source, assembles the electronic forwarder order in the tax-authority format, signs it and sends it through an EDI operator. Installs alongside your live transport system.

Line-haul planning rewritten from scratch: an engine computes capacity, temperature compatibility, time windows and cost; an agent brings a ready plan of consolidated runs and a human approves it in one click.

An internal service for access requests: a request is filed and walks its own approval route, with no phone calls or reminders.

AI parses inbound mail and requests, classifies them and drafts answers from the knowledge base. Simple cases close themselves; hard ones reach a human with the context ready.

A dedicated portal for couriers and carriers: assignments, route, documents and earnings. Fewer calls to the dispatcher and less paper in hand.

Cargo labels in one consistent format; scanning confirms receipt and dispatch and rules out mix-ups.

Selects the right thermal packaging for the cargo, temperature mode and route: less packaging waste and less risk of a temperature breach.

Warehouse photo capture of freight units: every shot is bound to the unit, time and order, so a dispute about cargo condition is closed with a fact, not a memory.

Tagging and tracking of thermal containers and cooling elements — no manual recounts and no lost reusable packaging.

Clients see shipment, delivery and request statuses themselves, download documents and stop calling the account manager over every detail.

Language models running on the company's own servers: data never leaves the perimeter, the cost per request does not depend on an external price list, and access goes through one gateway.

A dashboard of shipments where something went wrong: problem type, age, recipient, city. You see what to handle first instead of what caught your eye.

Tracking thermal boxes issued to and returned by couriers: who holds what, what is overdue and what never came back.

Tracking the return of signed documents for delivered orders: plan, actual and overdue by client. Money stops hanging because of paperwork.

Spending requests: a staged route, an approval queue and deadline compliance. A payment no longer hangs because somebody missed an email.

Accounting system configurations are exported into repositories: every change has an author, a history and a way back. A modification stops being an irreversible operation.

Stores and serves versioned playbooks to agents: a rule changes in one place and is picked up on the fly, with no service restarts.

Reconciliation of registers and settlements across systems: discrepancies are found automatically and land in a work list with the reason attached.

A microservice that computes transport department metrics: data is pulled from accounting systems on a schedule and the result is visible to the head of department and to finance.

A single page of key operational metrics for a screen in the office or the warehouse: it refreshes itself and can be read in passing.

Builds a map of corporate database structure: tables, domains, relations and lineage. Useful both to a person investigating and to an agent working with the data.

One home page for every HR service, with tiles and quick search: an employee no longer needs to know which system holds the task.

One registry of contractor agreements instead of a spreadsheet: terms, renewals, rate history, documents and alerts about what is about to expire.

Versioned definitions of the messages systems exchange. A contract describes the message, not the service code, so a system can be replaced without rewriting everyone who talks to it.

A team web workspace with an AI assistant: shared access, roles, working rules and action permissions. Staff work with the assistant inside the corporate perimeter, not in a public service.

Shared tokens, themes and components for every product: interfaces look and behave the same way, and a new screen is assembled from ready parts instead of being drawn from scratch.

Gathers requests marked 'ready to plan' into FTL trips and creates the trip in the transport system — a fast screen for one job instead of a general-purpose accounting UI.

Warehouse shift metrics on a screen: operations, pace, backlog. The shift lead sees a dip now, not in tomorrow's report.

A company financial model with scenarios: how a decision on tariffs, volume or costs will land in the result.

Cost calculation for last-mile delivery by route and courier — the basis for tariffs that do not run at a loss.

Dispatching and operational communications in one window: you see what is happening right now and where to look first.

The company's internal assistant: it answers from corporate data and helps with routine work without sending staff out to public services.

A recruiters' platform instead of a shared spreadsheet: who started, how probation is going, what is overdue and who should be introduced to the team.

One access point to the accounting core: external services reach 1C through a gateway by contract instead of connecting to the database directly.

A workspace for controlling temperature sensors per shipment: mode compliance, lost connection and free suitable sensors for replacement.

A management P&L assembled from accounting data instead of a hand-built spreadsheet that lands on the tenth of the month.

A live map of how systems actually exchange data: assembled from the data itself instead of drawn from memory. It shows the links nobody remembers any more.

Turns calls and meetings into text and prepares digests: agreements are not lost and conversation quality can be measured instead of debated.

The infrastructure layer: deployment, services and environment builds are described and repeatable. A new service is brought up from a template instead of being hand-assembled every time.

Receivables and overdue balances by client and ageing: you can see who to work with today, not at the end of the quarter.

A dashboard portal on how units work: load, output and trend, comparable across departments.

Computes a department's cash-collection metrics and distributes the bonus by accounting rules instead of by an argument at month end.

An interactive order report: plan versus actual, orders with no fulfilment, orders with no amounts and a year-on-year comparison.

Accumulates, day by day, the metrics clients actually pay for: delivery time, documents and cold-chain compliance. The question 'did it improve?' is answered with a chart, not a feeling.

Regular departmental reporting on one method: comparable numbers instead of a different spreadsheet for every manager.

Filing and processing HR requests — leave, certificates, documents — through the messenger people already use, with no trip to the HR office.

Tracking returnable packaging: where it is, who holds it and how much. Losses stop being an invisible cost line.

The service takes tasks from the change queue itself, does them, deploys to a staging environment and verifies the result — both code and live interface. It does not invent answers to open questions: it asks the owner and continues after the reply.

A customs clearance workspace on top of the accounting core: documents, deadlines and statuses in one place instead of email and folders.

A place where a new idea is tested on real data before anyone starts building it into a product.

The strangler-facade approach: a new service stands next to the working system, both compute in parallel for a while and the load moves across piece by piece. No business downtime and no big-bang cutover.

The voice agent answers the call, understands the question, looks up the request status in the system and replies by voice. Speech and reasoning run on separate hardware so the conversation flows without pauses.

Warehouse documents are recognised and parsed automatically: a person checks the result instead of typing it off the page.

Inbound accounting documents are recognised, parsed and reconciled automatically. An accountant reviews instead of typing.

Collects unposted carrier documents, matches them against operational facts and tariffs and assigns a traffic light with an explanation. Posting stays with a human.

Subscribes to bus events and assembles the whole case: status, timeline, stage owner and skipped steps. Domain data stays in the source systems.

Warehouse robots for patrols and readings: sensors in the physical space give an early signal where a person walks past once a shift.

Builds a passport for every service: what it does, where it runs, whether it is alive, what it talks to and who owns it. The question 'what do we even have' stops depending on an admin's memory.

Планирование заявки и заданий на перевозку в одном веб-рабочем месте: подбор транспорта, сроки доставки, формирование задания без обхода нескольких систем.

A system for internal policies and employee initiatives: versions, sign-off, review deadlines and rewards for accepted ideas.

A task and sprint board on top of the repository system: planning, estimation, decomposition and delivery visibility — while the repositories remain the single source of truth.

Flights, statuses, documents and monitoring for air freight in a system with history instead of manual spreadsheet work. Flight status tracking runs automatically.

An in-house recruiting platform: sourcing, screening, a first interview and a shortlist for humans. Built around maximum automation of the funnel.

Choosing a delivery mode across several transport types: comparison by transit time, cost and temperature risk rather than by an account manager's habit.

Orchestration of an agent team: a lead agent hands out work to workers, messages travel between them and stuck workers are cleaned up automatically. It works over every module and proposes actions in plain language.

A workspace for thermobox production: jobs, batches and assembly quality control, inside the same ecosystem as warehouse and transport.