Munin for solo founders.

A one-person company still has a support desk, a CRM, a knowledge base, a blog, an outreach motion, and an analytics question. It just has them badly. Support is your personal inbox. The CRM is a spreadsheet you last touched in March. The knowledge base is answers you've typed out four times from memory. Nobody is doing these jobs wrong, exactly — there just isn't anyone to do them.

What does Munin give a solo founder?

Six functions on one customer record, and agents to do the paperwork inside them. CRM, support conversations, knowledge base, CMS, outreach, and analytics run on one backend, and you point Claude or ChatGPT at it to handle triage, enrichment, and drafting while you approve the things that matter.

The pitch isn't "more software." It's that the six tools you'd otherwise be paying for separately — and syncing badly — become one thing with one bill and one place customers exist.

Does the free tier actually cover a one-person company?

Usually, yes. Munin Cloud Free is €0/month and includes all six modules and all four channels — email, chat widget, SMS, voice — with 5,000 MCP tool calls per month, 250 contacts, and 100 MB of storage. Nothing is feature-gated: the free tier is the whole product with caps, not a crippled edition.

The caps are the thing to size honestly. 250 contacts is a real early-stage customer list but not a mailing list. 5,000 tool calls is generous for supervised work and tight if you put four agent passes on aggressive schedules. When you outgrow it, Cloud Premium is a flat €99/month per org — not per seat, but it means hiring your second person doesn't change the bill.

Which jobs do the agents actually absorb?

The ones you're currently doing at 11pm or not at all. Each is a markdown skill you can read before you trust it:

Inbound support gets triaged before you open it — the thread is tagged, titled, and linked to a customer record. New signups get enriched from their company site instead of sitting as a bare email address. Questions you've answered once become knowledge-base drafts, so the second person to ask gets a cited answer rather than you retyping it. Recurring themes in conversations turn into drafted blog posts waiting for your edit.

None of that is judgment. All of it is typing, and typing is the part that moved upstream when the cheapest operator stopped being a person. For a solo founder that shift is worth more than it is for a team, because you are the entire bottleneck.

What breaks first?

Your attention, then the caps. In that order.

The review queue is real work. Agents propose merges, outreach drafts, and knowledge articles, and a queue nobody works becomes a queue that quietly stops mattering. Five minutes a day keeps it honest, and five minutes is genuinely the size of it — the passes only file what they couldn't decide on their own, so the queue stays short enough to clear over a coffee.

After that: contacts. 250 goes faster than you'd think once inbound conversations start resolving to real people. Storage is rarely the constraint unless you're loading images into the CMS.

There is also no manager's reporting layer in here — the SLA timers, CSAT surveys, and team dashboards a support org gets measured on are not among the things Munin ships. For a company of one that is mostly beside the point, because you already know how your week went without a chart to confirm it. What you get instead is the thing a dashboard can't hand you: six functions on one record, so when you ask what happened with a customer, the answer is a single lookup rather than four tabs and a guess. Every conversation, contact field, article, and campaign touching that person is in the same place, which is the version of reporting a company of one actually runs on.

Where should a solo founder start?

One channel and ten documents. Set up email or the chat widget, write the ten questions you're most tired of answering into the knowledge base, and put a single agent pass on triage. That's an afternoon, and it's enough to tell you whether the shape suits you.

Don't import a 5,000-row contact list on day one, don't turn on four passes at once, and don't self-host. Add the second pass when the first one has been right for a fortnight.

Who should not use Munin?

Three kinds of solo founder, and the criteria are concrete. If you don't want to think about AI agents at all, most of what makes Munin useful is capability you won't collect — a shared inbox and a spreadsheet is a perfectly good stack for a company of one, and it needs no supervision. If a polished sales UI is your priority, take Twenty, which is built for that and is AGPL rather than MIT if the licence matters to you. If your support lives on WhatsApp and Instagram, Chatwoot has native channels for both; Munin's four are email, chat widget, SMS, and voice. And if you're selling into enterprises that ask for SLA reporting in the contract, buy something that ships SLA reporting.

What's left once you've ruled those out is a fairly specific person, and it's the person the whole product is shaped around: one founder, a real customer list, and six jobs that all touch the same people. For them the arithmetic is unusual — one record instead of six systems, one bill instead of six, and agents doing the typing between them. That's why the free tier is the whole product rather than a teaser. An afternoon is enough to find out whether the shape fits, and it costs nothing to find out.

Frequently asked questions

Is Munin free for a one-person company? Yes. Munin Cloud Free is €0/month with all six modules and all four channels, capped at 5,000 MCP tool calls, 250 contacts, and 100 MB storage. Self-hosting is free forever under MIT with no caps at all — you pay in hosting and maintenance instead.

What's the cheapest CRM and helpdesk combination for a solo founder? Running both in one system rather than paying two vendors. Munin's free tier covers CRM, support conversations, knowledge base, CMS, outreach, and analytics together, which is usually cheaper than a free CRM plus a free helpdesk plus the work of syncing them.

Do I need to know how to code? Not for Munin Cloud. You do need to be comfortable pointing an MCP client like Claude or ChatGPT at it, and reading a markdown skill to see what an agent will do before you trust it — which is closer to reading a recipe than to programming. Self-hosting is the part that needs comfort with Docker.

How much supervision do the agents need? A few minutes a day on the review queue. Cheap reversible actions like tagging and enrichment apply automatically; anything irreversible — merging contacts, publishing a knowledge article — waits for you. An unworked queue is the main way this arrangement fails.

Should a solo founder self-host or use the cloud? Cloud, almost always. Self-hosting adds backups, upgrades, and on-call to a workload that's already one person. The code is identical either way, so start hosted and move later if you want to.

What happens if I outgrow the free tier? Cloud Premium is a flat €99/month per org with metered overage rather than hard cliffs — 200,000 MCP calls, 25,000 contacts, 10 GB. It's per organisation, not per seat, so adding your first hire doesn't change the price.

It takes an afternoon to try, it costs nothing, and every module exports cleanly if you ever decide to leave. Start on Munin Cloud, or read the agent recipes first.

One person can't run six departments. One person and six agents can.