Squint is a procedure system: an operator points a phone at a machine and the guidance for that job appears, with the record captured as the work is performed. Spot AI is not an authoring tool and does not replace that. What moves is the other half, the continuous record of what the line actually did, and here is how to move it.
One platform captures the record inside a procedure the operator opened, the other reads it off the cameras already over the line. Both rows describe what each vendor publishes.
Four moments when operations teams running a procedure tool start this conversation. If none of them are true, staying put is a reasonable answer.
Squint captures tasks, checklists and quizzes with photos, inputs, timestamps and results as the work is performed. That is a genuine record of a guided job. It is silent about the shifts, jobs and areas where nobody opened a procedure, which is a coverage question rather than a comment about anyone on the floor. Ask what share of your actual output runs inside a procedure today, then decide whether that is the whole picture.
Why the changeover on line three runs 20 minutes long, where the dwell goes at the dock, which shift the scrap concentrates in. Squint's Analytics tracks engagement and flags workflow gaps inside its own workflows. Continuous observation of a line, a cell or a dock is not publicly specified, so those questions need something watching the process rather than the app.
A procedure tool is not a detection platform and does not claim to be. When EHS asks about blocked exits and near misses, or security asks who was at the dock door at 02:00, the plant reaches for another vendor. The cameras that would answer both are usually already installed and usually unread, which makes this the cheapest place to consolidate.
Procedures here, safety there, security somewhere else, production intelligence on the line. Every one of them has a contract, an integration and an owner. Consolidation is not automatically right, but it is worth pricing honestly: quote what one platform covers against the four, and be explicit about the jobs it genuinely does not do, procedure authoring among them.
The structural differences that decide whether a switch is worth starting.
Swipe the table sideways to see every column.
Squint data comes from Squint's own public platform and pricing pages, read August 2026. Where Squint publishes nothing, this table says so rather than guessing.
A rollout that keeps coverage live throughout. Most sites go live inside six weeks.
Separate the two halves before anything else, because only one of them moves. On one side the authored library: how many procedures exist, who maintains them, which ERP, MES or CMMS integrations they feed. On the other side the observation question: which areas matter, what share of the work there runs inside a procedure today and which cameras already cover that ground without anything reading them. That second list is the case for the whole exercise.
Run it additively for a fortnight: Squint keeps guiding the work while Spot AI reads the cameras over one line or one cell. Then compare the two records against each other on the same shifts. That comparison is the entire decision, and it is the only version of it that is not a debate about datasheets, because both records describe the same fortnight on the same floor.
Move area by area, and only the observation half. Squint keeps authoring and serving procedures at the machine wherever that is what the plant needs, while adherence evidence, shift recaps and scorecards come off the cameras instead. If the intent is to consolidate vendors entirely, get the procedure export in writing during assess: Squint does not publish export behavior, and a document library is the hardest artifact to reconstruct after a contract ends.
Once the line is covered, the work moves to what a procedure tool was never pointed at. Put safety agents on the aisles and the dock, bring the yard and the perimeter into scope, add scorecards and shift recaps across sites, then build an Iris detection for something specific to your process. This is where one platform stops being a consolidation exercise and starts answering questions nobody could ask before.
The six that come up in every one of these conversations.
That matters less here than on most switches, because the pilot is additive: Squint keeps guiding work while Spot AI reads cameras it never used. Run the overlap inside the contract, use it to decide area by area and time any commercial change to the renewal date rather than to the pilot.
Not as part of this plan, and it is worth being blunt about why: Spot AI tracks SOP adherence, scorecards and shift recaps, and it does not author or serve step-by-step procedure documents at the machine. If authoring and guided work is the reason you bought Squint, that job does not move. If you do intend to consolidate fully, get the export terms in writing while the contract is live.
No, because nothing is switched off to run the comparison. Squint keeps capturing its record throughout the pilot and through cutover, and an area only changes once its replacement has run a full week on the same shifts. If an area fails that test, it stays where it is while the others proceed.
Where the confirmation comes from. In Squint the record is captured inside a procedure as the work is performed, which is a clean record of guided jobs. On cameras the record does not depend on anything being opened, so it covers the shifts and areas where no procedure was running. Neither is dishonest. They answer different questions and the pilot shows you which one your plant is short of.
Then leave that alone. The workflow at the machine is Squint's strongest part and this plan does not touch it. What changes is upstream of the operator: supervisors and CI leads stop assembling a picture of the shift from app engagement and start reading it off the line directly. Budget the full fortnight of overlap so both are compared on real production.
It depends what you consolidate, and anyone answering without that list is guessing. Squint publishes one Enterprise plan, and Spot AI charges a per-camera subscription covering the software and the IVR. Quote both against the identical area list, be explicit that procedure authoring stays where it is and count the vendors still needed afterwards on each side.
Bring a camera list and we will tell you what works as it is.
Customer-reported outcomes from named Spot AI customers.
Staccato went from first conversation to full deployment across an 800-acre campus in seven weeks, on the camera infrastructure it already had.
Bridge33 Capital standardized video across 25 plus properties, each acquisition arriving with a different camera system, and cut footage search from hours to minutes.
The YMCA of Greater Richmond deployed 17 locations in two weeks and standardized retention across the estate.
"Within four minutes of the alarm going off, Spot AI gave us video footage of the incident on the responding officers' phones. We had five recoveries within the hour."
No, and the plan is written on that basis. Spot AI covers SOP adherence, scorecards and shift recaps from the cameras on the floor. It does not author procedures or serve step-by-step guidance at the machine, which is what Squint's Author and Workflows modules do. Most plants keep the library and move the observation half.
No. Spot AI is camera agnostic: any IP camera speaking ONVIF or RTSP works as it is, whatever the manufacturer, and legacy analog runs come in through the Intelligent Video Recorder. In plants running a procedure tool, those cameras are usually already installed and usually unread, which is the whole argument for starting here.
Most plants are live inside six weeks: a week to inventory both halves, a fortnight of additive pilot on one line or cell, then an area-by-area decision. Because nothing is switched off during the pilot, the timeline depends on how quickly the plant agrees the area list rather than on any technical cutover.
Yes, and the plan depends on it. The pilot deliberately runs Squint and Spot AI over the same fortnight so the procedure record and the camera record can be compared on identical shifts. Plenty of plants stay that way permanently, keeping procedures where they are and putting observation on the cameras.
Who observes the work. In Squint the operator's device captures the record inside a procedure they opened. In Spot AI the cameras already installed carry it continuously, with 15+ pre-trained agents spanning operations, safety and security, plus AI Talk Down, strobes and horns through standard speakers where a response is needed.