Customer support decision

Help Scout

A small team can build a lightweight shared inbox + KB + AI-drafting workflow, but replicating Help Scout’s compliance posture, integrations ecosystem, analytics, and production polish is costly—so building a narrow replacement is realistic, replacing the full paid product is not.

Visit website
Subscription$25/month ✓ verified
Initial build80 hours
Monthly upkeep10 hours + $100
Evidence3/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

What a replacement has to do

  • Receive customer messages, surface relevant knowledge-base content, generate an AI draft reply, send email reply and log conversation history.

What it still won’t have

  • HIPAA compliance and audited security posture out of the box
  • Built-in integrations & app ecosystem (100+ apps)
  • Enterprise features: advanced workflows, SLA policies, SSO/SAML, and account management
  • Polished reliability and scale guarantees (uptime/SLAs and large-scale API rate limits)
  • AI Answers automated resolution tuning and analytics

What remains hard

  • Compliance and regulationHIPAA compliance
  • Brand trustWhy do 12,000+ companies choose Help Scout?
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 5 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal self-hosted customer support app with Node.js (Express), Postgres, and a React frontend. In scope: inbound email ingestion (IMAP webhook or SMTP relay), conversation storage and basic thread model, searchable knowledge base (simple vector index or Elasticsearch) with admin UI to add articles, an AI draft endpoint that calls a configurable LLM API to generate reply drafts and conversation summaries using KB results as context, a React inbox UI to review AI drafts, edit and send replies via SMTP/API, and usage tracking to count AI-assisted resolutions and enforce a monthly cap. Out of scope: enterprise SSO/SAML, HIPAA certification, phone/SMS integrations, and multi-tenant billing. Include error handling, input validation, and automated tests for API endpoints and core UI flows.
How we checked5 sources · 3/3 runs agreed · evidence score 64

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 5 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Hard moats found in the evidence-3
  • Evidence score64

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 5

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page