Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

AI companies can improve margins without throttling growth by lowering the cost of delivering a useful result, matching prices to customer usage and value, and making successful delivery more repeatable. Treat those as operating-design choices—not blanket cuts—and measure them alongside quality, latency, adoption, retention, and customer outcomes. No single tactic guarantees both better margins and continued growth.

Start with the right margin problem

Gross margin and operating margin answer different questions. Gross margin reflects revenue less the direct costs of delivering the product; for AI products, inference and cloud services can be major delivery costs. Operating margin also reflects operating expenses such as research and development (R&D), sales and marketing (S&M), and general and administrative (G&A) costs. A company can therefore improve operating leverage as revenue grows while infrastructure costs continue to pressure gross margin.

Measure economics at the level where decisions are made: a query, feature, customer, workload, or completed task. A low-cost query is not necessarily a good outcome if it fails, has unacceptable latency, or requires costly human support. Connect cost-to-serve with successful outcomes, customer value, and the product measures that show whether people keep using the product.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Make inference cheaper per useful result

Find the expensive work before changing infrastructure

Break down inference spend by feature, customer segment, and workload type. Identify which workloads drive cost, how often they are used, and whether spend is associated with successful tasks. Then compare ways to serve each workload against its quality, latency, reliability, and deployment requirements. There is no established, apples-to-apples benchmark here that identifies one best model or infrastructure provider across workloads.

Test routing, architecture, and utilization together

Potential levers include routing simpler requests to less expensive models, improving model architecture, batching or scheduling work where latency requirements allow, and increasing utilization of available capacity. These are hypotheses to test, not guaranteed savings. A change that lowers compute cost but worsens answers or slows the product can undermine adoption and retention.

Track the result as cost per successful task, with quality, latency, and reliability guardrails. Compare before-and-after performance on representative workloads; do not infer product-wide savings from a single feature or test. ICONIQ’s 2026 survey found that two-thirds of surveyed builders reported improved per-query unit economics, citing inference-cost management, model routing, and revenue growth as contributors. That is respondent reporting, not a controlled finding that any one approach caused the improvement. ICONIQ, State of AI: The Builder’s Economy (2026).

Distinguish near-term cost from infrastructure investment

Capacity, depreciation, and data-center operating costs can rise while a company builds for future demand. Microsoft reported a 66% Microsoft Cloud gross margin percentage in FY2026 Q3, citing continued AI infrastructure investment and growing AI product usage as downward pressures; efficiency gains in Azure and Microsoft 365 Commercial cloud partly offset them. Microsoft also reported 20% year-over-year growth in company-wide operating income for that quarter. These company results illustrate that infrastructure investment can weigh on cloud gross margin even as operating income grows; they are not a universal AI margin pattern. Microsoft FY2026 Q3 performance.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Alphabet likewise said infrastructure investment was increasing depreciation and data-center operating costs, including energy. Depreciation rose by nearly $6 billion, or 38%, from $15.3 billion in 2024 to $21.1 billion in 2025, according to Alphabet’s 2025 Q4 earnings call. Alphabet 2025 Q4 earnings-call transcript.

Price for usage and value without adding adoption friction

A subscription can make customer spend predictable, while consumption pricing can align charges more closely with usage and outcome pricing can tie payment to delivered value. A hybrid may preserve a predictable entry point while allowing revenue to rise with use or customer results. The best structure depends on customer willingness to pay, usage variability, cost-to-serve, expansion potential, and the predictability customers need.

Pricing patterns are shifting, but the evidence does not establish a universally superior model. ICONIQ reported that consumption-based pricing rose from 35% to 42% over six months and outcome-based pricing rose from 18% to 23%; surveyed companies blended an average of 1.7 pricing models. These are survey findings, not proof that switching models improves margins or growth for every company. ICONIQ, State of AI: The Builder’s Economy (2026).

Before changing packaging, model the effect on contribution margin, adoption, usage incentives, and revenue predictability. Check whether customers can understand and forecast a bill, whether heavier use creates positive contribution economics, and whether outcome measures are measurable and within the company’s influence. Watch actual conversion, expansion, retention, and cost-to-serve after launch rather than assuming a pricing change is neutral to product growth.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Scale repeatable delivery instead of custom work

