How We Work: Scope First, Then Care

This week we spent most of our effort on the Build page. We added a "How we work" section that lays out the sequence plainly: a Statement of Work first, then Apuna Care afterwards. The order matters. A project needs an agreed shape before anyone talks about ongoing support, and putting that in writing on the page saves everyone a round of guessing.

Alongside that, we revised our positioning copy in both the English and German dictionaries. The theme is bounded AI — KI mit klaren Grenzen. We would rather tell you where a system stops than imply it does more than it can. That honesty is the point, not a caveat.

We also made a small but deliberate call: the aquaristik case study is held back. It is split out from its original tickets and stays unpublished until the spec is settled and we have consent to use the client's work. Publishing without both would be the wrong trade. On the housekeeping side, the contact form bug is fixed — the missing API key was confirmed set — and the backlog now records our pricing and Care-tier thinking for the weeks ahead.