Doveryai case
Doveryai (formerly DD Phones) trades devices through its own storefront and a partner network, with its own warehouse, pickup points, courier delivery, and service centers. We built that IT infrastructure from scratch. DODVIR runs inside it: some operational processes are handled by our agents.
Context
The company sells devices to retail buyers and wholesale partners at the same time, and runs its own warehouse, pickup points, couriers, and service centers. Before us this lived on third-party sites and someone else's CRM: every part worked on its own, and the links between them were held together by people and spreadsheets. Mistakes at the seams are expensive — an item that cannot be sold, an order that cannot be assembled, a repair that gets lost. They needed one system where item, partner, order, delivery, and repair are parts of a single process with a shared history, and every participant sees their own slice and their own rules.
Custom development
- The customer marketplace: catalog, product page, checkout.
- The B2B portal: a partner registers one exact physical device and sends it to the marketplace.
- CRM and the operator console: item checks, work orders, and the state of the catalog.
- Warehouse and pickup points: intake, placement, and order handover.
- Courier delivery: routes and delivery statuses.
- Service centers: intake for repairs and status-driven work tracking.
- Payments, customer accounts, and the loyalty program.
This is not a storefront bolted onto someone else's CRM but the company's infrastructure: the system will not let you sell what is not physically in the warehouse, and it carries the history of one exact device from intake through repair to resale.
How DODVIR took part in the build
The run
Two weeks of autonomous work
May 2026. The system took a product goal and wrote the marketplace and CRM core for Doveryai: catalog, product page, orders, operator console. There was no split into CLI, SOLO, and MULTIAGENT back then — it was one agent.
- 2 weeks
- of autonomous work
- 294
- commits in the run
- ~180,000
- lines written by the system
- 16%
- of the platform today
What sits behind that: the platform today is about 1,120,000 lines, and roughly a sixth of it was written in that run. A third of the code it wrote is tests: the system hedged, because the run predates /goal. What that cost afterwards is below.
At the start this was a fast way to get both a working demo and a decently tested backend core: catalog, product page, orders, operator console. The system was noticeably weaker on the frontend — people reworked and rewrote the interfaces later. The run itself was held by our orchestrator: it set tasks, revived dead sessions, and kept the work moving, with Anthropic and OpenAI models running underneath. Competing IDE tools could not do that in May 2026: neither Claude Code nor Codex held a long run, they lasted a session.
The system did not always get the business logic right — some of it had to be corrected by hand. What it did set was the foundation and the style the rest of the platform was written in: service structure, code conventions, the approach to tests. That frame outlived both the rewritten interfaces and the three months of manual follow-up after the run.
The flip side of the same diligence is excessive coverage: one change in business logic drags several test fixes with it, and on change speed we sometimes move like a corporation rather than a startup. In exchange there are a lot of tests and the system is steadier for it. For a platform that runs a warehouse and money, we consider that a fair trade.
The main lesson went straight into the product. That run predates the /goal command: an operator could not yet hand the system a global goal that is held across an entire long run and that every piece of work is checked against. Without that anchor the system could not answer "is this even needed?" — so it hedged with tests. /goal exists as a direct consequence of this case.
Integration into business processes
A system nobody uses is worth nothing. So the third part of the work is not code:
- We worked through the processes with the customer: how operators, the warehouse, partners, and service actually work — before any of it became an interface.
- For three months we visited the client regularly, watched the work live, and took part in it ourselves, so the details came from the floor rather than from a spec.
- We wrote the rules of work and online instructions on the site itself, so an employee learns the system where they use it.
- We stayed on after launch and changed the system based on feedback from the people working in it every day.
- DODVIR agents inside the contour handle B2B partner assistance and operational routine in the CRM. Selectively for now: this is a pilot slice, not the whole operational flow.
What is running now
Doveryai marketplace
Customer-facing storefront for phones and accessories.
doveryai.dodvir.comB2B portal
Wholesale orders and partner accounts.
doveryaib2b.dodvir.comCRM / admin
Catalog, orders, and operations console.
doveryai-admin.dodvir.com/itemsService center
The post-sale side: device repair.
service.dodvir.comWhere it is now
The Doveryai platform runs in production and keeps growing. Every system linked above is live.