Revenue scales more efficiently when the product and its implementation can be delivered repeatedly. Reusable software modules, hardware configurations, deployment patterns, and support processes can reduce engineering effort and delivery complexity. Keep customization where it creates meaningful customer value or strategic learning, but examine bespoke work that does not transfer to later customers.

A 2026 HKEX filing describes prioritizing higher-value engagements while expanding standardized product offerings, with reuse of hardware, software modules, and system configurations as the stated rationale for reducing engineering effort and delivery complexity. That is the issuer’s strategy and explanation, not causal proof that standardization alone produces margin improvement. HKEX filing dated March 16, 2026.

For each customer or implementation, track contribution margin alongside implementation time, customization, support burden, and customer value. Use those measures to decide which offerings to standardize, which to price as higher-effort engagements, and which to decline or redesign.

Manage operating leverage without indiscriminate cuts

Review R&D, S&M, and G&A against revenue and the outcomes those investments support. The aim is not to minimize each expense category; it is to make sure spending contributes to product differentiation, adoption, or scalable operations. Broad headcount or product cuts can remove capabilities that support future revenue, and the evidence here does not show that such cuts preserve growth.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

One HKEX-filed company reported overall gross profit margin increasing from 30.5% in 2023 to 32.3% in 2024 and 37.3% in 2025. Its adjusted total operating expenses, excluding share-based payment expenses, declined from 113.6% of revenue in 2023 to 83.4% in 2024 and 63.9% in 2025. The same filing reported 2025 total operating expenses at 107.7% of revenue, with share-based payment expenses a material factor. The adjusted and reported figures answer different questions and should not be treated as interchangeable. These are issuer-specific disclosures, not a general AI-company benchmark. HKEX filing dated March 16, 2026.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Use company examples as evidence of trade-offs, not targets

Published figures show why margin comparisons need context: company scopes, definitions, reporting periods, and investment stages differ. The following examples are useful for understanding possible cost pressures and operating choices, but their percentages should not be compared as if they were measured on a common basis.

Disclosure Reported figure What it does—and does not—show
Company-specific HKEX filing covering a track record period through September 30, 2025 Inference cloud-service costs were more than 90.0% of cost of sales in each year of the track record period. Cost of sales as a share of revenue was 124.7% in 2023, 87.8% in 2024, and 76.7% in the nine months ended September 30, 2025. AI-native product gross margin was negative 23.5% in the nine months ended September 30, 2024 and 4.7% in the nine months ended September 30, 2025. Shows how inference costs can dominate delivery costs for one issuer and how reported economics changed across its stated periods. It is not a sector average or a forecast. HKEX filing.
Amazon management statement about Trainium3 in its 2025 shareholder letter Management said Trainium3 was 30–40% more price-performant than Trainium2 and expected several hundred basis points of operating-margin advantage at AWS at scale versus relying on others’ chips for inference. A company claim and expectation, not independently verified realized savings. Amazon 2025 letter to shareholders.
Alphabet 2025 Q4 earnings call Alphabet said nearly 75% of Google Cloud customers had used its vertically optimized AI offering; AI customers used 1.8 times as many products as customers who had not used AI. Company-reported customer adoption and product-use figures; they do not establish that AI caused broader product use or margin improvement. Alphabet 2025 Q4 earnings-call transcript.

Build a decision loop that protects product growth

  1. Baseline the economics. Attribute delivery costs to workloads, features, customers, and successful tasks; separate direct delivery costs from operating expenses.
  2. Set guardrails. Define acceptable quality, latency, reliability, adoption, retention, and customer-outcome measures before a cost or pricing change.
  3. Choose a targeted experiment. Test model routing, architecture, utilization, packaging, or standardization against a defined workload or customer segment rather than applying a company-wide change by default.
  4. Read the trade-off. Compare unit economics with guardrails and contribution margin. If cost falls while task success, adoption, or retention worsens, the change may not be an improvement.
  5. Scale only what repeats. Roll out the approaches that improve economics without undermining customer outcomes, then monitor whether the gains persist as usage and capacity needs grow.

There is no single margin target appropriate to every AI company, and the reported examples do not establish causal proof that the levers above preserve growth. Use them to frame measurable operating choices, not as targets to copy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.