Products / Clerk
Clerk clerk · the back officeAI agents that orchestrate tasks
An agent that joins the team chat, takes dictation, checks the record and asks before it writes. The back office you did not have to hire.
40 models matched. Two rows match nothing in the catalog:
Sale 5 kg Ceremonial · 1,250,000 ARS. Collection 750,000 ARS to Galicia today. Balance after: 500,000 ARS. Stock after: 41 kg (≈ 38 days).
Two real flows, compressed: the model decides what to do, the code computes and writes, a person approves before anything lands in Ledger. Sample values.
How it plugs into what you have
- Lives in Telegram, WhatsApp, Slack or Claude; no new app to open, nothing to learn beyond asking
- Takes a seat in the org chart: quoting, order entry, documents and PDFs, follow-ups, data entry
- Preview-then-confirm on every write; allowlists, rate limits and a full log of what it did and why
- Plugs into
- Ledger or your existing database, your document templates, calendars and inboxes, and any internal API. One agent covers the functions you would otherwise hire for.
In the field
- Photo Imagen: a desk agent that quotes, creates orders and issues documents
- Kura Matcha: a Telegram assistant the founders dictate sales and payments to
Further reading
Frequently asked
What is a remote MCP server and why would a company want one?
MCP (Model Context Protocol) is an open standard that lets an AI assistant such as Claude call external tools. A remote MCP server exposes a company's own systems (prices, orders, accounts, documents) as typed tools, so leadership can work with them from Claude on the desktop, without a terminal or a custom app.
How long does a first build take?
Typically four to ten weeks after the two-week assessment, with working software in the first week and real data by the second. Arlem prefers a narrow system used every day over a broad one that is not.