Partnership brief · prepared for Lovable

A warehouse operator built the accuracy layer his industry keeps asking for. On Lovable.

Fenyx is the accuracy operating layer that sits beside your WMS. Living rules. Count autopsy. Ghost hunt. It does not replace SAP. It does not post adjustments.

It was not designed from a market report. It was built from ten years of 4 a.m. cycle counts, missed putaways, and procedures that only existed in one person's head — by the supervisor who lived them.

No signup. No sales call first. Every button in the demo works.

Fenyx in 75 seconds

Westline DC, one count variance, one separate ghost hunt. Captions are on the video.

Deep dive (8 min)

The full story: cost of tribal knowledge, the layer, the method, and the pilot math. AI-narrated.

Shot-by-shot guide

Watch how each screen earns the next one: gap → miss → cause → procedure → hunt → boundary.

  1. 0:00–0:06 — Pulse. Westline at 96.4%; target 99.9%. Caption: “The gap is the product.”
  2. 0:06–0:18 — CC-118. System 48 EA, floor 42 EA. Six pieces Valley Gas cannot receive.
  3. 0:18–0:38 — Rank 1 cause. Retired-home slot drift; confirm by walking both locations.
  4. 0:38–0:52 — Tonight’s procedure. Receiver, putaway, grave lead; each step has a stop condition.
  5. 0:52–1:05 — Separate Ghost Hunt case: system 48 EA, bin 0 EA. Walk A-14-03, then WC-01 and stage.
  6. 1:05–1:15 — Back to Pulse. Historical operator result, then the boundary: Fenyx never posts adjustments.

What is already built

Three modules, all running in the demo today. Not mockups.

Living Rules

Tribal notes become numbered, owned procedures that survive the shift change.

Count Autopsy

A variance gets a ranked cause chain, a procedure step, and a closed loop — not a re-count.

Ghost Hunt

System says it's in the bin. It isn't. Fenyx names the three places it actually is.

Fenyx never writes to the system of record. That single constraint is why an operations manager will actually let it in the building.

Why this is the moment

Mid-market distribution centers are stuck between a spreadsheet and a seven-figure WMS replacement. Analysts have spent this year describing that exact gap — an operating layer that captures floor knowledge without ripping out the system of record. That is the product, and it already runs.

Enterprise vendors will build it for enterprise budgets. The 500-to-5,000-order-a-day DC gets nothing. Fenyx is priced and scoped for that DC: $399 per site per month, a two-week pilot, no integration project.

The ask

Not funding. Reach and reinforcement.

Co-tell the story

A built-on-Lovable case study aimed at operators, not developers. Fenyx is the proof that a warehouse manager with no engineering team can ship a real industrial tool.

Introductions, not leads

Warm paths into mid-market 3PLs and distributors. One pilot DC is enough to turn the story into revenue evidence.

Production support for pilots

Guidance on hardening multi-tenant pilots so the first paying DC never sees a wobble.

What Lovable gets

A named vertical flagship in a category nobody has claimed yet, and a founder who documents the method publicly, in operator language.

I spent a decade fixing accuracy with clipboards and shouting. Fenyx is that fix, made permanent. I built it on Lovable in weeks. Give it a hallway to walk down and it becomes the standard mid-market warehouses have been waiting for.

Matt Lane — Fenyx, Inland Empire

Demo data is fictional. Fenyx is not affiliated with any past employer.