01the layer
Wingman OS
One operational surface over your stack. Tasks, agents, alerts and reporting in a single place your team actually supervises.
- Supervision
- human-in-loop
- Surface
- web · telegram
WSOL // Wingman Systems · Operational AI Layer
Est. 2010 · IL
Connected systems. Operational AI.
Intent becomes finished work.
We connect your systems, build your AI agents and automate the work between them. Your team stays in control. Your business keeps moving.
- Pilot first
- Human approval
- Built on your stack
- 01CaptureMail · PDF · WhatsApp
- 02UnderstandRules · context · approval
- 03CompleteERP · CRM · your team
01. What we do
The right systems. Working together.
From a single automation to a connected operational system. Built around the way your team works.
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.
- Inputs
- mail · pdf · chat
- Output
- system 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.
- Direction
- two-way
- Model
- no 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.
- Access
- role-scoped
- Data
- live from source
02. Inside Wingman
See what connected work looks like.
Choose a familiar process. Follow the information from the first request to the action in your system.
An email becomes an order.
Capture
A supplier sends an order by email or PDF.
Check & decide
Match items and quantities. Flag missing details for your team.
Execute & record
Write the approved order into the ERP and send confirmation.
Your team approves exceptions before any write-back.
03. The wiring
Your systems, actually connected.
Start with the tools you already use. We check the available connections and permissions, then define where every piece of information belongs.
01two-wayPriority ERP
- Surface
- REST / API
- Typical use
- orders · stock · docs
02two-wayHashavshevet
- Surface
- API / export
- Typical use
- invoicing · reconciliation
03two-wayRivhit
- Surface
- API
- Typical use
- invoicing · receipts
04two-wayCRM
- Surface
- REST / webhook
- Typical use
- leads · status · follow-up
05two-wayWhatsApp Business
- Surface
- Cloud API
- Typical use
- intake · updates · approvals
06inboundEmail / IMAP
- Surface
- Mailbox
- Typical use
- orders · supplier replies
07two-wayTelegram
- Surface
- Bot API
- Typical use
- field reporting · alerts
08inboundSheets / CSV
- Surface
- File · poll
- Typical use
- 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.
Map one process
Bring us a single broken workflow. We trace it end-to-end and find where the hours leak.
Ship a pilot
In days, not quarters. A working automation on your real data, in your real stack.
Measure, then scale
Keep what measurably works, kill what doesn't, then widen it across the team.
Hand over with confidence
If it needs babysitting, it isn't done. You own a system that runs on its own.
06. Why WSOL
Proof over promises.
Pilots, not promises
We prove value on your data before you commit. The pilot is the pitch.
Humans set direction
Machines carry the load; the control room always has a person in it.
Built on your stack
Your tools, your data, your ownership. No rip-and-replace, no lock-in.
Built for everyday work
Clear permissions, documentation and a system your team can supervise.
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
08. Selected work
Systems that run real operations.
Selected projects across industry, services and digital products. Different needs, systems built to fit.
All work →Internal portfolio draft — new material is pending publication approval.
01 / On the factory floor
Pinhas Hisherik
From production scan to regional delivery.
An order and delivery tracking system connecting production-completion scans to order information in Hashavshevet.
Scan
The team scans an order when production is complete.
Retrieve
The system pulls the order information from Hashavshevet.
Route
Deliveries are automatically grouped by destination region.
GVK
A Hebrew–English website with separate journeys for commercial enquiries and service requests.
Gianetti Custom Yachts
Development and maintenance of a yacht website with project galleries, specifications and an online brochure.
Orevi Aluminum Industries
A WordPress website for an aluminium business, bringing together services, projects and professional content.
Hinneni
Website design and development connecting Hebrew navigation, enquiry journeys and the PPI questionnaire entry point.
Start here
Bring us one broken process.
Tell us what repeats, what slows you down and what you want to improve. We’ll explore a practical first step together.