View it, test it, tear it apart, here’s how I did it (link to live platform below).

We’ve spent the past decade asking tradetech platforms to be more user-friendly, more interoperable, and more responsive to actual workflows.

Heading home from some networking drinks, I’d heard of some AI code-gen software (think ChatGPT or Bard, for code). I decided to give it a try.

With $20, 2 hours, and a prompt-based AI development tool called loveable.dev, I (think I) created a functioning prototype of an electronic Bill of Lading platform. And when I say “functioning,” I mean:

  • You can issue and view eBLs
  • You can simulate a title transfer
  • You can plug in integrations like SAP, Finastra, or WaveBL
  • You can view a map of port movements
  • It was mobile first (because no one is allowed to bring their laptops into bed)

You can test it (link at the end of this article).

How it started…

I began with ChatGPT’s ‘Deep Research’ tool to refine the spec and logic. My high-level prompt looked something like this:

“Design a next-generation eBL platform for corporate commodity traders. It must solve adoption and usability gaps in platforms like CargoX, Enigio, WaveBL, ICE Digital Trade, Bolero, and Secro. It should support structured BL metadata, full MLETR compliance, transfer of title, digital endorsements, ERP integration (SAP, Oracle, Dynamics), and mobile-first UX. Branding must follow TTP guidelines. Make it elegant, modular, and API-ready.”

I also uploaded a few of my recent articles around interoperability challenges, the state of trade document digitlisation, etc., although LLM’s are pretty smart, they know this stuff already.

…how it’s going

With the spec ‘output’ mapped out in ChatGPT, I moved over to Loveable.dev. It’s an AI tool for non-coders like me (admittedly, I sometimes use the CSS rule !important before getting shouted at by my developers for breaking our website).

I asked it to build the next-gen eBL platform branded under Trade Treasury Payments. The brief was to create a structured app for corporate traders, shipping lines, and freight forwarders who might regularly issue the one document that many are trying to digitalise: the Bills of Lading.

The platform needed to do three things well: issue, transfer, and surrender eBLs.

Loveable generated a clean TTP-branded dashboard (ICYMI, I love orange).

Then I prompted it to add an eBL creation wizard. It gave me a multi-step form with metadata fields like consignor, consignee, vessel name, weight, goods description, Incoterms, and port codes.

I felt like the mockup could’ve gone further. I wanted this app to look a bit more workable and have usable functionality. I told it:

“Add title transfer logic. Show an audit trail and a transfer timeline.”

It built a version history tracker, a progress bar for endorsements, and transfer status labels. All on a responsive mobile layout.

Everyone loves a marketplace.

So I used the prompt:

“Add to integrations the ability to integrate with Enigio, CargoX, WaveBL. Add some accounting software integrations like Xero. Add ERP integrations like SAP. Add trade system integrations like Surecomp and Finastra. Make this look like a marketplace integration feature.”.

Of course, it mocked up tiles, added status states (Connected, In Progress), filters, and even included star ratings and install buttons.

Every time I wanted something more technical, like visual document timelines, port route maps, or ERP plug-ins, another prompt was just around the corner.

I created free accounts with Mapbox and some authentication solutions so that you can integrate better. Supabase powered the backend (there’s a free account, too).

At one point, I told it the mobile pages weren’t scrolling properly. It fixed the scroll logic. The ‘All eBLs’ page wasn’t rendering on iPhone. I prompted it again, it refactored the layout.

Red flags and compliance? I asked it to build in red flag alerts: checks on sanctioned ports, duplicate shipments, and suspicious metadata entries. It added a compliance module with basic screening logic and inline warnings right inside the eBL creation flow.

Next, I wanted visibility. I prompted it to build a reporting and analytics dashboard, daily eBLs issued, transfer times, top trade corridors, and average surrender delays.

It created a clean overview panel with filters, charts, and export options. And yes, it worked on mobile.

Screenshot

Then I ran out of credits, and realised I have work to do.

Why does this matter?

Whilst I fully expect you to rip this product apart, the excuses are running out.

For years, we’ve been told that trade digitalisation takes time, is complex, and that integrations are tricky. We’ve also been told that regulation slows everything down. And sure, some of that is true.

But, if I can build this, you can, and if you can, I don’t think tech is the problem. Adoption? Inertia? Lack of education?

Furthermore, for the tradetechs, this build proves something uncomfortable.

With no dev team, no VC funding, and no proprietary stack, I can build this rapid prototype. What is going to differentiate you from your competition? What will the new competition look like?

Product development, pace, and priorities have stepped up. The only question now is whether incumbents and innovators are willing to move faster.

The future of tradetech isn’t a roadmap. It’s a prompt.

And now anyone can write one.

Go build, friends.

Here’s my eBL app*

*Hey, any VC funders about and want to have a conversation? 😉