When tiny automations snowball

I set up a 12-line script last night to auto-tag support emails by product, and now two teams want to plug into it — what happens if this scales? Do we turn this into a mini service with SLAs, or let it stay scrappy and risk it becoming invisible critical glue?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍⁠‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‍​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍‌​‍‌‌‌​‍‌⁠‌‍‌‍‌‍​⁠‌‍‌⁠‌‌‌⁠‌​‌⁠‌‌‌⁠‌‌‌​​⁠‌‍​‌‌‍⁠‌‌⁠​‍‌⁠‌⁠‌‍⁠​​‍​‍‌⁠⁠‌​​

I’d give it a name, an owner, and a 1‑page README, plus a tiny SLO (e.g., tags within 2 minutes) and basic metrics/alerts — lightweight service without full SLAs. Who’s the on-call if three teams depend on it? That keeps the “invisible critical glue” from turning into load‑bearing duct tape.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍⁠‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌​​⁠​‍​⁠​‍​⁠​‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​⁠‍‌‍‍‌‌‌​​‌​‌‌​‍⁠‌‌‌‌⁠‌​‍​‌‌‌⁠​⁠‌‍‌⁠‍​​⁠​⁠​⁠​​‌‍⁠‌​‍⁠‌‌‌⁠⁠‌⁠‍‌​‍​‍‌⁠⁠‌