# A support forum for an early-stage startup with a one-person support team Author: Forum Cat Author URL: https://forumcat.com/blog/author/forum-cat Published: 2026-09-04 Category: Customer support Category URL: https://forumcat.com/blog/category/customer-support Meta Title: A support forum for an early-stage startup Meta Description: The one-person support playbook: what to set up first, what to skip until a trigger fires, and how a public forum keeps answers working while you build. URL: https://forumcat.com/blog/support-forum-for-startups Customer support for an early-stage startup needs three things. One address customers write to. One public place where answers live. One habit of answering repeat questions in public. That is the whole system at this stage. Skip the help desk, the chat widget, the saved replies, and the staffing plan until the volume forces them on you. A help desk is a tool that turns customer emails into tickets and assigns them. You do not need one yet. The rest of this post is the order to do things in, and what each step costs. ## Why one person changes the plan The person answering support is also building the product. Every minute spent typing the same answer twice is a minute not spent shipping. That is the argument for writing answers in public. The gain is where your hours go this week, more than any percentage of tickets avoided. Here is the arithmetic, with example numbers you should replace with your own. Say support takes eight hours a week today. Say half of those hours go to questions you have already answered for someone else. That is four hours a week. Four hours a week is a full working day every fortnight. Publishing the repeats is how you get that day back. The first customer to ask still costs you the ten minutes. The next twenty cost you a link. The numbers above are an example, not a measurement. Run yours for two weeks before you trust them. ## Step one, one address Every support channel points at one address. One mailbox, one place to look. Do not open live chat yet. Do not publish a phone number. Do not open a shared Slack channel per customer, which is a private chat room you and one customer share. Five channels with one person means four of them get ignored. An ignored channel is worse than a missing one, because the customer waited in it. Someone who cannot find chat will email you. Someone waiting in chat thinks you are rude. Put that one address on the site, in the app, and in your footer. Use a shared address like support at your domain, not your personal mail. Changing it later is annoying, and personal mail cannot be handed to a second person. ## Step two, answer everything within a day At this stage speed is the entire quality bar. A short correct answer today beats a polished one next week. Answer badly if you have to. "Yes, that is a bug, I am fixing it this week" is a good answer. So is "I do not know yet, I will write back Thursday." Both tell the customer where they stand. You can improve the wording later, when the same question comes back and you publish it. The first reply just needs to be correct and fast. Early customers forgive rough answers. They do not forgive silence. A four-day gap is what makes a small company feel unsafe to buy from. ## Step three, keep a tally of the repeats Every time you answer something for the second time, write the question down in the customer's words. Their words, not yours. If they wrote "how do I stop the emails", do not file it as "notification preferences". The customer's phrasing is what the next person will type into a search box. A text file is enough. Add a tally mark each time the question comes back. After two weeks you have a ranked list of what to publish. Do not hand this job to anyone else. The tally is product research. Five people asking how to cancel is a support fact. Five people asking where their data went is a product problem, and you want to read that list yourself. ## Step four, open a public place for the answers Open the public place once the tally has ten questions on it. Do not open it before then, and do not wait much longer. The place is a set of public pages, one per question, that anyone can read and search without an account. Customers ask in the open. You answer in the open. Each answered question stays up as a page the next person can find. Seed it with your tally. Seeding means writing those first threads yourself, from questions your inbox already answered. Ten to twenty solved threads and three to five categories is enough to go live. A category is a named group of threads, such as billing or getting started. Our post on [how to seed a new forum](https://forumcat.com/blog/seed-a-new-forum) walks through the writing part. ![The create a forum form in the Forumcat dashboard, filled in with a forum name and web address](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/03b-new-forum-filled-1788188160710-compressed.png) _Setup is the small part. The tally in step three is the work._ Mark the reply that solved each question as the accepted answer. The accepted answer is the one later readers should trust. It pins under the question, and the thread shows as solved. That is what makes a page usable by someone who was not in the conversation. ## Step five, route the repeats Routing means you point a repeat question at a public page instead of answering it only in email. When a repeat arrives, answer it in public first. Then reply to the person with the link and a line of context. You still helped them, and you left a page behind for the next one. Put the link where people already look. Your site menu, your email signature, and the auto-reply your mailbox sends when someone writes in. This habit takes about a week to build and it is the part that compounds. Answering in email only is where the four hours go. Answering in public is the same work with a page at the end of it. This is the whole idea behind [customer self-service](https://forumcat.com/customer-self-service). ## What to skip until later Skip anything whose job is coordination. You are one person, so there is nothing to coordinate yet. Skip the help desk until two people answer support, or until you lose track of a thread and a customer has to chase you. Those are the two triggers. When one of them happens, read [what to check before you buy help desk software](https://forumcat.com/blog/before-you-buy-help-desk-software) first. Skip live chat until someone is reliably online during posted hours. Chat sets an expectation of minutes. Breaking it costs you more than never offering it. Skip saved replies until you send the same answer daily. Below that, writing the reply fresh is faster than finding the template. Skip the status page until you have had a second outage. A status page is a public page showing whether your service is up. One outage is an email to the affected customers. Skip the chatbot. At your volume it will answer worse than you do, and the questions it fails on still land in your inbox. ## What breaks first as you grow The first thing that breaks is an unanswered question sitting in public. A forum with old unanswered threads reads worse than no forum. A visitor sees a question from March with no reply. They conclude that writing to you is pointless, and they leave. Answer everything, or do not open the place. If you go on holiday, say so in a pinned post. If a question needs a week, reply and say a week. Keep one view of unanswered threads and check it daily. On a one-person team that check takes a couple of minutes, and it is the only recurring duty the forum adds. ![A Forumcat portal filtered to solved questions, showing a short list of answered threads](https://prod.superblogcdn.com/site_cuid_cms24a31a00k901w1st1x9bu5/images/01-home-sort-solved-1788188145446-compressed.png) _Twenty solved threads is enough to open with._ Forumcat is one way to run that public place. A portal is live in about five minutes and there is nothing to install. It costs $9 one time on a Forumcat subdomain, which is an address like yourcompany.myforumcat.com. A custom domain and higher caps are $99 a month, and the trial runs 7 days with no card. Customers read and search without an account, and sign-in is a magic link, a six-digit email code, or Google. The setup for [a hosted support forum](https://forumcat.com/support-forum) is close to the same for a SaaS product, and there is a separate post on [a support forum for SaaS](https://forumcat.com/blog/support-forum-for-saas). Forumcat does not do two things. It is not a ticketing system, and it does not take email in, so customer emails still land in your inbox as they do today. It sits beside whatever mailbox you use rather than replacing it. Keep reading: [how to seed a new forum](https://forumcat.com/blog/seed-a-new-forum) and [what to check before you buy help desk software](https://forumcat.com/blog/before-you-buy-help-desk-software). ## FAQs Q: Do I need a help desk as a startup? A: Not while one person answers everything. A mailbox handles it, and a help desk mostly adds routing and assignment you do not need yet. Buy one when a second person joins support, or when a thread slips and a customer has to chase you. Q: When should a startup open a support forum? A: Open it when the same ten questions have arrived twice each. Before that you have nothing to seed it with, and an empty forum looks abandoned. Ten to twenty solved threads is enough to go live. Q: How should an early-stage startup handle customer support? A: Use one address for everything, answer within a day, and keep a tally of the questions you answer twice. After two weeks, publish that tally as public answers and send repeat askers the link. That system holds until two people are answering support. Q: How much time does support take for a one-person team? A: It varies by product, so measure your own for two weeks. Count the hours, then count how many of them went to questions you had answered before. That second number is the part publishing answers can give back to you. Q: What support tools should a startup skip? A: Skip live chat until someone is reliably online, saved replies until you send the same answer daily, and a status page until your second outage. Skip the chatbot at this size. Each one adds a promise you then have to keep. --- This blog is powered by Superblog. Visit https://superblog.ai to know more. ---