Automation and AI

Foundation Model

Also called Base model

A large general-purpose model trained once on broad data, then adapted by many different products instead of built from scratch.

Quick facts: Foundation Model

Category
Automation and AI
Also called
Base model
Level
Intermediate
Affects
Tool selection, output consistency, vendor dependence, cost
Where to see it
ChatGPT, Claude, Gemini, and the model APIs behind most AI products
In this article4
  1. How a foundation model works
  2. Why foundation models matter
  3. Common mistakes with foundation models
  4. How to act on it

How a foundation model works

Training a capable model from scratch takes an amount of data and computing power that is out of reach for almost everyone. So a handful of organisations train large general models on very broad material, and everybody else adapts those. The general model is the foundation; the adaptation is the product. Adapting can mean instructions that shape its behaviour, a set of examples, a connection to your own documents, or further training on a narrower dataset.

The word to notice is general. A foundation model is not built for marketing, for Nepali, or for your industry. It arrives knowing a bit about almost everything and nothing about your price list, your stock or your customers. Whatever makes a tool feel specialised was added on top, and can usually be added on top of a different model too.

Why foundation models matter

They explain why so many AI products behave alike. When several tools sit on the same underlying model they share its strengths, its blind spots and its habits, so comparing them on output quality alone often tells you very little. The real differences are usually elsewhere: how the tool connects to your data, how it handles review and approval, what it costs to run, and who is liable when it is wrong.

They also explain a risk in your supply chain. If a tool you depend on is a thin layer over someone else’s model, its pricing, availability and behaviour are not fully in your vendor’s hands. When the underlying model is updated, output you had tuned around can change without anything in your own setup changing at all.

Common mistakes with foundation models

Assuming the model knows your business is the first. It cannot see your inventory, your bookings or last month’s campaign unless something deliberately supplies that information with each request. Anything specific it states about your company was either given to it or invented.

Buying capability twice is the second. Teams often pay for several tools that are wrappers around the same model, doing work a single subscription plus a decent brief would cover. The third is building a fragile process on top of exact wording. If your workflow depends on the model phrasing something a particular way, a routine model update can break it quietly, and you will find out from a customer.

How to act on it

Before buying, ask which model sits underneath, whether that can change, and what happens to your data. A vendor who will not answer is telling you something. Ask what the product adds beyond the model, because that is the only part you are genuinely paying for.

Then design for change. Keep your instructions, examples and rules in your own documents rather than only inside a vendor’s interface, so they can be moved. Check important outputs on a schedule instead of assuming last quarter’s quality holds, and keep a person approving anything published — the same discipline that makes automated content production safe. If your requirements are genuinely narrow, fine-tuning is one option, but it is rarely the first thing to reach for.

Do and do not

Do

  • Ask a vendor which model sits underneath their product
  • Keep your prompts and rules in your own documents
  • Re-test key outputs after an announced model update

Do not

  • Assume the model knows anything about your business
  • Pay for several tools wrapping the same model
  • Build a process that depends on exact wording

Questions people ask about this

Is a foundation model the same as a large language model?

A large language model is one kind of foundation model — the kind trained on text. Foundation model is the broader term and also covers models trained on images, audio or a mixture of these. In everyday marketing conversation people usually mean a language model, because that is what sits behind the writing and chat tools they use.

Should I build on a foundation model or buy a finished tool?

Buy first. A finished tool handles the interface, permissions, logging and support that you would otherwise build and maintain yourself. Building directly on a model makes sense when your process is genuinely unusual, when you need the output inside your own systems, or when volume makes per-seat pricing worse than usage pricing. Prove the workflow with a bought tool before paying to build one.

What happens when the underlying model is updated?

Output can change even though nothing in your setup has. Wording, length, tone and formatting may shift, and a step that relied on a particular phrasing can quietly stop working. Keep a small set of example inputs with the outputs you expect, re-run them after any announced update, and check them before a busy trading period rather than during one.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.