Original Summary

Hey folks, Full-time IT job by day, and for the past year I've been building my first SaaS on nights and weekends. It's a document-processing API for no-code people: the problem was that every time I needed to merge PDFs, pull data out of invoices, or turn an HTML template into a PDF inside a Zapier/Make flow, I ended up paying for three separate tools or writing a script nobody else could maintain. So I built one place for all of it. It's now at 51 tools (convert, merge, split, compress, OCR, structured data extraction, redaction, templated document generation), each exposed as a REST endpoint, plus a visual Flows builder so non-coders can chain them and connect to Make, Zapier, n8n, Airtable and Sheets. Here's where I want the community's perspective. I have zero paying users and I suspect I did the classic engineer thing: kept building breadth instead of getting one workflow into someone's hands early. Pricing is credit-based, free tier up to $249/mo, and I'm now trying to get first traction via directory listings, community answers and outbound. For those of you who've been past this stage: 1. When you had a wide feature set and no customers, did narrowing to one use case work, or did the breadth end up being the moat? 2. For an API-first product aimed at no-coders, is a native Make/Zapier module non-negotiable, or does a REST endpoint plus good docs get you the first 10 customers? 3. What would you cut first if you were me? Happy to share the name in comments if anyone asks, but not looking to pitch here. Just want to learn from people who've done the 0→1 part. Cheers!   submitted by   /u/Dry-Care1428 [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/14 15:43:39