The Scrappy Stack includes paid partnerships with featured brands. Compensation may influence which products we highlight; it does not influence our editorial standards. See our Disclosure Policy for details.

The Scrappy Stack
5 min read

Do You Need a Help Desk Yet? A Solo Founder's Support-Stack Decision Guide

For a team of one, a help desk is often the fifteenth tool you didn't need. Here's the decision rule for when a shared inbox is enough, when you've actually outgrown it, and what to reach for next.

By Dana Okafor

TL;DR — If you're a team of one to three and doing under roughly 20–30 support conversations a week, you do not need a help desk yet — a plain shared inbox (a `support@` address) is not just cheaper, it's better at that volume. You've outgrown the inbox when you can name a specific recurring pain: threads getting dropped, no idea who's handling what, or the same question answered from scratch for the tenth time. Adopt the help desk to kill that named pain, not because it feels more professional.

  • Under ~20 conversations/week, solo or tiny team: a shared `support@` inbox. Stop there.
  • The upgrade trigger: a named, recurring failure — dropped threads, collision, or repeated answers — not a vibe.
  • First real help desk: the smallest tool that fixes the specific failure (assignment, saved replies, or basic reporting) — not the all-in-one platform.
  • Buy immediately, no inbox phase: nothing here. Support is exactly the workflow where boring-first wins.

The default answer is a shared inbox

When the first support emails trickle in, the instinct is to go shopping for a "customer support platform." Resist it. The most boring thing that works — a shared inbox on a `support@` address — is genuinely the right tool for a very long time, and it costs nothing beyond the email you already pay for.

The setup is trivial: a `support@yourdomain` address that lands somewhere you and any co-founder can both see. That can be a shared mailbox in the email provider you already run, or a lightweight group/alias that fans out to your personal inboxes. At the volume a young product actually has — a handful of conversations a day — this handles everything a help desk would, minus the monthly fee and the setup project.

More importantly, the inbox teaches you the shape of your support. Before you buy a tool that imposes someone's opinion of how tickets should flow, you want to have felt your own patterns: what people actually ask, how fast you can reply, where the repetition is. Six months in a shared inbox is the cheapest customer-research you'll ever run.

The three signals you've actually outgrown it

A help desk is earned, not adopted. You've earned it when you can point to a specific, recurring, named pain — not a general sense that you "should" have one. In practice it's one of these three:

1. Threads are getting dropped. An email arrives, you glance at it, mean to reply after lunch, and it slides up the inbox and dies. If customers are falling through the cracks because nothing tracks "this is open and unanswered," that's the inbox straining. A help desk's core job is making the open/closed state of every conversation visible.

2. You and a co-founder keep colliding. Two people, one inbox, and you both reply to the same customer — or neither does, each assuming the other had it. The moment there's more than one person, you need assignment: who owns this thread. A shared inbox has no answer for that; a help desk does.

3. You're answering the same question for the tenth time. When a real fraction of your volume is the same handful of questions, retyping the answer each time is a tax. Saved replies / canned responses (and, eventually, a public help doc that deflects the question before it's asked) are the fix. If you can list your top five repeat questions from memory, you've hit this signal.

If you can't name which of these is hurting, you haven't outgrown the inbox — you're shopping. That's the tell.

What to reach for — smallest tool that kills the pain

When a signal is genuinely lit, buy without flinching. But buy narrow. The mistake is jumping to the all-in-one support-and-CRM-and-chat-and-knowledge-base suite that you have to configure into usefulness — for a small team, that configuration is a project you don't have the attention for.

Match the tool to the specific pain:

  • Best for "threads get dropped" + "we collide": a simple shared-inbox help desk — the lightweight category (tools like Help Scout, Front, or Plain live here) that adds assignment, open/closed status, and a shared view on top of email, without the enterprise scaffolding. It should feel like your inbox with the two missing features bolted on, and work on day one.
  • Best for "same question ten times": start with saved replies inside whatever inbox tool you land on, then a small public help doc. The doc is the higher-leverage move — it deflects the question entirely — but it's also more work, so do it once the repeats are proven, not speculatively.
  • Best for "I just need reliable delivery": that's not a help-desk problem, it's an email-infrastructure one — make sure your `support@` domain has its email authentication (SPF/DKIM/DMARC) set up so your replies actually land, whether you're on a shared mailbox or a help desk.

Notice what's not on this list: a reason to buy the biggest platform first. There's no support tool you need on day one the way you need a real payments provider on day one. Support is pure internal workflow — flexible, cheap to change, easy to migrate. It's the textbook case for staying boring until it hurts.

The honest tradeoff

The failure mode of this advice isn't buying too early — it's the opposite. Founders who take "run lean" as identity will limp along on a chaotic inbox well past the point customers are being dropped, because switching feels like admitting defeat. Don't. The rule is earn the tool, not never buy the tool. When one of the three signals is clearly lit, a help desk pays for itself in a week of recovered dropped threads and un-retyped answers — and the twenty-dollar-a-month fee is nothing against a churned customer who emailed twice and got no reply.

So: default to the shared inbox, let it teach you your patterns, watch for one of the three named signals, and the moment one lights up, buy the narrowest tool that kills it. A support stack isn't the one with the most features. It's the one where every customer who writes in gets an answer — and you can tell, at a glance, that they did.