About

Most shop disasters
were predictable.

The most expensive shop disasters are the ones that never had to happen. A tolerance contradiction missed at quote time turns into a rework loop two months later. A customer who changes specs mid-job for the fifth time, and nobody priced it in. A machine that's been quietly slipping deliveries for a quarter, and nobody connected the dots until the foreman said something at lunch.

The information is already there — in the RFQ, in the shift notes, in the QuickBooks export, in last month's scrap log. It just isn't reachable in time to matter. Opsentinel is the system that reads everything you already have, finds the patterns that cost you money, and says them out loud before they hit you again.

What we've built

10

Risk categories scanned

Per RFQ, deterministically.

30s

Typical analysis time

Upload → a specific list of findings.

100%

Re-run reproducibility

Same document → same report.

262

Backend tests passing

Every push, before deploy.

How we built it

Three principles, every shipped feature.

Manufacturing-specific, not a ChatGPT wrapper.

Domain prompts, citation enforcement, severity rules tuned for tolerances and datums and shop-floor realities — not generic 'AI for X'.

Deterministic by design.

Temperature-0 LLM calls, canonicalization of findings, two-pass verification on critical issues. Re-running an RFQ never produces a different answer — auditable, defendable, debuggable.

Works with what you already have.

Drag-and-drop PDFs, telemetry CSVs, foreman shift notes, QuickBooks exports. No integration tickets. Older shops without sensors get the same value as CNC operations with full telemetry.

Who's building this

Founder

Matt Kidd

Email me about a pilot.

hello@opsentinel.io

Opsentinel is a small, focused team building one thing: a manufacturing-specific operational risk system that reads what your shop already produces and surfaces what it's about to cost you.

We ship in days, not quarters. When something on the product is wrong, we fix it that week. When you ask for a feature, we tell you honestly whether it fits the roadmap or not. When we don't know something, we say so in the procurement FAQ instead of burying it.

We're looking for a small number of pilot customers who want to be early — and who want to influence what the product becomes. If that's you, get in touch.

Want to see it on your own data?

Send a backlog of past RFQs or a month of operational data. We'll show you what Opsentinel would have caught. Honest answer in days, not quarters.