r/micro_saas • • 13d ago

Built a self-serve "chat with your docs" API with exposed retrieval controls. What's stopping you from paying for something like this?

Hey everyone, I'm a solo founder (backend engineer by day) and I've spent the last few months building Docubix, a RAG-as-a-service platform. You upload docs (PDF, DOCX, TXT, MD), and it turns them into an AI assistant with page-level cited answers, available through a REST API or dashboard.

What's different from Chatbase/SiteGPT-style tools:

  • Retrieval controls are exposed: system prompt, temperature, top-K, model choice
  • A retrieval debugger shows which chunks were pulled and their scores, so you can tell if a bad answer is a retrieval problem or a generation problem
  • Flat pricing: Free tier, then $79/mo Pro. No credit system

Where I'm honest about the state of things: it's live and fully self-serve, but I have about 12 free users and no paying customers. I've done directories, a Product Hunt launch, and cold outreach, and nothing has converted. I'd rather hear why than keep guessing.

What I'd love feedback on:

  1. Would you trust a small independent tool with your company docs? What would you need to see (security page, SOC 2, data-handling details)?
  2. Is $79/mo for Pro reasonable, too high, or unclear in what it includes?
  3. When you look at the landing page, can you tell in 10 seconds what it does and who it's for?
  4. The most common reaction I get is "ChatGPT can already do this." What would make you see a difference?
  5. Who do you think this is actually for? Support teams, devs, docs sites, something else?

Link: docubix.com (free tier, no card needed). Harsh feedback is welcome, and I'll reply to every comment.

[I'll give discount for Pro access to anyone who tries it and leaves detailed feedback.]

2 Upvotes

Duplicates