After the sale
Warranty and service cases from serial number to reply: repair route, spare part, recall, claims against the manufacturer.
In the end a process runs on rules instead of habit. It takes three steps, and you can stop after any of them.

We map the process as it really runs: who is involved, which data it needs, how often it occurs, where it snags. Read access, nothing more.
You get: the process as a map, the points where time or money is lost, and an order of what comes first.
Every decision in the process becomes a rule with condition, consequence, occasion and date. Plus checkers that report when a result breaks a rule, and that are themselves tested against a deliberately planted error.
You get: your rulebook as a file. Your team can read it, a machine can check it, and it belongs to you.
The rulebook gets executed, by three kinds of building block:
| Block | What it is | Example |
|---|---|---|
| Agent | a specialist with a craft, a limit and its own rights | Leo runs your visibility |
| Skill | a fixed procedure that runs the same way every time | the reply to a customer review, from the case file to the text |
| Tool | a program that calculates, checks or writes without guessing | a checker that counts every figure against its source |
You get: work done to your rules. Every change to your systems arrives as a preview first and runs only after your approval.
An example from this site: every figure here sits in a file with source, counting rule and date. A tool recounts them on every build, and if one is off, the build fails.
Warranty and service cases from serial number to reply: repair route, spare part, recall, claims against the manufacturer.
Basic settings, product and order data, theme and templates, copy and translations across every language.
A document store that maintains itself, analyses from shop data, and recurring reports that are no longer assembled by hand.
Commercial and customs documents generated from rules, freight costs per shipment checked against what was agreed.
Each app is a rulebook with an interface: the rule lives as data in the shop, the app executes it. We develop and provide them, the shop owner installs and runs them. Three of them run today in the admin of a shop that is not ours.
Buy a device, pick a free gift with it, one per device. The app puts it in the cart and removes it again once the entitlement lapses. The merchant maintains the promotion: period, devices, gifts.
Installed and in operation.
The EU warranty label, mandatory from September 27, 2026. The app shows which product lacks a label and generates it from the Commission's original files. No server of its own, the data stays in the shop.
Installed and in operation.
On sold-out product pages the customer signs up and hears first when the item is back. The app stores nothing itself and requests no access to shop data at all.
Installed and in operation.
The access our specialists use to work in your shop. You switch its rights on yourself in the admin, per area: read, catalogue, content, service, finance. Switching off works the same way.
Tested in a live shop.
On a price reduction it shows the lowest price of the 30 days before. Only if every one of those days is on record. If one is missing, the app stays silent rather than guess a figure.
Built and tested, not yet rolled out.
Every outward effect waits there as a preview for a yes.
Counting only what is missing makes a catalogue look maintained when it is not.
Commissions with holding periods, bookings checked against people, places and load limits.
What you see is the kind of system, not a client's name. The same rule will protect your data later.
Bookkeeping and legal review for third parties. Both require a licence in Germany. We run them for ourselves, and for you we point out what we notice so you can pass it to your tax adviser or lawyer.