Work that replaced a chore people used to do by hand.

Because most of this work sits inside someone's operations, and a lot of it touches customer data or internal process. Naming clients and quoting numbers would mean asking them to be marketing material, which is not a fair trade for them. The problems and outcomes are described as they happened.

For client work, usually not, since the code belongs to them. On a call I can walk through the architecture and, where it fits, show something comparable running. Judging whether I can do the work should not depend on seeing a stranger's login screen.

Roughly two to eight weeks, depending on how many systems were involved and how much of the surrounding workflow had to be built as well. The pattern is nearly always the same: something working in the first or second week, then hardening it.

These three are typical rather than exceptional: document heavy operations, multi step processing, and workflows where someone re types the same information between tools. If your problem looks like one of them, it is worth a conversation.

Real traffic found things the demo never showed, as it always does. The first weeks are spent tuning retrieval and prompts, trimming cost and adding the exceptions nobody mentioned at the start. Launch is the beginning of the useful part, not the end of the project.