


For a period, saying you were an AI company was itself the pitch. Capital was abundant, the category was new, and the questions were about capability.
That period ended. Investors have now funded enough AI companies to know which ones work, and the diligence has become specific and uncomfortable: what is your gross margin, what happens when the next model release absorbs your feature, and is that revenue a contract or an experiment?
This guide covers what investors actually underwrite in AI companies, the three funding profiles the sector splits into, the compute problem, and the revenue-quality questions that decide rounds.
Classic software carries very high gross margins because serving one more customer costs almost nothing. That assumption underpins essentially every SaaS valuation multiple.
AI products built on inference break it. Every query costs money — tokens to a model provider, or GPU time on your own infrastructure — and that cost scales directly with usage. Companies building on third-party model APIs frequently find gross margins well below software norms, sometimes closer to a services business.
The consequences run through everything:
What investors want to see: unit cost per query or per task tracked over time, a clear trajectory of improvement, and a specific plan — model distillation, caching, routing cheap queries to smaller models, moving to owned infrastructure at scale, or pricing that passes cost through. Founders who present this proactively are far more credible than those who omit the line and get asked in week three.
Model capability was briefly a moat. It is not one now, because capability is a fast-depreciating asset — whatever is hard today is a feature in a foundation model release within a year or two.
The "thin wrapper" critique lands whenever a product is a prompt over someone else's model with a login page. It is frequently unfair, but you must answer it directly.
What investors now accept as durable:
Enormous capital requirements, driven by compute and talent. Funded by the largest growth investors, sovereign vehicles, and strategic investors — frequently with compute commitments forming part of the deal. A small number of companies, a category most founders are not in, and one where the capital requirements make conventional venture returns difficult.
Orchestration, evaluation, observability, vector and retrieval infrastructure, inference optimisation, data pipelines, safety and governance tooling. Conventional venture profiles and conventional software margins, with the specific risk that foundation model providers absorb your category into their own platform.
Investors underwrite this like developer infrastructure: adoption, expansion, and whether you sit above or below the layer that commoditises.
Where most companies and most funding are. Applying models to a specific industry problem — legal, healthcare, finance, logistics, construction, customer support.
Investors underwrite this like vertical SaaS with two additions: gross margin, and whether the domain knowledge embedded in the product is deep enough that a general model cannot replicate it. The strongest of these look less like software companies and more like outcome-based businesses in what they charge for.
Compute is the largest input cost for many AI companies, and it has produced financing structures that did not previously exist.
Founders should be clear-eyed that credits and compute commitments flatter early margins. Investors model what happens at list price, and so should you.
This is where the most rounds are lost, and it is entirely avoidable.
Enterprises have run large numbers of AI pilots. Budget exists, procurement is willing, and a founder can accumulate an impressive-looking revenue figure from experiments that will not renew.
Investors separate these ruthlessly. Expect to be asked:
A company with modest but genuinely committed production revenue raises more easily than one with a larger number built from experiments. Presenting the split yourself, unprompted, is a strong credibility signal.
Gross margin is not only a cost problem. Most AI companies with poor unit economics have a pricing model inherited from software, applied to a product whose costs behave nothing like software.
Four models are in use, and investors read your choice as a statement about how well you understand your own business.
Two pricing mistakes recur often enough to name. The first is flat unlimited pricing offered early to win logos, which converts your best customers into your largest losses and is extremely difficult to unwind later. The second is anchoring price to the incumbent software tool rather than to the labour cost of the work being replaced — an anchor that caps your realisable price at a fraction of the value you deliver.
Investors also look closely at whether you have ever raised prices. A company that has repriced an existing cohort and kept it has demonstrated something no growth chart can: that customers value the product above what they are currently paying.
Usually not, and training one is an expensive way to build a depreciating asset. Fine-tuning, retrieval over proprietary data, and strong orchestration deliver most of the benefit at a fraction of the cost. Own models make sense where privacy, latency, cost at very high volume, or genuinely specialised domains demand it.
Favourably, as an option rather than an identity. Running open-weight models on your own infrastructure can transform gross margin at volume and answers data-residency objections in regulated sectors, at the cost of engineering burden and a capability gap against the frontier that varies enormously by task. The credible position is that you have benchmarked both on your own evals and route by task — not that you are committed to either on principle.
Three questions before any others: what happens when the agent is wrong, who approves consequential actions, and how cost per completed task behaves as task complexity rises. Multi-step agents can consume many times the inference of a single query, so margin measured at demo scale tells you very little. Show cost per successfully completed task, not cost per call.
Less than founders hope, and occasionally it hurts. Free usage on an inference-cost product is a liability with a growth chart attached. Investors will ask what the free tier costs you every month and what proportion converts — and a company with a smaller number of paying production customers usually raises more easily than one with a large unmonetised audience.
Whatever gets you to evidence of production usage and a defensible margin trajectory. Rounds in this category have run larger than historical norms, partly justified by compute costs and partly by competition. Over-raising at a valuation you cannot grow into remains the same trap it always was — see our guide to down rounds.
It is now a standard question. Investors and acquirers ask about provenance, licensing and whether your invention assignment agreements cover AI-assisted work. Have a policy, and make sure your counsel has reviewed it.
It brings compute, credibility and technical access. It can also signal alignment that complicates relationships with their competitors, and it may constrain your infrastructure choices. Resist rights of first refusal over your company, and value compute-in-lieu-of-cash honestly rather than at headline.
Yes, and they are under-used. R&D tax credits apply squarely to this work, cloud credit programmes are substantial, equipment financing works for owned GPUs, and applied AI in defense, health and energy is directly fundable through SBIR and STTR.
The AI premium in fundraising has narrowed to companies that can answer three questions well: what is your gross margin and where is it heading, what do you still have if the model layer commoditises, and how much of your revenue is production rather than experiment.
Answer those unprompted, with numbers, and you are ahead of most of the market.
Global Capital Network connects AI founders with investors who understand these economics. See upcoming events or get in touch.



.png)




