When we started building Tarshix, we made a deliberate choice: start with maritime. Not because maritime is the largest market in Nigerian trade, but because it is the most structured, the most document-heavy, and the most underserved by existing software.

Twelve months into the build, we have learned something that validates the strategy: approximately 70% of what we have built for maritime works for every other trade vertical.

The specific templates are different. A PDA is not a purchase order. A charter party is not a lifting agreement. But the underlying infrastructure is identical.

Transaction management. In maritime, a transaction is a port call — a vessel arrives, services are rendered, invoices are generated, payments are collected. In energy, a transaction is a lifting — crude is nominated, documentation is prepared, invoices are generated, payments are collected. In agriculture, a transaction is a shipment — produce is contracted, shipped, documented, invoiced, and paid for. The structure is the same: a commercial event that generates documents, invoices, and payments across multiple parties.

Multi-party workflows. Maritime involves ship owners, charterers, port agents, sub-agents, and various service providers. Energy involves operators, service companies, joint venture partners, and off-takers. Agriculture involves farmers or cooperatives, buyers, logistics providers, and export agents. In every case, multiple parties need access to the same transaction data, with different permission levels and different approval responsibilities.

Payment reconciliation. Every trade vertical has the same problem: a counterparty makes a bank transfer, and someone on the receiving end needs to match that transfer to the correct invoice. This is manual everywhere. The solution — a unique virtual bank account per invoice — works identically regardless of industry.

Audit trail requirements. Maritime has IMO regulations. Energy has DPR compliance. Agriculture has export documentation requirements. The specifics differ, but the need for an immutable record of who did what, when, is universal.

Contract-to-payment lifecycle. In every trade vertical, there is a lifecycle that begins with an agreement (contract, charter party, purchase order) and ends with a payment. Between those two points lie documents, approvals, invoices, and reconciliation. This lifecycle is what Tarshix manages.

The expansion path is not about rebuilding the platform for each industry. It is about adding industry-specific templates (invoice types, document types, charge categories) on top of shared infrastructure. The transaction engine, the approval workflow, the payment reconciliation, the audit trail, the counterparty portal — these are the same for maritime, energy, agriculture, and logistics.

This is why we describe Tarshix as "trade infrastructure" rather than "maritime software." Maritime is where we start. It is not where we end.

Our planned expansion follows trade corridor patterns: maritime Nigeria (2026), maritime East Africa (2027), energy and oil/gas (2027), logistics and freight (2027), agriculture and commodities (2028). Each expansion adds domain-specific templates and workflows. The infrastructure remains the same.

For trade businesses in adjacent industries watching our maritime launch: the platform you see today is the platform you will use tomorrow. The invoicing engine that generates a PDA will generate your purchase order. The approval chain that routes a ₦50 million FDA for MD sign-off will route your procurement approval. The audit trail that records every action in a port call will record every action in a cargo lifting.

We build deep for one industry, then go wide. That is the Tarshix thesis.