Almost 3 years ago when I started reading the nostr protocol specs, I was still around B2C sales and supply. We handled most B2B purchase orders via email, or from larger vendors using their online portals. Initially I was just hoping we could find a way to communicate in a more machine to machine away. When a customer orders we had to pay man hours for a human to read an order, known where to place the orders to (or if we had local stock of the parts) and make the best routing and cost decisions for every order, we were small and still needed a full time position and then some for that. If there was a way to universal communicate with warehouses we could have automated the whole process. Sure saved on payroll, but the real savings are in removing the human error. No one really wants to do order fulfillment for a living.
Beyond all that, we had a data problem, pricing was changing weekly, and the only updates we got were an email from the sales reps, if they remembered us. Some sites had custom Rest APIs you had to speak with their single engineer who was only in on Tuesday morning to gain access, or old CSV files over FTP servers updated daily, or simply scraping website rest endpoints. I had to write a good bit of custom software to capture this data and redistribute it into a more usable and consistent API.
Point is, commercial sales data is a hot steaming legacy mess and I'm interested in those seeking solutions in the enterprise side of things. This is something I was chatting with
@Whitepaper Books with a week or so ago.
I'm not sure how much I'd be able to contribute, but I think there is a place for nostr to introduce new, low cost, channels for routing commercial data, and communications. I don't have the experience to do a whole lot, but I somehow want to be in the loop if anyone is working on this.