Dennis v.

👋 Founder of Coheed here, building in the least glamorous corner of ops data. Looking for a few launching customers (and for people to tell me where this breaks). The mistakes that cost the most money don't live inside a system, they live between them. A delivery date promised against stock that was already reserved. Work that got delivered and never invoiced. A customer whose margin looks fine until you add what it costs to serve them. Each one needs data from two or three systems that don't talk. So we built the layer that connects them, keeps checking the records still agree, and answers those questions. Then prepares the action, autonomously or for approval. Nothing gets replaced. Who it's for, so you can skip fast: 20–250 person wholesale, logistics and manufacturing companies. My preference would be (for now) companies in Benelux - the connectors are Exact/AFAS/Business Central shaped. I'm looking for launching customers (implementation on us, first year of support included), or 20 minutes for feedback from anyone who's run RevOps somewhere with inventory. Feel free to message me!

Hi, curious about other's experience in this --> I'm starting up a platform around data integration, quality and analytics between / for operational systems. We have a prototype running and are looking for launching customers. So far, I've experienced that it is hard to find launching customers willing to join in on something not running at a large range of clients yet, even though we offer a lot of flexibility and benefits as part of the 'launching customer' offer. Basically, I'm wondering how others have tackled this challenge of going from prototype to launching customers.