Plain-English answers over live warehouse data
Ask in Claude or ChatGPT and get answers computed from your live WMS data — one connector works with both assistants. No query language, no report builder.
AI-powered forecasting, replenishment and inventory analytics on top of the WMS you already run.
Now piloting with UK 3PLs and brands. Pilot slots are limited.
Illustrative demo with sample data.
The problem
Export the stock report. Export the sales report. Paste both into the spreadsheet with the fragile pivot and rebuild the same analysis you built last Monday. By the time the numbers are ready, they're already a week old — and half the morning is gone.
A client emails at 9:15. The honest answer lives across four screens that were never built for the question, so it takes forty minutes you don't have. The reply goes out after lunch. The client remembers the wait, not the answer.
It was visible three weeks ago — in the run rate, the supplier lead time, the open orders. Nobody had time to line those numbers up. You paid for it in emergency freight, a bare pick face, and an awkward phone call.
What it does
Everything below is live in the product now. Future work is on the roadmap, labelled as such.
Ask in Claude or ChatGPT and get answers computed from your live WMS data — one connector works with both assistants. No query language, no report builder.
Per-SKU demand forecasting that reads each product's pattern — steady, erratic or intermittent — chooses the right statistical method for it, and reports its own accuracy.
Reorder points, safety stock and suggested order quantities calculated from forecast demand and lead times — not last year's gut feel.
Stockout risk and days-of-cover per SKU, ABC/XYZ classification, and inventory valuation — the analyses you'd build in a spreadsheet, already done.
“Turn that into a PDF for the client.” Done, in the same conversation. Reports leave the warehouse looking like you spent an hour on them.
Data-readiness checks run when you connect. If your history can't support a feature yet, it says so — instead of showing you confident wrong numbers. We think that's the most important feature on this page.
A steady seller, a seasonal line and a slow mover need different maths. The engine reads the pattern and picks the method — watch it work on three sample products.
| Week | Actual demand | Fitted forecast |
|---|---|---|
| 1 | 103 | 118 |
| 2 | 121 | 119 |
| 3 | 112 | 119 |
| 4 | 118 | 120 |
| 5 | 125 | 120 |
| 6 | 135 | 121 |
| 7 | 125 | 122 |
| 8 | 129 | 122 |
| 9 | 109 | 123 |
| 10 | 115 | 123 |
| 11 | 132 | 124 |
| 12 | 126 | 125 |
| 13 | 124 | 125 |
| 14 | 111 | 126 |
| 15 | 137 | 126 |
| 16 | 127 | 127 |
| 17 | 137 | 128 |
| 18 | 137 | 128 |
| 19 | 129 | 129 |
| 20 | 132 | 129 |
| 21 | 129 | 130 |
| 22 | 142 | 131 |
| 23 | 140 | 131 |
| 24 | 130 | 132 |
| 25 | 143 | 132 |
| 26 | 130 | 133 |
| 27 | — | 134 |
| 28 | — | 134 |
| 29 | — | 135 |
| 30 | — | 135 |
| 31 | — | 136 |
| 32 | — | 137 |
For 3PLs
For brands & retailers
How it works
Link your WMS account. Read-only, authorised by you, revocable any time.
Ask in Claude, ChatGPT — or the dashboard, when it ships. Plain English in, real numbers out.
Get ranked, explained recommendations: what to reorder, what's at risk, what can wait.
Security
Connecting your WMS means trusting us with a key to your operation. We designed for that from the first commit — these aren't policies we wrote later, they're how the system is built. We don't claim certifications we don't hold; everything below is true of the build today.
Your WMS API keys are stored with per-credential envelope encryption — each secret wrapped in its own key.
Every customer's data is separated at the database level, and that isolation is covered by automated tests on every release.
Your team signs in through enterprise-grade authentication, SSO-ready from day one.
We never write to your WMS. Access is read-only, granted by you, and you can revoke it at any time.
Answers are built from aggregates first, so the assistant works with summaries rather than trawling raw records by default.
Roadmap
None of this is shipped yet — that's why it's here and not above. Waiting-list members shape the order we build it in.
A dashboard for teams that don't live in chat, with branded client reports on a schedule.
Your brands check their own stock under your logo, with per-brand access controls.
“What needs attention this week” lands in your inbox before you ask.
Know which accounts make you money — and which quietly don't.
Price new 3PL business from real cost data instead of a stale spreadsheet.
The engine is platform-agnostic by design. Linnworks is next; others follow demand.
I run 3PL systems for a living, and I got tired of watching smart operators spend Monday mornings rebuilding spreadsheets to answer questions their WMS already knew the answer to. InvictaVision is the tool I wished existed: connect the warehouse, ask the question, get the number. It's being piloted with real warehouses now — if that Monday ritual sounds familiar, I'd like to hear from you.
— Founder, InvictaVision
No spam, no drip campaign. You'll get one email when your slot opens.
Mintsoft is live today. Linnworks is in development. The engine is built platform-agnostic, so further integrations follow demand — tell us yours on the waiting list form.
No. Access is strictly read-only. We compute forecasts and analytics from your data; we never write anything back, and you can revoke access at any time.
Today, yes — the assistant experience runs inside Claude or ChatGPT, which needs one of their paid plans. The web dashboard on the roadmap removes that requirement.
Encrypted at rest with per-credential envelope encryption — each credential is wrapped with its own key. See the security section above; we only claim what's actually built.
Pilot pricing is agreed individually with each pilot partner. Public pricing will be published at launch.
That's the white-label client portal on the roadmap: your brands sign in under your logo and see only their own data. Today, you answer for them — in seconds instead of an afternoon.