A two-person SaaS team gets 40 support emails a week. They answer maybe 15. The rest age out or get a one-line reply days later. They're not ignoring customers on purpose — they simply don't have the time to write thoughtful replies to the same billing, cancel, and 'how do I do X' questions repeatedly. The complaints users file ('no response,' 'three days waiting,' 'barely get back to you') are symptoms of this math problem.

Existing support tools are built for support teams — they assume roles, routing rules, SLAs, and managers. A two-person SaaS company doesn't need a ticketing system; they need drafts already written when they open their inbox so responding takes 30 seconds instead of 5 minutes. No existing tool is optimized for this because the buyers of Zendesk, Intercom, and Freshdesk are support managers at companies with dedicated headcount, not founders who answer tickets between sprint planning and investor calls. The founder is both the buyer and the user here, and nobody is building for their actual constraint.

The complaint 'there is no way to contact a real person for support' points to something deeper: these companies eventually stop offering live contact at all because the overhead is too high. An inbox that pre-drafts replies using the product's own documentation, past resolved tickets, and billing history means a founder can process a queue of 40 tickets in under an hour — which means they keep the channel open instead of hiding the contact form.

This is a business because every new customer cohort generates a fresh wave of the same questions, and as the product grows, the queue grows faster than the team. The cost without it is founder time at $200+/hour spent copy-pasting the same answer about how to cancel.

What to build

Build a lightweight shared inbox for SaaS founders that automatically drafts replies to incoming support emails by pulling from the product's help docs, recent changelog, and the customer's own account and billing history — founders review and send in one click, or edit before sending.

Where to start

Start with Stripe-integrated SaaS tools specifically — pre-pull subscription status, last charge, plan name, and trial end date into every draft so billing replies are immediately accurate, which is both the hardest part to get right and the most common ticket type.

The hard part

Draft quality has to be high enough that founders trust it without reading every word — one bad auto-draft sent to a customer poisons trust in the whole system, so accuracy on billing and account-specific questions (which require live data, not just docs) has to work from day one.

How it makes money

Flat monthly fee per workspace ($49–99/month), free up to 50 tickets/month to let founders feel the value before paying.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in AI Writing Assistant.

More ideas in AI Writing Assistant