The $0 support stack for solo founders

Buttr, reviewing the Intercom invoice: "interesting. that's a lot of zeros in the wrong direction."

A solo founder at under $3K MRR can run a complete support operation — AI chat, human handoff, bug tracking, docs, and uptime monitoring — for $0/month. Self-hosted Krispy handles the chat and Telegram handoff on Cloudflare's free tier. GitHub Issues covers bugs. A Notion doc absorbs 60% of repeat questions. Total monthly cost: $0.

What does a solo founder's support stack actually need to do?

Five jobs. That's it:

1. Answer common questions when you're not around
2. Route edge cases to a human (you) fast
3. Capture leads who had a question but never wrote in
4. Let users report bugs and search for existing answers
5. Tell you when something is broken before users assume it's permanent

A $400/month enterprise plan covers all five — plus seventeen dashboards you will never open. Each job below has a free alternative.

How does AI chat and Telegram handoff work for $0?

AI-powered live chat with human handoff used to cost real money. Intercom's Essential plan starts at $39/seat/month (source: intercom.com/pricing); Crisp's team plan runs $95/month. Self-hosted Krispy covers the same core loop — bot answers, human takes over, bot resumes — for nothing.

Krispy runs on Cloudflare Workers. Cloudflare's free tier gives you 100,000 Worker requests per day and 10ms CPU time per request (source: Cloudflare Workers limits). For a chat widget on a side project, that is large headroom. Krispy also uses Workers AI for inference, so there is no separate OpenAI key or per-token bill. When a visitor needs a human, Krispy fires a Telegram notification. You reply in Telegram; it appears live in the widget.

Setting Krispy up on Cloudflare takes one command after cloning:

git clone https://github.com/krispyai/krispy
cd krispy
cp .env.example .env   # add your Telegram bot token + Cloudflare account ID
wrangler deploy

Widget live. Handoff working. You own the data. If you ever outgrow the free limits, Cloudflare's paid Workers plan is $5/month — still not $95.

What covers email, bugs, docs, and uptime?

Email collection — $0 to start. Buttondown's free tier handles up to 100 subscribers; Mailchimp's covers 500. You do not need drip sequences yet. You need somewhere to put the email address of the person who asked a useful question and deserves a follow-up when you ship the fix.

Bug reports and feature requests — $0. GitHub Issues is free for public and private repositories on GitHub's free plan (source: github.com/pricing) and already has search, labels, and cross-references. A public repo lets users find existing answers before they write in — which cuts duplicate questions without you touching anything. Add a short CONTRIBUTING.md pointing to Issues and you have triage for free. Linear's free tier works if your project is closed-source.

Documentation — $0. A three-page Notion doc or GitHub wiki catches 60% of support volume at most small projects. Write it once; it works while you sleep. Link it from your site footer and from the bot's first message so people find it before they type.

Status page — $0. Upptime (GitHub Actions, fully free) and Instatus's free tier both work. When something is down, users check the status page before writing in. Five minutes to configure; saves hours of "is this down for you too?" threads.

What does the honest cost math look like?

The per-seat pricing model used by enterprise support vendors was designed for procurement teams counting headcount, not for one person doing five jobs. At $74–400/month for a typical paid stack, you are buying a pricing structure that was never built for you.

What do you actually give up with this stack?

One inbox. With this stack, conversations arrive through Telegram, bugs through GitHub, and email through Buttondown — three places instead of one. That is a real coordination cost.

You also give up automatic CSAT reporting, SLA tracking, and conversation tagging. If you need those today, you are probably past the stage where "free" is the binding constraint.

Self-hosting means you are the operator. When Krispy ships an update, you pull it and redeploy — one wrangler deploy, about 30 seconds. If you would rather not think about it, Krispy Cloud runs the same AI chat and Telegram handoff with a 14-day free trial at $19/month flat — same open-source codebase, managed for you.

When should a solo founder start paying for support tools?

When the coordination cost of checking Telegram, GitHub, and email takes more than 3–4 hours a week of active management. Not before.

Most indie projects take longer to outgrow this stack than they expect. Cloudflare's free tier headroom is real. The Telegram handoff is fast once you are used to it. Adding a VA or co-founder to your Telegram bot or group costs zero — there is no seat, no invoice delta. That is exactly the per-seat trap that enterprise support pricing creates: one part-time helper should not double your bill.

FAQ

Can a solo founder actually run real support for $0?

Yes, for most founders at under $2–3K MRR. Self-hosted Krispy covers AI chat and human handoff at zero cost. GitHub Issues handles bug tracking. A Notion FAQ absorbs repeat questions before they become tickets. Cloudflare's free tier handles 100,000 Worker requests per day — more headroom than most indie projects will ever use. The stack holds up comfortably through 30–60 active support conversations a month without strain.

What's the actual catch with Cloudflare Workers' free tier?

The limits are 100,000 requests per day and 10ms CPU time per request (per Cloudflare's public Workers documentation). For a chat widget on a side project, that is large headroom. Very long AI inference calls may occasionally push against the CPU limit; Cloudflare's $5/month paid tier extends that to 30 seconds per invocation. In practice, most Krispy conversations stay well inside the free limits.

How does the Telegram handoff actually work?

When a visitor's message needs a human, Krispy sends a Telegram notification — to you, or to a Telegram group if you have a small team. The notification includes the full conversation context. You reply in Telegram; it appears live in the visitor's chat widget within seconds. Krispy steps aside while you are active and resumes automatically when you go quiet. Most handoff conversations close in under two minutes.

What happens when I bring in a VA or co-founder?

Nothing changes on the bill. Add them to your Telegram bot or group for zero — there is no seat, no invoice delta. This is exactly the per-seat trap that a $0 stack sidesteps: adding one part-time helper doubles your bill only on tools that invented that pricing model.

When should I actually pay for a support tool?

When managing Telegram, GitHub, and email takes more than 3–4 hours a week of active coordination. At that point, a $30–50/month unified inbox pays for itself in reclaimed focus. Below that threshold — especially while you are still learning the shape of your product's support load — the $0 stack wins every time.

If you want to try it: star the Krispy GitHub repo — it helps other builders find it. And if running infrastructure is one thing too many right now, Krispy Cloud is a 14-day free trial, $19/month flat after that — same bot, no terminal required.