Systems already in production. They can be installed again
Building from scratch means months and risk. Below is software that is written, debugged and running daily under load for other clients. It gets configured to your process in weeks.
Messenger sales with documents
The customer writes on WhatsApp, Viber or Telegram — the system takes the order and generates the invoice, contract, delivery note and waybill. The manager types nothing.
20 months in production: 260 orders worth UAH 22.2M, 196 documents, 3,332 conversations, 6 staff with role-based access. Figures read from the production database on 14.09.2026.
What you get
- —Messenger bot (WhatsApp Cloud API, Viber, Telegram): order intake, confirmation, reminders
- —Admin panel: orders, clients, statuses, staff roles
- —Document generation from templates — no manual typing of details
- —Data extraction from document photos, confirmed by the customer
- —Carrier integration and payment tracking
Who it fits: A manufacturer or wholesaler selling over messengers and drowning in paperwork.
Diwave Sales: demo, what is included, prices →Together with Diwave Marketing — an AI marketing team →Paying for a car wash from a phone
The driver points a camera at the QR code by the bay and pays — card, Apple Pay, Google Pay. No coins, no notes, no queue at the kiosk.
Built on a live self-service car wash network: bay controllers over Modbus RTU/TCP, the payment layer, per-shift till reconciliation. The terminal keeps taking payments when the internet drops and backfills once the link returns.
What you get
- —QR at the bay, payment in the browser — no app to install
- —Your own branded app if you want one
- —Bay control: start the programme, count the time, stop
- —Revenue reconciliation per bay, per shift
- —Offline operation with deferred delivery of transactions
- —Remote diagnostics: you see what the equipment is doing right now
Who it fits: Self-service washes, vending, parking, laundromats — anywhere a machine takes money.
Online store with warehouse sync
A catalogue of thousands of items, B2B pricing for wholesalers, two-way sync with the accounting system. Reserved stock cannot be sold twice.
The platform was built for a Polish plant nursery and runs on its market: Angular SSR over two Laravel back ends, seasonality, attributes, search and filters that hold at real volume.
What you get
- —Catalogue with attributes, seasonality, search and filters
- —B2B layer: personal pricing, deferred payment, purchase history
- —Two-way stock synchronisation with the warehouse
- —Server-side rendering — pages get indexed
- —Content admin panel and a separate dev contour
Who it fits: A wholesaler or manufacturer whose stock lives in an accounting system but has to sell online.
Figures are indicative. Hryvnia converted at the National Bank rate of 14.09.2026; dollar and pound via euro at the same rate.
Terms
What does "ready solution" mean?
The system is already written and running in production for another client. It gets installed, configured to your process, your data migrated and your people trained. This is not building from scratch — which is why the timeline is weeks, not months.
Why "from" rather than a firm price?
Because every implementation is priced on its own, and what previous clients paid is their commercial confidence. The figures above are a ballpark so you can see the order of magnitude and not waste time if we are not in the same range. I quote the exact figure after a conversation, once the scope is visible.
Three ways to work — pick yours
First: you buy the ready solution and want it adapted — the price is implementation plus the changes. Second: you want a monthly subscription instead of buying — the system stays mine, you pay for use and support. Third: you bring me into your team as an engineer — then it is not a product sale but a contract or a salary. Tell me which of the three is yours and the conversation moves twice as fast.
Name your budget up front — it saves us both a week
The most useful thing you can put in the first email is how much you are ready to invest. Not so that I fit the price to the number, but because the scope follows the budget: one figure buys one thing, another buys something else. Without it the first two emails are spent establishing it.
Who owns the code?
You own everything built for your project. The platform core stays mine and is licensed to you perpetually. Exclusive rights to the core are a separate agreement at a separate price.
How do we work and how is it paid?
A contract with my Ukrainian sole proprietorship or through Gnizdo Ltd (UK) — whichever suits your accounting. Payment in stages: an advance to start, the rest on delivery milestones. An hourly contract also works if you are adding me to your team.
What about support after launch?
A monthly subscription: hosting, updates, monitoring and incident response. The amount depends on load and how fast you need a response. The system runs without it too — but then you watch it yourself.
What if I need something slightly different?
Then we talk about what exactly changes. Half of these requests are settled by configuration, some by a week or two of work. If the task is genuinely different, I will say so rather than sell you the wrong thing.
Talk about your task
Dmytro Kravets, founder. I answer myself, usually within a day. Tell me the task and the budget — the first reply will already show whether this is your case and what it costs.