Built for food processing plants
Wren turns your plant's own manuals into machine-specific answers. Scan the QR tag on the machine, photograph the fault, and get the documented fix — in seconds, not shift handovers. Because in food processing, a stopped line puts product at risk, not just output.
No card required · Early access opens with 25 plants
Machine identified · 1.4s
Line 4 — Vacuum Packager
Zone: raw poultry pack-off · Product at risk: 1,850 lb
Photo diagnosis · sealing-jaw fault
Interface preview · sample data
Illustrative design targets for the Wren pilot programme — not audited customer results.
The problem
Other plants lose throughput when a machine stops. A food plant loses the product too. Perishable inventory sitting in a stalled line drifts out of temperature spec, out of hold time, out of compliance — and at some point it stops being inventory and becomes a write-off. The information needed to restart the line almost always exists. It's just not where the technician is standing.
Spoilage-driven downtime is the core pain Wren is built for.
A stopped packager holds raw poultry above temperature. A stalled chiller pushes a batch out of its cooling curve. A jammed conveyor backs product up in an oven. The line stops and the shelf life starts burning down with it.
The OEM manual describes a base model. Your grinder has a retrofit control head, your sealer has a rebuilt jaw assembly, and three sanitation-driven changes nobody wrote down — except in a folder on a shared drive.
Your most experienced technicians carry the real troubleshooting tree in their heads. When they retire or move plants, the fix time for every recurring fault quietly doubles — and so does the product you write off.
How it works
Wren is designed for the first ten minutes of a stoppage — the window where a food plant either recovers the shift or starts writing off product.
Print a washdown-rated Wren tag for every asset — conveyor, grinder/mixer, oven, fryer, packager/sealer, chiller, freezer, pump — and fix it to the operator panel. The tag links to that exact asset: model, serial, control revision, rebuild history and the manuals that actually apply to it.
Setup: ~4 minutes per machine
A technician scans the tag with a phone and photographs what they are looking at — a torn seal on a packager, a mistracking belt on a transfer conveyor, frost on a spiral chiller coil, an alarm on the oven controller. No fault codes to type, no login on a shared terminal.
Works with wet gloves on, works offline
Wren returns ranked probable causes, each one linked to the exact page of your manual or SOP that covers it — then records what actually worked so the next technician starts where this one finished.
Every answer cites your own documentation
At the panel · not at a deskDesigned for the floor
Technicians don't stop mid-fault to open a laptop. Wren is one scan deep: large touch targets, high-contrast type readable under plant lighting, and a cached copy of every manual for the machines on your floor so a dead spot in the freezer or the pack-off bay doesn't block a repair.
What's inside
Upload OEM manuals, retrofit addenda, sanitation SSOPs and your own work instructions. Wren indexes them per machine and answers only from documents your plant owns, with the page reference attached.
One washdown-rated tag turns any machine into a scannable asset: model, capacity, control revision, installed options and the fault history logged against it.
Photograph the defect or the alarm screen. Wren matches what it sees against your documented fault library and ranks the probable causes rather than returning a wall of search results.
Failed vacuum seals, mistracking belts, grinder plate wear, oven zone temperature deviations, chiller coil frost-up, pump cavitation — modelled as real troubleshooting trees for food plant equipment, not generic asset templates.
Manuals and fault trees for the machines on your floor are cached on the device. Freezers, pack-off bays and metal-clad process rooms stay covered; scans sync when the phone reconnects.
Every resolved fault is captured as a short structured note against the machine, so the incoming shift sees what was tried, what worked, and what to watch on the next production run.
One vertical, on purpose
A platform that covers every asset class covers none of them deeply. Wren goes the other way: one equipment class — food processing — modelled properly across every subsystem in a meat, poultry or packaged-food plant, so the guidance a technician gets is specific enough to act on without interpretation.
Subsystem depth is prioritised by our design partners — not by a roadmap committee.
Where Wren fits
The tools your plant already runs are built for planning, compliance and fleet-wide visibility. None of them are built to stand next to a stalled packaging line at 2am, with product warming on the belt, and tell a technician what to check first. That gap is the whole product.
e.g. Augmentir
Digitising work instructions, skills and training across every asset and role in the plant.
Broad by design · plant-wide rollout
e.g. UpKeep
The system of record for work orders, preventive maintenance schedules, parts and asset cost.
Maintenance planning · work-order centred
e.g. Fiix, part of Rockwell Automation
Asset reliability, integrations and analytics across many plants and large mixed fleets.
Fleet scale · reliability programmes
Food processing, only
Category descriptions are our own summary of how these products are positioned. Wren is built to sit alongside them — it is not a CMMS and does not replace your system of record.
Voices from the floor
Placeholder quotes — Wren is pre-launch. These are illustrative examples with fictional names and plants, not real customers.
Half my job used to be finding out which revision of the machine I was standing in front of. The tag answers that before I put my gloves back on.
We photographed a bad seal on Line 4, got three ranked causes and the exact page of our own packager manual. The line was running again before the pallet in front of it went out of temp.
The value isn't the search. It's that a second-year tech now starts a diagnosis in the same place my best 20-year tech would.
Pricing
One seat per technician who uses Wren on the floor. Machines, tags and scans are never metered — a stopped line and the product sitting on it are the only meters that matter.
1 – 9 seats
$89
per technician / month
For a single plant getting its first machines tagged and its manuals in one place.
10 – 49 seats · volume discount applied
$75
per technician / month
For a full maintenance crew keeping processing and packaging lines running around the clock.
50+ seats
Custom
volume pricing across sites
For multi-plant groups standardising troubleshooting across every food processing facility.
The arithmetic
At an illustrative $200 per minute of stopped line — lost throughput plus perishable product at risk — one 30-minute stoppage avoided on a packaging line covers 67 technician seats for a month.
Worked example: a vacuum packager on a raw poultry pack-off line goes down with a sealing-jaw fault. 30 minutes × $200/min = $6,000 in lost output and product held above temperature. At $89 per seat, that single avoided stoppage pays for 67 seats for the month.
Example calculation only, using a placeholder downtime-plus-spoilage rate — substitute your own figure. Billed monthly per active seat. Annual billing available. No metering on machines, tags or scans.
Questions
Still need something specific about your lines, your controls or your documentation? Add it to the note field when you join the waitlist and we'll cover it in the first call.
Food processing equipment across meat, poultry and packaged-food plants: mixers and grinders, slicers and formers, spiral ovens and fryers, vacuum packagers and sealers, chillers and blast freezers, conveyance and metal detection, and the pumps, CIP skids and utilities that feed them. Wren is deliberately deep rather than wide — food processing is the one equipment class we model properly, and subsystem depth is prioritised with our design partners.
Early access
We're onboarding 25 food processing plants as design partners. You bring the lines and the manuals; we bring the tags, the fault library and a technician-first app your crew will actually open.