Executive brief
Building an AI-native product
Six considerations for founders building on a language model: risk process, attacks, authority, evaluation and law, and what each asks of the design.
Executive brief
Eight checks an investor can run on a company whose product depends on a model, and what each one leaves unanswered
Investors who look at an early-stage software company are used to checking the entity, the cap table, the customers and the code. A product that depends on a model adds questions those checks do not reach, and this brief is organized around them.
It sets out eight checks, running from the model’s role and the data behind it to the supplier, security, proof of performance, public claims, regulation and ownership of outputs. Each check names the public sources behind it, describes the documents a company might hold, and says what that evidence cannot establish.
The sources come from standards bodies, regulators, a security project and model suppliers’ own documentation. The brief reports what they say and keeps its analysis apart, marked as analysis.
It makes no assessment of any company, offers no recommendation to invest, and names no company. It closes with questions to put to a company or to counsel.
This brief is general information for investors. It is not legal, tax or investment advice.
The chapters in reading order, and one public figure that frames the question the brief answers.
These figures describe the wider market, not WE's results.
The sections of the full brief, in order. WE sends the full text by email to the address you give.
This brief gives considerations for founders. It is not legal, tax or investment advice.
Tell WE where the company stands. WE replies to arrange a conversation and a written read of your company's timeline.
A short PDF of the charts and sources, sent by email to the address you give.
Talk to WE : A question that does not fit a form.