Business Pill · Keep watching after launch
Post-market surveillance means watching a product after it is on sale, in real use, not only before launch. The video shows a shop that tests a coffee machine for one afternoon, buys it, and finds months later that the coffee tastes bitter.
A short explainer video, under a minute. The shopkeeper and the helper are an illustration of the idea.
At a glance
What Post-Market Surveillance Is
Watching a product after it is on sale has a name: post-market surveillance.
Before and After Launch
The video sets two views side by side. Before launch there is one test, in a controlled place.
Why It Matters
The video turns this into one question: who is watching it after the test?
The Short Answer
A shop tests a new coffee machine for one afternoon. It works perfectly, so the shop buys it.
Months later, the coffee tastes bitter. The shopkeeper protests, but it passed! A helper says the test was one afternoon.
What Post-Market Surveillance Is
Watching a product after it is on sale has a name: post-market surveillance. It means watching the product in real use, not only before launch.
Before and After Launch
The video sets two views side by side. Before launch there is one test, in a controlled place. After launch the checking keeps going, in real use.
The board’s last row says what each shows. The first shows how it can work. The second shows how it does work.
The Idea in Parts
The lesson in its own parts
What Post-Market Surveillance Is
Watching a product after it is on sale has a name: post-market surveillance.
Before and After Launch
The video sets two views side by side. Before launch there is one test, in a controlled place.
The Honest Limit
A test is a snapshot. Watching only helps if someone reads the signals and acts on them, and it costs effort, every day.
The Honest Limit
A test is a snapshot. Watching only helps if someone reads the signals and acts on them, and it costs effort, every day.
Why It Matters
The video turns this into one question: who is watching it after the test?
Its takeaway is short. A test shows one day, so keep watching.
The key insight: A test shows one day. So keep watching.
The honest limit
A test is a snapshot. Watching only helps if someone reads the signals and acts on them, and it costs effort, every day.
The Business Engineer Lens
Where this idea sits in the Business Engineer library:
Where This Shows Up in AI Business Today
Our report on the UK government’s response on regulating AI in healthcare says the response describes a “conscious shift towards ongoing assurance rather than overreliance on pre-market assessments and passive adverse event reporting”. The report also says the MHRA’s AI Airlock page names post-market surveillance as its current priority regulatory challenge area.
This is the lesson’s idea in a new setting: a check before launch, and watching afterwards. The report presents all of it as the government’s own statements of intent, and this publication verified none of it independently.
The Question to Ask
- Who is watching it after the test?
How This Concept Connects
Layer 5 of 8 · Trust, Risk & Governance, on the Business Engineer Concept Map
- AI Evaluation as Acceptance Test contrasts with Post-Market Surveillance. An acceptance test decides before shipping; post-market surveillance keeps checking in real use because a test shows one day.
- Red Teaming (lesson unlocks soon) contrasts with Post-Market Surveillance. Red teaming attacks before launch and never proves there are no holes; surveillance keeps watching in real use.
- Kill Switch (lesson unlocks soon) contrasts with Post-Market Surveillance. Surveillance is the alarm that tells you; a kill switch is the owned stop that acts.
- The Notification Clock (lesson unlocks soon) builds on Post-Market Surveillance. Watching in real use is how a maker spots a flaw after sale, and the notification clock starts the moment it does.
Pragmatic Rigor vs Precision Theater
Ongoing checking over one-day tests.
Get the full Concept Map as a free poster.
Related Business Pills
See It in the News
UK Accepts All 44 Recommendations to Regulate Healthcare AI. The news story this explainer is embedded in.
All Business Pills
- The Memory Wall: Why a Faster AI Chip Is Not Faster AI
- Tokens per Watt: What an AI Data Centre Actually Produces
- Why AI Can’t Be Both Instant and Cheap: Latency vs Throughput
- The Model and the Harness: Why Same-Model Products Differ
- Context, Not Capability: Why a Smart AI Model Gives Poor Answers
- Discardable Software: When Code Is Cheap Enough to Throw Away
- Human in the Loop vs Human on the Loop: Supervising AI Agents
- The AI Audit Problem: When Making Work Is Cheaper Than Checking It
- AI Evaluation as Acceptance Test: How to Know It’s Good Enough
- Extensibility Is Control: Who Holds the Power in an AI Product
- RLHF Explained: How an AI Model Learns What People Prefer
- Pretraining Explained: How an AI Model Learns Before Anyone Teaches It
- Fine-Tuning Explained: How to Adapt a General AI Model to One Job
- Tokens Explained: The Unit AI Reads, Writes and Bills In
- Embeddings Explained: How a Machine Compares Meaning
- RAG Explained: How a Model Answers From Your Documents
- AI Hallucination Explained: Why Models State False Things
- Distillation Explained: How a Small Model Learns From a Large One
- Reasoning Models Explained: What Changes When AI Thinks First
- Tool Use Explained: How an AI Model Goes From Text to Action
- Capex and Depreciation Explained: Why Chip Lifetime Drives AI Profits
- Run-Rate Revenue Explained: What an AI Company’s Number Means
- Backlog Explained: Revenue That Is Signed but Not Yet Earned
- Switching Costs Explained: Why It Is Hard to Leave an AI Supplier
- Temperature Explained: The Dial That Sets How Predictable an AI Model Is
- Guardrails Explained: Rules Enforced Around an AI Model, Not Inside It
- Benchmarks Explained: Why a Test Score Is Not Your Own Result
- Agent Memory Explained: How an AI Assistant Remembers You Between Chats
- MCP Explained: The Shared Plug That Connects AI Models to Tools
- Quantization Explained: How a Large AI Model Is Shrunk to Fit
- Parameters Explained: Where an AI Model’s Knowledge Lives
- Scaling Laws Explained: Why AI Labs Keep Building Bigger
- Synthetic Data Explained: When a Model Writes Its Own Training Examples
- Transformers and Attention Explained: How AI Reads Every Word at Once
- Context Window Explained: How Much Text an AI Model Can Keep in View
- Prompt Injection Explained: When Text a Model Reads Gives the Orders
- Inference Explained: The Cost Paid on Every AI Answer
- Multimodal Explained: AI Models That Work With Images, Sound and Video
- AI Agents Explained: From Answering to Doing
- Open Weights Explained: Rent the Model or Run It Yourself
- Gross Margin Explained: What an AI Company Keeps From Each Dollar
- Usage-Based Pricing Explained: Paying for Work, Not for Seats
- Total Cost of Ownership Explained: Why the Cheap Robot Is the Expensive One
- Free Cash Flow Explained: Profit on Paper, Cash in the Bank
- Few-Shot Prompting Explained: Why Showing a Model Examples Beats Describing
- Knowledge Cutoff Explained: The Date Where an AI Model Stops Knowing
- Overfitting Explained: Why Memorizing Is Not Learning in AI
- Model Routing Explained: Sending Each Question to the Right AI Model
- GPUs Explained: Why AI Runs on a Chip Built for Video Games
- Data Labeling Explained: The Human Work Behind an AI Model
- Churn Explained: The Customers Who Leave Through the Back Door
- Customer Acquisition Cost Explained: The Price of a New Customer
- Operating Leverage Explained: Why Profit Grows Faster Than Sales
- Burn Rate Explained: How Fast Cash Goes and How Long It Lasts
- Computer Use Explained: When an AI Agent Operates the Screen
- Multi-Agent Systems Explained: One Agent or a Team
- Outcome-Based Pricing Explained: Paying for the Result
- Agentic Commerce Explained: When the Shopper Is an Agent
- Sovereign AI Explained: Who Controls the Model and the Data
- Context Engineering Explained: What a Model Sees Before It Answers
- Forward Deployed Engineers Explained: The Engineer Who Moves In
- On-Device AI Explained: A Model in Your Pocket
- Physical AI Explained: When AI Gets a Body
- Neoclouds Explained: Renting the Chips by the Hour
- Prompt Caching Explained: Why You Should Not Pay Twice to Read the Same Page
- Structured Output Explained: Why Programs Need a Form, Not a Paragraph
- Model Deprecation Explained: What Breaks When the Model Under You Changes
- The Jevons Paradox Explained: Why Cheaper AI Can Mean a Bigger Bill
- Take-or-Pay Explained: Paying for AI Chips Whether You Use Them or Not
- Least Privilege Explained: Giving an AI Agent Only the Access Its Task Needs
- Rate Limits Explained: Why an AI Product Can Stall in Its Busiest Minute
- Red Teaming Explained: Attacking Your Own AI System Before Someone Else Does
- Shadow AI Explained: The AI Tools Your Company Cannot See
- Data Flywheel Explained: When Using a Product Makes It Better
- Sale-Leaseback Explained: Sell the Asset, Keep Using It
- Mixture of Experts Explained: Many Specialists, Few at Work
- Binding Order Explained: A Promise With a Price on It
- Consent Explained: You Can Only Agree to What You Know
- Convertible Preferred Explained: Paid First, Able to Turn Into Shares
- Gross vs Net Savings Explained: What You Cut Is Not What You Keep
- Lead Time Explained: Why the Wait Is Part of the Price
- Matching Funds Explained: Public Money, Matched by Private Money
- Percentiles Explained: Why the Average Hides the Slow Ones
- Power Purchase Agreement Explained: A Steady Price for Power
- Synthetic Data Explained: Practice Made on Purpose
- The Residency Model Explained: Learn on Real Work, Then Be Tested
- Synergies Explained: Savings You Control, Sales You Hope For
- System of Record Explained: One Place Where Each Fact Is Kept
- Data Quality Explained: Fewer, Better Examples
- Financial Conditions Explained: Several Prices Pulling at Once
- Cross-Licensing Explained: You Use Mine, I Use Yours









