# How to Handle Support as a Solo Founder Without Losing Your Build Time > How to handle support as a solo founder: batch windows, a priority matrix, templates, docs and lean tools like Crisp and Help Scout. - Canonical: https://zeroraised.com/blog/how-to-handle-support-as-a-solo-founder - Published: 2026-11-06T13:36:21Z - Author: ZeroRaised Team (https://zeroraised.com/blog/authors/zeroraised) - Publisher: ZeroRaised (https://zeroraised.com/) - Section: Growth - Tags: customer-support, solo-founder, operations, bootstrapping To handle support as a solo founder, answer messages in two or three fixed windows a day rather than all day, and sort each one with a simple priority matrix so outages and billing problems always come first. Turn any question you answer twice into a saved reply, and any reply you keep sending into a help doc. Start on a free shared inbox, protect your build hours on the calendar, and hire help only when support still overflows after all of that. This guide sets out that system step by step. Tool prices come from the vendors' own pricing pages, checked on 6 Nov 2026. The process advice is ours. ## TL;DR - **Batch, do not hover.** Pick fixed support windows, publish a reply time and close the inbox outside those windows. - **Triage with a matrix.** Rank every message by how many customers it affects and whether money or data is at risk. Outages and billing jump the queue. - **Write once, reuse forever.** Two identical answers make a saved reply. Repeated saved replies make a help doc. Repeated docs point to a product fix. - **Start at $0.** Crisp Free gives 2 seats with chat and a shared inbox ([Crisp](https://crisp.chat/en/pricing/)). Help Scout Free gives 5 users, 1 inbox and 1 Docs site ([Help Scout](https://www.helpscout.com/pricing/)). - **Hire last.** Fix the causes of tickets first, then bring in part-time help when revenue supports it. **Disclosure:** ZeroRaised publishes this guide and is a launch site for bootstrapped products. Prices and plan limits come from the linked vendor pages as checked on 6 Nov 2026. ZeroRaised has no commercial relationship with Crisp or Help Scout. **Solo founder support** means one person handling every customer question, bug report and billing issue alongside building, marketing and selling the product, without a dedicated support team. ## Why support is different when you are on your own In a company with a support team, a ticket waits in a queue someone else owns. When you are the whole company, every message competes directly with the code you were about to write. That has two consequences. First, support is your best source of product truth. Early customers tell you exactly where the product confuses them, breaks or falls short. If you are still winning your [first 10 paying customers](https://zeroraised.com/blog/how-to-get-your-first-10-paying-customers), those conversations are part of selling, and fast, personal replies are one of the few advantages you have over larger competitors. Second, support has no natural ceiling. Each new customer adds questions, and without a system you end up checking the inbox between every commit. The aim of this guide is to keep the first benefit and cap the second. ## Step 1: Set support windows and batch your replies The single biggest change most solo founders can make is to stop answering support in real time. Context switching costs more than the replies themselves. **How to set it up:** 1. **Pick two or three windows a day.** For example, one in the morning after you check for anything urgent, and one late in the afternoon after your main build block. Put them on your calendar as recurring events. 2. **Publish a reply time.** Write it in your auto-reply, contact page and footer: "We reply within one business day, usually sooner." Only promise what you can keep on a bad week. 3. **Turn off notifications outside the windows.** Keep one exception: alerts for outages and payment failures, which should come from your monitoring and billing tools, not from the support inbox. 4. **Work the inbox to zero in each window.** Zero does not mean every issue is solved. It means every message has a reply, a label and a next step. ## Step 2: Triage with a priority matrix Batching only works if the right things still get handled first. A two-axis matrix gives you a quick, consistent order every time you open the inbox. **Axis one: impact.** Does this affect everyone, several customers or one? **Axis two: risk.** Is money, data or access at risk, or is it an inconvenience? | Priority | What it looks like | Response | |---|---|---| | P1: urgent | Outage, data loss, security issue, customers charged incorrectly | Break the batch rule. Acknowledge now, fix now, post a status update. | | P2: high | Bug blocking one paying customer, failed payment, refund request, cannot log in | First thing in the next window. Fix or work around the same day if you can. | | P3: normal | How-to questions, minor bugs with a workaround, account changes | Answer in the normal window with a saved reply or doc link. | | P4: low | Feature requests, feedback, "nice to have" ideas | Thank them, log the request with the customer's name, reply when it ships. | A few rules that keep the matrix honest: - **Billing is always at least P2.** A customer who has been charged wrongly or cannot pay is either about to churn or about to complain publicly. Neither waits. - **Paying customers beat trial users, and trial users beat cold enquiries,** unless the cold enquiry is a sales lead you are actively chasing. - **Count, do not just answer.** Tag every message with a category (billing, bug, how-to, feature). After a month, the tags tell you which product fixes would remove the most support. ## Step 3: Turn repeat questions into templates The second time you type the same answer, stop and save it. Both Crisp and Help Scout support saved replies or shortcuts, and even a plain text file works at the start. **What makes a good saved reply:** - **Opens with the customer's name and one line specific to them.** A template should not read like one. Edit the first sentence every time. - **Answers the question in the first two lines,** then gives steps or a link. - **Ends with a clear next step:** "Reply here if that does not work and I will look at your account directly." - **Stays short.** If a reply needs screenshots and ten steps, it belongs in a help doc instead. **Templates worth writing in your first month:** - Password reset and login problems - How to cancel, and how refunds work - How to change plan or update a card - Invoice and receipt requests - "Is X on the roadmap?" (thank them, explain how you prioritise, promise to tell them if it ships) - Bug report acknowledgement (what you need from them, when they will hear back) Keep the templates in your support tool so you can insert them with a shortcut. Review them every few weeks; a stale template that describes an old screen creates a second ticket. ## Step 4: Turn repeated templates into docs Templates speed up answers. Docs stop the questions arriving. Use a simple rule of thumb: any template you send three times a week, or any answer that needs screenshots, becomes a help article. **How to build a help center without a big project:** 1. **Start with the top five tags.** Your tag counts from Step 2 tell you which articles will save the most time. 2. **Write each article as the answer to one question,** with the question as the title. "How do I cancel my subscription?" beats "Billing settings overview." 3. **Link docs from inside the product,** next to the feature they explain, and from your auto-reply. 4. **Reply with the doc link plus one personal line** rather than pasting the whole article. Customers learn where answers live. 5. **Update the doc in the same session you change the feature.** Make it part of your definition of done. Help Scout's Free plan includes 1 Docs site ([Help Scout](https://www.helpscout.com/pricing/)). Crisp includes a knowledge base from its Essentials plan ([Crisp](https://crisp.chat/en/pricing/)). You can also start with pages on your own site and move them later. Docs also do quiet marketing work. Clear answers to "how do I…" questions can show up in search, which ties support into the content habits covered in our guide on [how to bootstrap a SaaS](https://zeroraised.com/blog/how-to-bootstrap-a-saas). Before volume spikes at launch, fold support prep into your [product launch checklist for bootstrapped makers](https://zeroraised.com/blog/product-launch-checklist-for-bootstrapped-makers) so templates and a help page exist before strangers arrive. **The final step is a product fix.** If a doc still gets linked several times a week, the feature is confusing. Fixing the screen removes the question entirely, which beats any template. ## Step 5: Pick a support tool (Crisp or Help Scout) You do not need a paid helpdesk to start. A shared inbox with saved replies, tags and a contact form covers most solo founders for a long time. Two tools have useful free plans. ### Crisp - **Free:** $0, 2 seats, website chat widget, shared inbox, contact form, mobile apps. - **Mini:** $45 a month per workspace, 4 seats, adds a shared email inbox, shortcuts, chat triggers and a custom email domain. Crisp charges per workspace rather than per user, and offers a 14-day trial of any plan ([Crisp](https://crisp.chat/en/pricing/)). It suits founders who want live chat on their site. ### Help Scout - **Free:** $0, 5 users, 1 inbox, 1 Docs site. - **Standard:** $25 per user a month, adds multiple inboxes, live chat and SMS, knowledge bases and an AI inbox assistant. Help Scout charges per user ([Help Scout](https://www.helpscout.com/pricing/)). It suits founders who prefer email-first support and want a docs site from day one. **Which to choose:** if live chat is central to how you sell, start with Crisp Free. If your customers mostly email and you want docs built in, start with Help Scout Free. Either way, stay on the free plan until you hit a specific limit you can name. **On live chat:** chat creates an expectation of instant replies. If you add it, show your hours in the widget and let messages fall back to email when you are offline, so chat does not quietly undo your support windows. ## Step 6: Protect your build time Support systems fail when build time is the thing that gives way. Defend it as deliberately as you would a customer meeting. - **Block your deep work first.** Put a long build block on the calendar before the support windows, and treat it as fixed. - **Keep urgent alerts separate from the inbox.** Uptime monitoring and payment failure alerts should reach you directly. Then you can close the support inbox during build time without worrying you will miss an outage. - **Batch bug fixes too.** Unless a bug is P1 or P2, log it and fix it in a planned slot rather than mid-reply. - **Set a weekly support review.** Spend a short session looking at tag counts, the slowest tickets and the docs that got linked most. Choose one product fix that will cut tickets next week. - **Watch for scope creep in replies.** "Could you also build…" requests are P4. Log them with the customer's name and move on. If you are still working a day job while building, these boundaries matter even more, because support otherwise takes the only build hours you have. ## Step 7: Know when to hire help Hiring is the last step, not the first. A new person inherits your mess unless you have already built the templates, docs and triage rules. **Signs it is time:** - Support regularly overflows its windows even after templates and docs are in place. - Your weekly review keeps finding the same causes, and you never get time to fix them. - Response times are slipping past the promise you publish. - Revenue can cover a part-time contractor without putting your runway at risk. **How to hire without losing control:** 1. **Start part-time and scoped.** First-line replies using your templates, plus writing and updating docs, is a clean starting brief. 2. **Keep billing, refunds and escalations yourself** at first. These carry the most risk and teach you the most. 3. **Hand over your triage matrix and tag list on day one.** It is your support policy in one page. 4. **Read a sample of replies each week** and keep doing your weekly review. ## A weekly support routine you can copy | When | What | |---|---| | Each morning | Check alerts. Handle any P1. Work the inbox to zero, P2 first. | | Main work block | Build. Inbox closed, notifications off. | | Late afternoon | Second support window. Reply, tag, log feature requests. | | Weekly | Review tag counts. Write or update one doc. Pick one product fix that removes a ticket type. | | Monthly | Refresh templates. Check you are meeting your published reply time. Reassess whether the free plan still fits. | ## Frequently asked questions ### How much time should a solo founder spend on support? There is no standard number. Set fixed support windows, track how long they take each week, and treat a steady rise as a signal to improve docs, fix the product issue causing the questions, or eventually hire. The goal is that support has a box on your calendar and stays inside it. ### Do I need live chat as a solo founder? Not necessarily. Live chat sets an expectation of instant answers that one person cannot always meet. Many solo founders do better with email or a contact form plus a stated reply time. If you do add chat, show your hours and let messages fall back to email when you are offline. ### What is the best free support tool for a solo founder? Crisp Free and Help Scout Free are both reasonable starting points. On 6 Nov 2026, Crisp Free included 2 seats, a website chat widget, a shared inbox, a contact form and mobile apps. Help Scout Free included 5 users, 1 inbox and 1 Docs site, which is useful if you want a help center from day one. ### How fast should a solo founder reply to support emails? Fast enough to meet the reply time you publish, and faster for urgent issues such as outages or billing errors. A promise you keep, such as a reply within one business day, builds more trust than an instant reply some days and silence on others. ### When should a solo founder hire someone for support? When support keeps overflowing its windows after you have added templates, written docs for repeat questions and fixed the product issues behind them, and when revenue can cover the cost. Start with a part-time contractor on a defined scope, such as first-line replies and docs, while you keep billing and escalations. ## Where ZeroRaised fits ZeroRaised is a launch directory for products built without institutional VC or accelerator equity. Once your support system can handle new users, you can [submit your product](https://zeroraised.com/submit) for free. For more practical guides on running a product without investors, [join the ZeroRaised newsletter](https://zeroraised.com/newsletter). A listing is one small launch among many. We do not promise traffic, sign-ups or revenue. ## Sources - [Crisp pricing](https://crisp.chat/en/pricing/), last checked 6 Nov 2026 - [Help Scout pricing](https://www.helpscout.com/pricing/), last checked 6 Nov 2026 ## Frequently asked questions ### How much time should a solo founder spend on support? There is no standard number. Set fixed support windows, track how long they take each week, and treat a steady rise as a signal to improve docs, fix the product issue causing the questions, or eventually hire. The goal is that support has a box on your calendar and stays inside it. ### Do I need live chat as a solo founder? Not necessarily. Live chat sets an expectation of instant answers that one person cannot always meet. Many solo founders do better with email or a contact form plus a stated reply time. If you do add chat, show your hours and let messages fall back to email when you are offline. ### What is the best free support tool for a solo founder? Crisp Free and Help Scout Free are both reasonable starting points. On 6 Nov 2026, Crisp Free included 2 seats, a website chat widget, a shared inbox, a contact form and mobile apps. Help Scout Free included 5 users, 1 inbox and 1 Docs site, which is useful if you want a help center from day one. ### How fast should a solo founder reply to support emails? Fast enough to meet the reply time you publish, and faster for urgent issues such as outages or billing errors. A promise you keep, such as a reply within one business day, builds more trust than an instant reply some days and silence on others. ### When should a solo founder hire someone for support? When support keeps overflowing its windows after you have added templates, written docs for repeat questions and fixed the product issues behind them, and when revenue can cover the cost. Start with a part-time contractor on a defined scope, such as first-line replies and docs, while you keep billing and escalations.