Pipe17

As the Plaid of commerce, we at Pipe17 integrate with some of the most awful, legacy, abandoned IT systems on earth. Here's a sampling of some of the worst: - Direct database access: We literally connect to the database and manipulate the data directly. Decades old drivers - EDI over SFTP: EDI is written out to a file and then SFTP'd back and forth - AS/400 (green screens): Lots of flat files - FTP and SFTP'ing flat files: Arbitrary file formats, some random binary encodings, S/FTP'd arbitrarily - EDI VANs: Big clearing networks where EDI vendors swap data - Polling web hooks: Pushes notification that something has changed In many cases, documentation doesn't exist. Someone who's been there for 40 years knows everything and has to personally engage. Sometimes you literally have to go on-site and buy doughnuts and sit down in front of a whiteboard. Individual holes have to be put in firewalls to gain access to systems. Logistics and back office software is frozen in the 80's and 90's and often physically cannot be updated. These companies will go out of business decades in the future never having touched it. They can't. Many of the selling channels we connect up with (Walmart, Amazon, TikTok, Shopify, etc) have newer tech, but require that you: - Join their partner program - Negotiate a Data Protection Agreement (DPA) - Submit to their initial and then ongoing security audits - Pay ongoing fees for the right to connect into their systems - Police your customers to ensure they don't violate the platform's Terms of Service In short - connectivity is HARD and is the problem to solve as merchants deal with more selling channels, back office systems of record, and fulfillment channels. Our unique hub/spoke network abstracts away all the underlying complexity of connectivity, in the same way that Plaid does so for financial services. Plug in your API key and you're good to go! Connectivity is far more than wiring together two APIs. On top of our network, we've built AI-native enterprise order management. But the two are deliberately kept as separate layers. I firmly believe that AI will allow anyone to build an OMS and all the required features. There are already dozens of great OMSes on the market. What AI can't and won't solve is the connectivity problem, which is why our network-first approach to order management is so differentiated and is winning in the market.

Today we launched pipe17.ai ! It's a detailed how to use Pipe17 guide but ONLY for your agents. It's pages and pages of well formatted markdown explaining what our product does and how to use it, including well structured Q&A. This information is previously spread across our .com (which like most websites is JavaScript-heavy and hard for agents to read) and our documentation. This concisely puts it all in one place, with clear markdown. Just copy / paste the instructions to your agent (from the "Human") tab and your agent will then have everything available from the "Agent" tab. (Thank to Mathias Biilmann Christensen who I shamelessly stole this idea from. He has long been talking about optimizing for "agent experience" and he is now proven to be right) https://pipe17.ai/

Smart move. Won't fix stockouts on its own. Unifying planning is real progress. Optimizing safety stock by store, region, and local demand is exactly the kind of problem AI is good at. At Lowe's footprint, the upside is huge. But planning is only half the system. The other half is execution: intelligent routing and sourcing, real-time inventory sync across channels, and exceptions resolved before a customer hits an empty shelf. That layer is fragmented at almost every retailer I talk to, even ones with sophisticated planning stacks. A better plan routed into a fragmented execution layer doesn't eliminate the stockout. It just diagnoses it faster. This is the gap we're closing at Pipe17 . Planning decides where inventory should go. Order Operations makes it actually happen. So the question isn't "do we have unified planning yet?" It's: what keeps breaking after the plan is right? Where's that gap hitting hardest for you? Routing, inventory accuracy, exceptions, or vendor execution? https://lnkd.in/g6aZXvav

A week ago, Anthropic released Claude Design which allows you to build entire presentations that adhere to a specific design system. Here I show in 11 minutes how simple it is to build deeply customized presentations using a fictional company - Chubbs Peterson's pro shop. This has quickly become the default way that we at Pipe17 are building presentations because they're dramatically better and faster than taking the gold pitch deck and lightly modifying it for each pitch. First, start by going to Claude where you'll use it to build an entire outline. Here's the prompt I used: --------------------------------- In an alternate universe, Chubbs Peterson from Happy Gilmore survived and opened his own pro shop. - Pro shop has gone viral and is now selling $250m annually through Shopify, TikTok, Amazon, Walmart, and EDI - They use Celigo to connect up their selling channels to NetSuite. Getting expensive and difficult to sell through new channels - They have an owned warehouse running Logiwa and also use Ryder as a 3PL I'm meeting with Chubbs himself tomorrow and would like you to build a slide deck I can present in 20 minutes. Chubbs is a golfer by training, so be sure to use corny golf analogies throughout. Claude Design will be building the presentation for me. Build a full markdown file with detailed instructions for content and visual design for each slide. I want to simply paste the output here into Claude Design Design notes for Claude Design: - Stick to the Pipe17 design system - Make the slides visually appealing - use lots of golf imagery. Avoid using too much text - Chubbs is a CEO - Ensure text isn't over the top of images, so that it's hard to read - Double check that the slides look great visually --------------------------------- In a normal pitch, Claude would have access to: - HubSpot / Salesforce data - Transcripts from previous meetings - Intel from various SI and ISV partners - Emails / Slack All of that data is then used to build the outline. You can get as detailed as you wish in building the outline. Make sure to use Opus 4.7 (the newest model) and turn on adaptive thinking so it thinks longer. As you can see in the video, it then spits out a full outline including detailed visual guidelines. Copy that outline and then paste it into Claude Design, selecting your company's design system. Your design system captures visual elements, color palettes, fonts, spacing, rounding of buttons - hundreds of visual design elements. Then you can see in the video how Claude Design actually builds the slides, while adhering to your company's design system. It's not perfect by any means. You'll want to swap out the clip art-type photos with real photos, and hit "Comment" to have it update the design in real time. Then export to .PPTX which you can then import into Google Slides. This has been on the market for exactly eight days. It's only going to get better from here!