enceladus.ai
All posts
Tag

tools

  • What "enterprise" actually means on an AI licence

    The word is on every pricing page and it means different things on each. The five things an enterprise AI tier should give you, and how to tell which ones a given tier actually does.

  • Claude Code for engineering teams: a practical setup

    Agentic coding tools change how software is built, but only when the project instructions, standards, review gates and budgets are right. The setup we use ourselves, and recommend to clients.

  • Custom GPTs and Claude skills for a sales team

    The difference between a licence and a tool people use is configuration: assistants set up for the recurring work in a function, with its templates, its tone and its rules built in. Six we configure for sales, and the pattern behind them.

  • Rolling out Copilot by role, not all at once

    A licence for everyone on day one produces a bill and a shrug. A rollout by role, with champions, measurement and enablement on each function's own tasks, produces a change in how people work. How to sequence it.

  • No-training licence terms: what to check before you sign

    The contractual commitment that your data is not used to train the model is what makes enterprise AI tools safe to open. What the commitment actually covers, where it does not apply, and the six things to confirm at contracting.

  • Governed AI access: a model that works

    The alternative to blocking AI tools is not a free-for-all. It is five controls, all well established, that make enterprise AI safe to open and unlock the cheapest value in any AI programme.

  • Why blocking ChatGPT at work makes the data risk worse

    A blanket block on AI tools is the costliest governance decision we see. It does not stop AI use; it moves it to personal accounts the business cannot see, and it forfeits the cheapest value in any AI programme.