Halo’s single-SKU pricing is a real differentiator — it removes a lot of the budget uncertainty that shows up elsewhere in this market. But for small, technically capable IT teams, that predictability comes with a catch: realizing Halo’s advanced value requires scripting skills, and for full AI capability, standing up and managing your own Azure OpenAI and vector database infrastructure.
Most meaningful configuration requires code, not clicks. Halo automations run through “runbooks” — custom, API-based integrations requiring knowledge of webhooks, SQL statements, JSON payloads, and scripting languages like PowerShell. Independent assessment describes this as workable for small technical teams doing simple automations, but breaking down for larger organizations. Realistically, that means budgeting for 2–3 dedicated script/SQL/JSON specialists just to build and maintain integrations.
Most AI capability requires you to run your own AI infrastructure. Many of the AI features within Halo do not leverage a default AI connection and require customers to bring and manage their own Azure OpenAI account and Azure AI Search infrastructure. That’s not a flexibility option; it’s a transfer of AI operations cost, effort, and risk onto the customer.