Water delivery, end to end
Company operations platform · architecture, monorepo, bots, 1C integration
A delivery company with a long history. Orders lived in a notebook and phone calls. Now it is a platform: customers order through the site or a Telegram bot, dispatch builds routes, drivers run their deliveries from a phone, and stock and counterparties sync with the 1C sitting in the client's office.
How it worked before
Orders were taken by hand and passed to drivers over a messenger. Where the water was, and whether it had arrived, was known only by calling the driver. The books lived separately and were reconciled by hand at the end of the day.
What made it hard
The client's 1C is unreachable from the internet, and doing without it is not an option: the accounting lives there. On top of that, five applications — site, worker, two bots and a connector — have to be one product while holding different rights to the data.
Engineering decisions
- 01
A local agent instead of a tunnel into someone's network
The connector runs inside the client's network, calls 1C over OData itself and initiates the exchange itself — not one port is opened outward.
- 02
The database boundary is held by a test, not an agreement
A CI guard fails if a bot or the connector imports the database client: they reach the platform over signed HTTP. Direct database access belongs to the web app and the worker only.
- 03
Queues instead of synchronous integrations
The 1C exchange and the notifications are retryable jobs, not a request that can hang the checkout.
- 04
Installed on a phone without an app store
A PWA with a service worker and push: the driver has an app on the home screen, and updates arrive by deploy rather than by store review.
Documentation as part of delivery
22 documents: architecture, schema, roles, API, user flows, operations, staging, diagnostics — and a separate set for 1C: the integration contract, a discovery checklist, a playbook for the call with their programmer, a rollout runbook.
Where it stands
The platform runs in production on live traffic: orders, routes, bots and notifications. The 1C exchange has passed discovery and its integration contract and is in final validation.
- A multi-tenant restaurant platform: app, back office and three workers45,000
- A travel agency: its own catalogue, booking in three steps27,000
- Water delivery, end to end22,100
- A clinic: 52 pages, an assistant and a smile simulator14,500
- An outreach automation engine11,000
- A relationship CRM with an AI assistant10,400
- Direct-message sales run by an AI4,800
- Daily quests with an AI game master3,700
- A catalogue that updates itself3,300
- A platform for authored training programmes3,300
- A funnel that qualifies the lead itself2,900