01the layer
Wingman OS One operational surface over your stack — tasks, agents, alerts and reporting in a single place your team actually supervises.
Supervisionhuman-in-loop
Surfaceweb · telegram
WSOL // Wingman Systems · Operational AI Layer
Est. 2010 · IL · --:--:-- · EN
Operational AI, in production
Intent becomes finished work.
WSOL is the operational AI layer that connects the systems a plant already runs — ERP, CRM, email, WhatsApp, the shop floor — and quietly clears the repetitive work between them, so your people spend their hours on the work that actually moves production.
FIG.00 — WING / 3DLive
Built for operations that cannot stopHuman approvalEvidence before doneScoped pilotsPrivate when required
01 — What we do
Four layers. One operating system.
We don't sell a tool your team has to learn. We install a layer over the systems you already run — and it does the work.
02the agents
AI Automation Order intake from email, PDF and WhatsApp. Supplier replies read and matched. Shift reports written. Not a chatbot — a coworker that picks up the task and finishes it.
Inputsmail · pdf · chat
Outputsystem write-back
03the wiring
Integrations ERP, CRM, WhatsApp, sheets and portals finally talking to each other. No rip-and-replace, no lock-in, no second source of truth.
Directiontwo-way
Modelno rip-and-replace
04the control room
Web Systems Custom portals and dashboards wired into live processes — the control room where your people supervise the machine.
Accessrole-scoped
Datalive from source
02 — Inside Wingman
From raw signal to finished work.
One operational loop: capture every input, decide with context, then write finished work back into the systems your team already uses.
STAGE.01Data intake
Every signal arrives ready for work.
Orders, specs, supplier mail, forms and floor events are captured, validated and normalised into one live operational stream.
MULTISource intake
CLEANValidated stream
STAGE.02AI core
Context drives the next decision.
Wingman classifies, enriches and routes each item against your rules — with every decision logged for review.
AIRules + context
HUMANWhen required
STAGE.03System execution
The work lands finished, not pending.
Approved actions write back to ERP, CRM and the tools already in place — synchronised, accountable and complete.
SYNCSystem write-back
PROOFBefore complete
03 — The wiring
Your systems, actually connected.
Integration is where operational AI succeeds or fails. These are the surfaces we work through most often — always two-way where the system allows it, always with one source of truth.
| System | Surface | Direction | Typical use |
|---|---|---|---|
| Priority ERP | REST / API | two-way | orders · stock · docs |
| Hashavshevet | API / export | two-way | invoicing · reconciliation |
| Rivhit | API | two-way | invoicing · receipts |
| CRM | REST / webhook | two-way | leads · status · follow-up |
| WhatsApp Business | Cloud API | two-way | intake · updates · approvals |
| Email / IMAP | Mailbox | inbound | orders · supplier replies |
| Telegram | Bot API | two-way | field reporting · alerts |
| Sheets / CSV | File · poll | inbound | legacy lists · handovers |
Anything with an API, a mailbox or a file drop can be wired in. If it has none of those, we say so before you commit.
04 — The shape of the change
One order, both ways.
A supplier order arriving by email, traced end to end. The counts below describe these two diagrams, not a client result — what changes for you depends on your process, and we measure it in the pilot.
PATH.CURRENT07 steps · 05 manual handoffs
- 01Order lands in a shared mailbox
- 02Someone notices and opens itmanual handoff
- 03Lines are read off the PDFmanual handoff
- 04Re-keyed into the ERPmanual handoff
- 05Stock checked in another screenmanual handoff
- 06Confirmation typed back by handmanual handoff
- 07Nothing recorded but the email
PATH.INSTRUMENTED03 steps · 01 approval gate
- 01Order captured and parsed on arrival
- 02Matched against stock and priced; exceptions raised for a personhuman approval
- 03Written to the ERP, confirmation sent, every action logged
05 — How it works
Start with one working pilot.
D0
01
Map one process
Bring us a single broken workflow. We trace it end-to-end and find where the hours leak.
D3
02
Ship a pilot
In days, not quarters. A working automation on your real data, in your real stack.
D10
03
Measure, then scale
Keep what measurably works, kill what doesn't, then widen it across the team.
D30
04
Hand over autonomous
If it needs babysitting, it isn't done. You own a system that runs on its own.
06 — Why WSOL
Proof over promises.
01
Pilots, not promises
We prove value on your data before you commit. The pilot is the pitch.
02
Humans set direction
Machines carry the load; the control room always has a person in it.
03
Built on your stack
Your tools, your data, your ownership. No rip-and-replace, no lock-in.
04
Done means autonomous
We're finished when the system runs without us — and keeps running.
HumanApproval stays in the loop
EvidenceRequired before work is done
ScopedPilots around a real workflow
PrivateLocal or on-prem when required
07 — The company
Systems people, since 2010.
We spent fifteen years wiring CRMs, ERPs and portals for operations that can't afford downtime — including manufacturers whose systems run the floor. Then AI made the last mile possible: not just connecting systems, but finishing the work between them.
WSOL is that layer, built by the people who ran the wiring. Small senior team, no juniors on your account, and nothing ships that we wouldn't run ourselves.
Founded
2010
Base
Israel
Focus
Industry
Model
Pilot-first
FIG.06 — FIELD / OPSLive
08 — Selected work
Systems that run real operations.
A reviewed selection. Each entry is presented at the level its client has agreed to publish.
All work →Start here
Bring us one broken process.
One workflow that eats your team's week. We'll come back with a pilot — on your stack, on your data, in days.