Verso / Platform
The platform

Six products. One record.

Run the operation and command the collection on one connected platform — the market side of the trade and the operational side under it, finally joined. Every product below reads and writes the same four things: Party, Object, Condition, Document.

The problem

Six systems that each hold a piece of the same object.

Nobody in this trade set out to run a disconnected operation. It happened one sensible purchase at a time, and the cost only shows up at the seams — which is where the object actually is.

On separate systemsOn one record
The objectEntered in the CRM, re-entered in the shipping system, re-entered on the condition form, re-entered on the invoice. Four versions, four people, one work.Entered once. Every product reads the same object, and a change to it is a change everywhere at once.
A sale that needs shippingAn e-mail with dimensions pasted into it, and a shipper who re-types them at midnight.A door. The operator sees the object’s facts — never your prices, your collectors or your provenance.
ConditionA PDF in a folder on somebody’s drive, named after the date it was written.A versioned state on the object itself. Append-only, positioned, signed — and the same history the owner and the crew read.
The paperworkDrafted from a previous job’s paperwork, because that is faster than looking it up.Drafted from the record’s own parties, objects and values, reviewed and signed by a person, filed to the object.
Who knows whatEach party knows their slice and assumes about the rest. The gaps are found when something is already late.Each party sees their own scope of one record, by relation. Nobody assumes, because nobody has to.
Product by product

What each one is actually for.

Six products, switched in place rather than six pages you have to hold in your head at once.

The operations command centre

Every desk of a specialist art logistics operation — sales, quotations, dispatch, atelier, freight, warehouse, documents and finance — as one system on one job record.

  • Quotations grouped by customs regime, priced against your own rate book.
  • The dispatch desk the day actually runs on, with the field answered where the day is planned.
  • An atelier that outputs the cut sheet the carpenter cuts, with volumetrics flowing live to the freight line.
  • Freight on real geography, driving the job rather than being reported into it.
The operations command centre
Logistics ERP · Dispatch · ERP-v3.47
The shared record

Four things, one truth.

Every product reads and writes the same four entities — so nothing is ever a second copy, and nothing is re-typed between a sale and a crate.

Party

Everyone in the trade

Collectors, galleries, packers, insurers — one identity across the system, with the basis you hold each contact on.

Object / Work

The thing itself

Identity, value, location and history, captured once. Custody is a state, not membership.

Condition

A versioned state

Held on the object, not in a folder. Append-only: every check kept, every report signed.

Document

Drafted, signed, filed

Quotations, invoices, carnets, condition notes — drafted from the record, signed by a person, filed to the object.

4shared entities
6products, one record
2command centres
0%of any sale
Human-in-Command

It drafts. You sign.

Verso AI works inside every product on the platform — reading the record in front of you, drafting the work, waiting for a person. The dial is yours: Manual, Assisted, Proactive.

app.verso · demo tenant · fictional data
Logistics ERP · the Verso panel — real screen capture
Logistics ERP · the Verso panelReal screen · ERP-v3.47 · captured Sep 2026
How Verso AI works

See both command centres on one record.

Book a demo