Built for the people who move the boxes
Importers moving containers between the US and Latin America run the business on a spreadsheet, a WhatsApp thread and an inbox, so nobody knows what a container really cost until long after it lands. That's why we built Clasto: one record per container, with every document, cost and payment on it. You know where every container and every dollar stands, before the box lands.
The container is the unit of work. Software rarely treats it that way.
An importer's day is organised around boxes in transit. The software they are sold is organised around a chart of accounts.
So the real system ends up scattered. Open shipments live in a spreadsheet that one person maintains. Supplier conversations live in WhatsApp. Bills of lading and packing lists live in an inbox, attached to an email thread nobody else can find. The accounting package sees the shipment weeks after it mattered, when there is nothing left to decide.
None of those tools are wrong on their own. Together they mean the same numbers get typed three times, the landed cost is a guess until the container clears, and the only person who knows where anything stands is the one who built the spreadsheet.
Clasto starts from the container instead. One record per box, with the purchase order, supplier invoice, documents, customs paperwork, landed cost, and payment all attached to it. The record is complete before the box lands, and everyone is looking at the same one.
Six commitments we design against
These are the arguments we have already had internally. Writing them down keeps us from relitigating them badly later.
The container comes first
If a feature cannot attach itself to a shipment record, we question whether it belongs in the product at all.
AI drafts, people approve
Extraction saves you typing, not judgment. Nothing reaches your books until one of your users approves it, and the audit trail says who.
Both languages, equally
English and Spanish are the same product, not a translation layer. Every screen, every document, every email.
One system, not a suite
We would rather ship modules that share one record than a dozen that need an integration team to reconcile.
Priced by containers, not seats
Charging per user punishes you for letting your warehouse and your accountant see the truth. So we do not.
Your data leaves when you do
Full export, any time, in a format you can open without us. Lock-in is not a retention strategy.
What is live, and what is next
An honest state of the product. If a module is not on this list, we are not building it yet.
If you clear containers on the US–LatAm lanes and want to shape what we build next, say so in the demo form.