Proof

One real build. And an honest account of everything else.

Charidan is new. We'd rather show you one system in production and be straight about the rest than pad this page with logos. Here's what exists, what it does, and what we'd build for a company shaped like yours.

Case Study 01 · In Production

A pen and ink importer, Los Angeles

REAL CLIENT · ANONYMIZED AT THEIR REQUEST

From five disconnected systems to one live hub

~2,900 SKUS · 5 SALES CHANNELS · IMPORTED PRODUCT · OWNER-OPERATED

A wholesale importer selling through Amazon, their own site, US dealers, international distributors, and trade shows. Inventory lived in their ERP. Distributor revenue lived in QuickBooks. Freight status lived in an inbox. Nobody could see the whole picture without a person spending most of a morning building it.

What we found

  • Purchasing decisions made from a report that was three days stale by the time it was read
  • Units already on the water not subtracted from reorder quantities — so the same SKU got ordered twice
  • International distributor revenue invisible in the ERP entirely
  • Container status reconstructed by searching email
  • 51 exclusive and limited-edition projects tracked in one spreadsheet, on one laptop, maintained by one person

What we built

  • Six connectors into one canonical schema — ERP, Amazon SP-API, Shopify, QuickBooks, Sheets, and a manual freight connector
  • Purchasing engine that nets inbound units and applies per-vendor lead times
  • Role-based seats: owner, purchasing, accounting, and custom projects
  • A two-stage projects model — resin PO to production PO to promised ship month — that the ERP could not represent
  • A WhatsApp agent that turns a chat message into a finished contract, in Hebrew
$250K+
Committed project value surfaced that had never been consolidated anywhere
6
Live data sources in one view, refreshed continuously
1 file
Client-specific configuration — the engines are shared, so the next build is faster
CLIENT NAME WITHHELD BY AGREEMENT. WE CAN WALK THROUGH THE LIVE SYSTEM ON A SCREEN SHARE.
Illustrative Scenarios

What we'd build for a company like yours

These are not clients. They're worked examples — the shape of the problem and the shape of the build, for the three company profiles we see most. We've put them here instead of inventing case studies, because you'd find out eventually and it would cost us more than it earned.

SCENARIO · NOT A CLIENT

Housewares importer, 4,000 SKUs

Sells on Amazon and to regional chains. Purchasing runs off a monthly export; by the time it's built, the fast movers are already short and the slow movers already reordered.

BUILD: Reorder Brain + Container Tracker
TIMELINE: 4 weeks · $5,500–$9,500
SCENARIO · NOT A CLIENT

Apparel wholesaler, 60 dealers

Orders arrive as emails, PDFs and photos of handwritten sheets. Two people spend most of Monday and Tuesday keying them in, and the errors surface at invoicing.

BUILD: Dealer Order Intake + Invoice Chaser
TIMELINE: 3 weeks · $4,000–$6,500
SCENARIO · NOT A CLIENT

Specialty food distributor

Landed cost hasn't been recomputed since freight moved. Several SKUs are being sold below true cost and nobody will notice until the year-end close.

BUILD: Margin Watchdog + accounting seat
TIMELINE: 3 weeks · $4,500–$7,000
The Guarantee

If the audit is worthless, we'll say so

The ops audit is free and it isn't a sales call in disguise. If we can't find at least three specific, quantified places your operation is losing time or money, we tell you that and there's no pitch. You keep the written plan either way — including the parts you could implement yourself without us.

Founding Clients

We're trading discount for a story

We're taking a small number of founding clients at 20–30% off, in exchange for a written case study once the system is running and one introduction to someone else who needs it. That's the whole arrangement, and it expires once this page has enough on it.

Pick a time hello@charidan.com · Los Angeles / Tel Aviv