ReqChain

Stop approving company purchases over WhatsApp

3 followers

Stop approving company purchases over WhatsApp

3 followers

Visit website

AI Workflow Automation

ReqChain turns scattered purchase requests into one traceable workflow. Anyone submits a request; it moves through the approval levels you define, by role. Attach quotes, then invoices and payment slips, so finance only pays what was actually approved. It also has a supplier side: publish a catalog with today's prices and let your business customers order from it. 14-day free trial, no card required.

Free Options

Launch tags:Productivity•SaaS•Finance

Launch Team / Built With

LightfieldAI-native CRM that builds itself and does work for you

Promoted

Hunter

📌

I’m Felipe, the founder of ReqChain. I started building ReqChain because I kept seeing the same problem: companies trying to manage important purchasing processes through WhatsApp conversations, spreadsheets, emails, and disconnected systems. The problem isn't that these tools are bad. The problem is that the actual procurement workflow gets fragmented between them. A request starts in one place. A supplier responds somewhere else. Someone updates a spreadsheet. Another person asks for the status in a WhatsApp group. And suddenly, something that should be a simple purchasing workflow becomes operational chaos. ReqChain is my attempt to solve that. The idea is simple: bring companies, distributors, and suppliers into one connected workflow and eventually build a much smarter layer on top of the purchasing process. We're still early. We don't have a huge customer base or impressive traction to show you yet. What we do have is a product, a problem we genuinely believe is worth solving, and a lot left to build. If you work with procurement, purchasing, distribution, or operations, I'd genuinely love to hear: How does your company manage purchasing today? What still lives in WhatsApp, Excel, email, or manual processes? Try ReqChain, tell me what breaks, tell me what we're missing, and tell me what you'd want this product to become. We're building this in public, one workflow at a time. 🚀

Report

2mo ago

Forum Threads

p/reqchain

•

19d ago

The lock-in in AI app builders isn't the hosting. It's the build config.

Two months ago my production backend went offline. Not a bug, not traffic my credit balance hit zero, and the managed backend shut down with it. No users were affected, since I don't have paying customers yet, but the product was simply gone, for a reason that had nothing to do with my code.

That week I moved the database to my own Supabase. Harder than expected, for a boring reason: the dump was a custom-format file with zstd blocks and pg_restore refused it. I ended up reading the TOC with pgdumplib and pulling the data out by hand. 16 tables, 362 rows, 6 accounts with their original password hashes. I compared md5 on both sides before switching over. It worked, and the app has run on my own database ever since.

Last month I looked into moving the hosting too. That's where it got interesting.

I expected "connect GitHub, deploy elsewhere." But the build config isn't really mine. It imports a proprietary package that already bundles the framework, Tailwind, path aliases, env injection and the server adapter and the file itself warns that adding those plugins manually breaks the app through duplication. Leaving isn't a deploy step. It's rebuilding the build.

p/reqchain

•

20d ago

How do you stop being your team's human reminder?

Every week, the same loop.

I'd ask someone to handle something: get three quotes, review the marketplace listings, pull numbers for the marketing meeting. A few days later I'd follow up. The answer, more often than not: "Sorry, I forgot."

The thing is, they weren't lying. The task was a message in a group chat, buried under fifty others by the next morning. I was asking people to remember things I'd given them nowhere to keep.

View all