Operations | Monitoring | ITSM | DevOps | Cloud

If you were anywhere near LinkedIn last week, you probably saw us launch AI Signals. We weren’t exactly quiet about it. (Press release, a couple of blog posts, and more social posts than we’d like to admit. Sorry about your feed.) We covered the why behind AI Signals already, but I wanted to actually walk you through what you’re seeing on the screen. Sooner or later someone asks what the company spent on AI last month.

Cost per AI outcome is your total attributed AI spend divided by the business results it produced: resolved tickets, converted leads, merged pull requests. It includes the cost of failed attempts, sits at the top of the AI unit-cost ladder, and it's the number that makes vendor outcome pricing, ROI claims, and build-versus-buy decisions comparable.

If you set the budget for your team’s AI agent work, or answer to someone who does, you need a rough idea of what a job will cost before it starts. That’s hard to get. Stanford researchers found the same agent, given the same task, can use up to 30 times more tokens from one run to the next, and you usually find out afterward. Most developers just run the job.

When you have a question about your cloud or AI spend, you want an answer quickly, not a ticket that disappears into a queue. Support should not mean waiting for business hours, repeating your account details to multiple people, or wondering whether anyone picked up your message. That changed this week for every CloudZero customer. You get answers to most product and account questions immediately, at any hour, and when your question needs a person, they already have context.

There’s a specific kind of measurement problem worth naming precisely rather than dramatizing: this month we found that our model-routing agent was assigning a token budget to every unit of work, and that budget was noise in the strict sense. Fixing it meant improving a system that’s mostly right, not tearing one down.

September is associated with football, foliage, flannel and, for some, the Financial Plan. As we put pen to paper (or agents to harnesses), there’s a few core elements that have always driven the P&L outlook for the following year: rep productivity and new product releases driving new sales, expansion and contraction against the install base, employee roster changes, and discretionary spend.

Somewhere in your company, a team is three weeks into the AI project that’s going to matter. Somewhere else, a support pilot from the spring is still summarizing every ticket with a frontier model, and nobody has looked at it since it started working. On the invoice they’re identical, and the company has two moves: leave everything open, which funds the waste, or cap everyone, which kills the bet.

An LLM inference provider hosts open-weight models like Llama, DeepSeek, and Qwen behind a pay-per-token API, handling GPUs, scaling, and serving for you. The same Llama 3.3 70B model ranges from $0.10 to $1.04 per million input tokens depending on who serves it, so provider choice is a pricing decision. Top picks as of September 2026: Groq and Cerebras for speed, DeepInfra for price, Together and Fireworks for breadth, Baseten for custom models.

Build when the problem is narrow (one provider, one team, simple attribution) and the tooling is strategically yours to own. Buy when AI spend spans providers, arrives untagged, and needs unit costs finance will trust, because that build is a multi-quarter platform project with a permanent maintenance tail. Price both paths in engineer-years before deciding. CloudZero sells the “buy” side.

Perplexity pricing runs $0 for Free, $20 a month for Pro, and $200 a month for Max, with enterprise seats listed from $40 per user. Pro fits most people who search for work daily. Max exists for heavy automation. The prices are verified against Perplexity's live plans page as of September 2026. When Perplexity published a customer quote on its own pricing page, it chose an unusual one.