
One source of truth: how the site builds itself from the catalog
We had our services stored in the database and written out again on the website. Every change had to be made twice, and one side was always stale.
Blog
Craft notes on websites, software, AI automation and marketing. What works and what does not.

We had our services stored in the database and written out again on the website. Every change had to be made twice, and one side was always stale.

An agent that remembers everything is slow, expensive and confused. Designing what gets discarded turned out to be harder than designing what gets kept.

Idempotence, migrations, soft deletes, failing fast. Decades-old concepts that turned critical exactly when the one writing the code is not always human.

A rules file does not get written in one sitting. It gets written after each thing that breaks, and that is exactly why it works.

Giving an agent direct database access looks faster. It is, right up until the day a creative agent runs an UPDATE without a WHERE.

The most expensive decision in an AI system is not which model you pick. It is which parts you keep rigid and which parts you let reason.

A process that takes three days cannot live in the memory of a process that restarts on every deploy. Here is how we solved long-running work.

Every tool you add gets paid for twice: in tokens and in hesitation. Fifty available tools do not make an agent more capable, they make it more indecisive.

A client sent five pictures of their shop over WhatsApp and the agent stopped responding. The cause was not the model: it was what we let into the context window.
Tell us what you need and we'll tell you how we'd approach it. In minutes, not weeks.
No strings attached. The first chat is free and we reply right away.