Mid-market companies do the same work Amazon does, with a fraction of the tooling. We started Fask to fix that.

I spent over twelve years at Amazon, eventually becoming a Principal Engineer leading payment systems. Those systems sat behind ordering, fulfillment, accounting, compliance, customer support, and seller operations.

The visible order is a small slice of the work. The rest is invoice matching, vendor chase, payment reconciliation, replacements, claims, and ERP updates.

Amazon had long-running services, audit logs, and escalation paths for that work. Mid-market teams usually have inboxes, spreadsheets, and people clicking through portals.

My co-founder George Koshy was on the same Amazon team, then ran payments, fintech, and RevOps engineering at Coinbase.

We kept seeing the same gap: retailers, brands, wholesalers, distributors, commerce operators, and 3PLs were running Amazon-like operations without Amazon-like tooling.

VPs of Operations, Supply Chain, and Finance described the same pattern: thousands of vendor emails, late POs in spreadsheets, retailer deductions, marketplace claims, AP / AR gaps, and ERP records that lagged reality.

RPA broke on template changes. Workflow builders became hard to maintain. Front-office AI stopped at the conversation. ERP copilots summarized one system but missed the email, EDI, portal, carrier, and marketplace signals around it.

Teams wanted agents that could read the item, log into the ERP, process EDI, pull carrier data, follow the SOP, and close the loop.

Fask is autonomous AI agents that execute on the systems your business already runs: NetSuite, SAP, Oracle, Microsoft Dynamics 365, EDI, carrier APIs, retailer portals, marketplace portals, shared inboxes, and spreadsheets.

We focus on the wedges where the pain is sharpest:

Underneath, Myst runs the agent platform and Cali runs the operational communications. Agents read SOPs, score every action with confidence, keep a full audit trail, and route low-confidence cases to humans.

The first goal is simple: take repetitive exception work out of inboxes and spreadsheets, then make every item visible until it closes.

We started with vendor operations because that pain showed up first. The sharper wedges now are retail deductions, vendor order exceptions, distributor order ops, marketplace claims, cross-channel exception desks, and 3PL client exceptions.

If your team is reading vendor emails, chasing late POs, disputing chargebacks, filing marketplace claims, or reconciling exceptions by hand, we should talk.