— Bootstrapped · Building in public

HOW SAAVOS IS
being BUILT.

Bootstrapped and built in public. Here's the problem I saw, what I built to solve it, and where the product is headed.

— The problem I saw

VISITORS BOUNCE.
FOUNDERS pay for it.

A visitor lands on your site at 11pm. They have one question — “does this work with Webflow?” — and you don't have live chat. They bounce. You never know it happened. This plays out on solopreneur and small SaaS sites hundreds of times a day.

The cheap fix is a template chatbot: pick from 12 canned flows, watch visitors ignore it. The “real” fix is Intercom or Drift — $65+ per seat, built for a team of five support agents you don't have yet. Somewhere in between there's a tier of AI chatbot products that charge per resolution. Your bot has a good week on Reddit and you get a surprise invoice. Fun.

What I wanted was simple: point it at my site, get a bot that actually knows what's on my site, embed it in five minutes. Flat pricing so I stop thinking about cost per chat. Frontier model because confident hallucination is worse than no bot at all.

— What I'm building

SAAVOS. PASTE A URL,
get a bot.

You paste a URL. saavos fetches your site, chunks the content, embeds it with text-embedding-3-small, and stores it in pgvector on Supabase. When a visitor asks a question, it retrieves the right chunks and runs them through the latest Claude — the frontier model, not the economy one. Citations ship on by default so the bot links back to your real content instead of confabulating.

Pricing is flat: free / $9 / $24 per month. No per-resolution billing. No per-seat charges. Your bot has a big week? Same bill on Solo and Builder. Quiet month? Same bill. Every paid plan runs the same Claude — I didn't want to gate the model between tiers and then wonder why early customers churn.

— Where it stands

BUILT TO
PRODUCTION STANDARD.

The product is production-hardened — billing webhooks, ingest pipeline, embed widget, citation-grounded retrieval. Payments run through Dodo Payments as merchant-of-record, so billing and tax compliance are handled by infrastructure built for exactly that.

Infra: Supabase (Postgres + pgvector + Auth + Storage), Vercel for hosting, Resend for transactional email. No third-party support tool, no analytics bloat, no cookie banner. Stack is locked and boring on purpose — boring infra means I spend time on product, not ops.

6
SEO posts published
5
Vendor comparison pages
3
Infra services
5 min
Time to first bot
24h
Support reply time
Weekly
Feature releases
— What's next

THREE THINGS.
in order.

  1. 01Grow paying usage — everything else is a distraction until the product earns it.
  2. 02npm publish the SDK — so developers can wire saavos into their own stack without touching the embed widget.
  3. 03SOC 2 Type II — the unlock for selling to teams that run a security checklist.
— Try it · Follow it · Say hi

THE BUILD IS public.

Story — saavos