Why the second use case should cost a fraction of the first

Automation programmes usually stall for an economic reason rather than a technical one: every use case costs roughly what the last one did. When the tenth project costs as much as the first, the programme runs out of sponsorship before it runs out of ideas.

What actually gets reused

Reuse is often discussed and rarely achieved, because the reusable layer is not identified deliberately. In practice four things carry across almost every use case.

• Connectors and authentication to the systems the organisation already runs.
• The governed data layer — how information is ingested, permissioned and retrieved.
• Agent skills and workflow patterns, such as approval gates and exception escalation.
• The operational surface: logging, monitoring, cost visibility and release process.

The commercial consequence

When those four layers are built once, the marginal use case is configuration and tuning rather than construction. That is what makes an automation programme compound instead of plateau — and it is a reason to weigh architecture at least as heavily as the first delivery date.