Working together
Four stages. The difference between them is a right in the system, not an agreement. You can stop at any stage.
| Package | Rights | What happens | What does not |
|---|---|---|---|
| Assessment | read | Process analysis with a written finding: what is missing, what costs money, what comes first. | Nothing in your systems is changed. |
| Department | read, execute | A rulebook and one to three specialists delivering drafts, reports and previews on an ongoing basis. | No write access. You implement, or you add effect. |
| Department with effect | plus write, per service | We write to your systems, every change as a preview first. | No blanket write right across all access points. |
| Ongoing operation | plus schedule | Recurring runs on a schedule, with evidence. | No run without the rights registered for it. |
How every change runs
Preview
Old value, new value, reason. Your system stays untouched.
Approval
You approve, amend or decline. Who approved and when is recorded.
Evidence
What worked, we measure on your side, with reference, date and source.
The rights are enforced when a specialist is loaded: a capability that writes is not loaded at all without the right to do so. Your data is marked as yours and travels in no package for another client. Separate databases per client are designed and not yet built; we will tell you when they are.
Getting started and price
It always starts with an assessment at a fixed price. A department starts at 2,500 euros a month. There is no price list, because the scope follows from your processes: how many, how often, and whether we should write or only deliver.
We take on few clients. When we are full, we say so.
Who it suits
Merchants with a real catalogue where the same work comes up often: product copy across hundreds of items, translations across several languages, service cases with recurring patterns.
Who it does not suit
Occasional work across many topics. An AI subscription is the better choice for that, and we would be too expensive.