Four domains I have actually shipped in
Agent reliability is mostly domain-independent — until it isn't. What changes by industry is which failure is unacceptable, what a security reviewer will ask, and which regulation now applies. These four are the domains I have actually shipped in, so each page carries the specific constraint rather than generic advice with the industry noun swapped in.
2,000
concurrent users on multi-tenant HR analytics
Regulated domain
HR technology
AI agents on HR data, where the data is the whole problem
The most sensitive non-medical data a company holds, in a multi-tenant product, read by managers about their own reports.
Conversational analytics over workforce dataAttrition and time-to-fill forecastingPolicy and handbook assistantsManager copilots for reviews and one-to-ones
The constraint, and what I would doB2B + B2C
recruitment platform with AI matching in production
Regulated domain
Recruitment & ATS
Candidate-facing AI has to be defensible, not just accurate
If the same candidate scores differently on a re-run, you cannot defend the decision — and from August 2026 you may have to.
Candidate–job matching and ranking enginesResume parsing and enrichment pipelinesAutomated screening and shortlistingSourcing and outreach agents
The constraint, and what I would do520M
parameters processed every 15 minutes
Telecom & data platforms
Keep the language model out of your hot path
At 520 million records every 15 minutes, per-record inference is off by six orders of magnitude. There are still good places for an agent — just not there.
Anomaly explanation over network performance metricsPipeline and connector configuration generationAlert triage, deduplication and enrichmentRunbook automation with human gates
The constraint, and what I would doEnterprise CLM
contract lifecycle platform in production
Legal & contracts
In contract AI, an unsupported sentence is a liability
Grounding to a specific clause version is not a feature. It is the product.
Clause extraction and classificationContract review and risk flaggingObligation and renewal-date extractionTemplate and clause-library assistants
The constraint, and what I would doWhy only four?
Because these are the domains where I have shipped production systems, and an industry page for a domain I had not worked in would be exactly the generic filler that makes these pages worthless. The reliability work itself transfers to any domain — if you are somewhere else, the solution pages are the better starting point.
Different domain, same problems?
Unvalidated tool arguments, unbounded loops, missing evals and cost with no ceiling look the same everywhere. Tell me what you are building and I will tell you which of these constraints applies to you.