Every piece of software has an owner and a handover path, so your important tools don't depend on a single person.
Before rollout, see exactly what a tool reads, writes and impacts so teams can safely approve and share it.
See every approved bespoke tool, which team uses it, what data it touches and where it fits in the company.
Keep the prompt, builder, data sources, permissions decisions and change history attached, so each tool stays maintainable.
Anything a teammate built to do real work — dashboards, scripts, bots, spreadsheets that grew into apps, or full internal applications built with Cursor, Claude Code or Replit.