R.T. Cohen — Post-Call Brief

R.T. Cohen · ר.ט. כהן — Post-Call Brief

Discovery call with Ronen (owner) · 61-min recording · gardening / turf / ag machinery — import, service & parts

↻ Supersedes the 29 Jun pre-call brief — this reflects what Ronen actually said, not desk research.

1 The business, in his words

~10,000machines serviced

~½ millionpart relationships (1000s/machine)

1,000scustomers

~21 yrsRonen has built it

Imports & services Toro, MultiOne, Weidemann, Peruzzo, Euro-System + more (full list pending).
Runs almost entirely on Hashavshevet (חשבשבת) — their ERP holds inventory, parts, customers, work-cards & invoicing — plus a lot of expert human memory.

2 What's breaking — his own ranking

The warehouse / parts identification — "hurts the most." Matching a machine (by serial) to the exact right part across supplier catalogs. Needs expert eyes; slow, Sisyphean.

Fault codes + supplier claims — machine throws an error code, customer sends it, staff must decode it & know the fix; plus opening warranty/claim cases in each supplier's portal. "I need fast answers and don't have them."

Work scheduling & dispatch — a broken 8-yr-old tool (built by Hana) + Yuval assigning drivers to jobs entirely by hand/memory.

3 How it works today

Work-card opens in Hashavshevet → a person matches the machine's serial to supplier catalog drawings & part numbers → finds it in the warehouse by location code (often missing) → prices it by hand (USD × 10 = ₪) → orders. Dispatch lives in Yuval's head. Machine & warehouse don't talk to the ERP — all re-keyed manually.

4 What Ronen wants built

Customer → their machines → exact parts, auto-pulled — one shared "language" for customer, tech & warehouse; no re-searching.
Parts-ID assistant — index supplier catalogs; identify the part, show its location & price.
Fault-code & claims automation — decode codes, pre-fill supplier claim requests to edit & send.
Dispatch optimizer for Yuval (drivers, zones, rebalancing).
Later: a customer portal for service-status transparency.

5 What we owe before scoping

Hashavshevet API — confirm read/write integration (talk to their integrator).
Supplier data — test extracting Toro/Weidemann catalogs (open sites) & whether others grant API access.
Hana's contact (old scheduling tool) · full supplier list · on-site warehouse visit to see the real flow.

★ Recommended next step

Start small & contained — one slice that proves value fast (the parts-ID / warehouse lookup is his sharpest pain), then phase into fault-codes, dispatch & the customer portal. We have a direct precedent: the cellular-retail client where we pull competitor data, translate it, and write straight back into their Hashavshevet — turning a 3–4 min task done 200×/day into 3 clicks.