ITLine

Case study

WPC Pont

A complete bespoke business system for a Hungarian trading-and-manufacturing company — from specification to production in 12 days.

Client
WPC Szaküzletek Kft.
Go-live
14 June 2026

A complete, bespoke business system for a Hungarian trading-and-manufacturing company: from AI interpretation of the incoming order e-mail through approval, documents, stock and delivery, to matching incoming payments. It runs in production, without a single interruption.

The delivery in numbers

9
days of specification
building the knowledge base from meetings and correspondence, before a line of code
4
days to a working system
from first orchestration to go-live — schema, auth, orders, catalogue, partners
811
commits in 12 days
with multi-agent orchestration, under senior supervision, behind quality gates
0
weeks lost since go-live
daily iteration, in-app release notes, continuous operation

The system today

10 000+
products in the catalogue
with an article-number system encoding size, colour and finish
333
reseller partners
with individual prices, terms and credit limits

Measured: August 2026.

What the system does

Every module is in live use. The list comes from the user manual, which documents only behaviour that actually shipped.

  • Orders

    The central workflow: order interpreted from e-mail, approval, documents, delivery, settlement. A three-panel view — the list, the incoming letter and the order data side by side.

  • Quotes

    Quotes with their own numbering, versioning and expiry tracking — as a phase of the same case, not a separate register.

  • Product catalogue

    A speaking article-number system by size, colour and finish, with colour variants, packaging units, partner-specific prices and stock levels.

  • Stocktaking

    Stocktaking and stock levels, usable on mobile — in the warehouse, not at a desk.

  • Partners

    Terms, individual prices, credit limits with warnings, payment deadlines, agent commission — per partner.

  • Documents

    Generating, sending and tracking proforma invoices, delivery notes, work sheets and invoices — every issued document in one place, with status.

  • Finance

    Automatic matching of incoming transfers to orders and documents, with operator approval and splitting across several documents.

  • Delivery

    Dispatch planning and a driver view on mobile: own runs, handover confirmation, movement between sites.

  • AI assistant

    Ask the system questions in natural language, run operations by written instruction — permission-bound and audited.

What it looks like

Screens from the working system, on fabricated data. The company names, people, addresses and amounts are all invented — no real customer or partner data appears in them.

Orders — the incoming letter and the order extracted from it side by side, with case data and delivery in a third panel.
Orders — the incoming letter and the order extracted from it side by side, with case data and delivery in a third panel.
Assistant — ask the system in natural language; the answer works from your own data, permission-bound and audited.
Assistant — ask the system in natural language; the answer works from your own data, permission-bound and audited.
Finance — incoming transfers matched automatically to orders and documents, with operator approval.
Finance — incoming transfers matched automatically to orders and documents, with operator approval.
Quotes — as a phase of the same case, with their own numbering, versioning and expiry tracking.
Quotes — as a phase of the same case, with their own numbering, versioning and expiry tracking.
Product catalogue — speaking article numbers by size, colour and finish, with colour variants, stock levels and partner pricing.
Product catalogue — speaking article numbers by size, colour and finish, with colour variants, stock levels and partner pricing.
My deliveries — the driver’s phone-first view: today’s runs, item counts, weight, longest piece, close-out with photos.
My deliveries — the driver’s phone-first view: today’s runs, item counts, weight, longest piece, close-out with photos.

How it was built

01

Knowledge first, code second

Nine days went into processing meetings, correspondence and domain walkthroughs before a line of code was written. Every specification started from the structured knowledge base, never from raw notes — and that is what made four days of development possible at all.

02

Orchestration, not faster typing

The system was built with multi-track, parallel AI orchestration: every work stream in its own worktree behind its own quality gates — build, test, end-to-end — and only work that passed got merged. The 811 commits are throughput, not haste.

03

Measured in production, not in a demo

Go-live happened on day 12, and from then on the system has worked on real orders. We measure the accuracy of the e-mail interpretation layer by replaying live orders against what the operator actually approved — not on a synthetic sample.

This is where the product came from

This project produced the interpretation layer we are now developing as a standalone product — and for which we are looking for pilot partners.

Article numbers from e-mail — the layer, on its own →