I ve been building MapleBridge, a sourcing workflow for North American buyers looking for better-fit Chinese manufacturers.
One thing I kept running into: supplier search is not only a search problem. A buyer can have a very specific brief product, MOQ, target market, packaging, certification path, timeline but most supplier directories still reduce that into keywords and listings.
So I separated part of the work into an open layer.
I m building VoiStory, a parenting app that helps families create personalized bedtime stories in a parent s own voice.
The idea came from a simple but emotional problem:
sometimes parents are tired, traveling, busy, or just don t have the right words at bedtime but they still want their child to feel comforted and connected.
A decade in B2B SaaS taught me one thing: revenue, finance, and ops teams all run off slightly different numbers, and everyone spends half their week reconciling and the other half arguing about whose source of truth is right. So, I built Gohvio, a platform that handles the full path, from ingestion and cleaning through transformation, masking, and visualization, so the people inside your company who actually work with data can stop playing detective and start deciding. What it is: a single, clean data layer that connects CRMs, finance tools, and ops systems so revenue, finance, and ops teams stop arguing over whose numbers are right. Not a Databricks or Fabric replacement. A layer above them, built for mid-market teams those platforms were never designed for. Where I'm at:
Launched publicly April 13
6 beta testers
Website traffic 12 to 52 visitors in 4 days
Not looking for upvotes. Looking for honest feedback and beta testers who actually have this problem.
Beta signup: gohvio.io
Roast the positioning, tell me what's missing. All welcome.
Search is changing. People are asking ChatGPT, Perplexity, and Gemini for recommendations instead of Googling. And most brands have no idea if they're showing up there or not.
So we built Aeoix - track your brand's visibility across AI engines, see where competitors are winning, and act on it directly. You can reach out to publishers, close content gaps, and manage everything from one place.
Hey Product Hunters We re building initdesk an email-first AI help desk for SaaS and lean teams. The idea is simple: support agents should not need to jump between browser tabs, admin panels, CRM, and internal dashboards just to answer a customer.
initdesk brings customer context into the ticket itself, then uses that context to help draft replies, summarize conversations, tag tickets, detect sentiment, and power a help center with AI chat. We also don t charge per seat. You can invite the whole team, and pricing is based on ticket volume instead.
Would love honest feedback on:
1. What customer context would be most useful inside a ticket?
I ve spent years in the broadcasting world and noticed something depressing: while the whole world moved to the Cloud, AI, and sleek interfaces, radio automation software stayed stuck.
Most professional suites today: Look like they were designed for Windows XP. Crash if your local hardware has a hiccup. Make remote broadcasting a nightmare of VPNs and lag.
When I started building DockFM, people told me: 'Don't bother with Mac, radio is for Windows PCs.' I ignored them. I wanted to build something that leverages Apple Silicon power, for 99.9% cloud uptime, and integrates AI Voice Cloning so a DJ can broadcast from a beach without sounding like a robot.
Use the AI Agent to have conversations about artists you search for get more info, similar artists, best songs, best albums, best live concerts, and more.
Listen to an artist's full discography without interruptions.
Accepting new independent artists to register and upload their music.
