Indie founders rarely run one thing. You have the SaaS that pays the bills, the little tool you launched last month, a client site or two, and that side project you swear you will finish this quarter. Each one has users, and users have questions. The problem shows up the moment you try to support all of them: most support tools price per project or per seat, so every new thing you ship quietly raises your monthly bill and adds yet another inbox to babysit.
It does not have to work that way. This guide walks through putting every project you run into one shared inbox at one flat price, where each project keeps its own chat widget and its own look, but all the conversations land in the same place. You add a site, paste one line of code, and you are done. No per-project upgrade, no per-seat math, no five browser tabs open just to answer support.
Why per-project and per-seat pricing punishes people who ship a lot
The pain is structural, not a one-off annoyance. When a support tool charges per workspace or per project, shipping is taxed. Launch a fourth project and your support cost goes up before that project has earned a single dollar. So you do the thing nobody should have to do: you skip real support on the small projects, paste an email address on a contact page, and hope.
Per-seat pricing has the same shape from a different angle. You are a team of one or two, but the second you want a contractor to cover replies for a week, you are paying for a full seat. The tooling assumes a big support team. You are not a big support team. You are a person with a lot of tabs.
- →Every new project is a new subscription line, or a new tier you have to upgrade into.
- →Conversations are scattered across separate accounts, so you log in and out all day.
- →Notifications come from five different places and you miss the one that mattered.
- →You quietly decide some projects are not worth supporting properly, which is a strange way to treat your own users.
How one inbox across many projects actually works in muro
Your login lives in a workspace. Inside that one workspace you create a site for each project: your SaaS, your side tool, each client. Every site gets a distinct widget_id, which is how muro knows which project a message came from. The widgets are separate on the outside, but on the inside they all feed a single inbox, so you triage everything from one screen instead of one login per project.
Because the boundary is the site and not the seat, inviting a teammate or a contractor to help out does not change your bill. They join the same workspace and see the same inbox, filtered however they like. The thing that decides your price is how many projects you run, and on Fleet that number is simply unlimited. See the flat pricing for the exact plans, or open the live demo to watch a multi-project inbox in action before you sign up.
Step 1: add a site for each project
After you start free, you land in onboarding for your first site. To add the rest, open Sites at /app/sites. You will see every project as a card with its domain and favicon. Click to add a new one, give it a name and its domain, and muro generates a fresh widget for it. Repeat for as many projects as you have. There is no per-site charge to do this on Fleet, so add the tiny weekend project too. It deserves real support as much as the flagship.
Step 2: install the widget on each project
Every site has its own install snippet with its own widgetId baked in. Open a site from /app/sites, copy its snippet, and paste it just before the closing </head> tag on that project. Here is the shape of it. Replace YOUR_WIDGET_ID with the id shown for that specific site (each project has a different one, so do not reuse a single id across projects):
html<script>
(function(w,d,s,o){
w.MuroChat=o;w[o]=w[o]||function(){(w[o].q=w[o].q||[]).push(arguments)};
var j=d.createElement(s);j.async=1;j.src='https://muro.chat/widget.js';
d.getElementsByTagName('head')[0].appendChild(j);
})(window,document,'script','muro');
muro('init',{widgetId:'YOUR_WIDGET_ID'});
</script>The widget is about 6 KB and loads async, so it will not slow any of your sites down. Once a page reloads, muro detects the ping and marks that site as installed. Do this once per project and every one of them is now wired into the same inbox. The same single line works on any stack: a static landing page, a framework app, a no-code builder, or a client's CMS.
Step 3: give each project its own branding
One inbox does not mean one identical-looking widget. Open any site at /app/sites and you can set per-project branding so the chat matches that product, not a generic house style:
- →Theme color, so the launcher and bubbles match each project's palette.
- →Agent name, so your fintech tool can answer as a different persona than your indie game.
- →Agent avatar, uploaded per site, so the face in the chat fits the brand.
Step 4: live in one inbox, switch by project when you need to
Day to day you work from a single inbox that shows conversations from every project at once, which is exactly what you want when you are context-switching anyway. When you need to focus, filter to one site and the noise from the others disappears. Each conversation is tagged with the project it came from, so you always know whether this is a flagship customer or someone poking at the weekend build. One screen, every project, no logging in and out.
Where the AI fits across many projects
The AI agent answers from each project's own docs and hands off to you when it is unsure, so a question about your SaaS does not get answered with your side tool's help articles. On managed AI you share one monthly credit pool across all your projects, which is simple and predictable. If a particular project gets busy, you can paste a separate LLM key for it so the AI there runs unlimited at zero markup. That is the bring your own AI key wedge, and it matters more the more projects you run, because per-resolution billing across a whole portfolio is exactly why AI support gets expensive.
If you are doing this for clients rather than your own portfolio, there is a sibling playbook on how to support multiple clients without sharing AI credits that goes deeper on the per-client key setup and isolation boundaries.
Running many projects should make you feel productive, not punished. One shared inbox, one flat price, a separate widget and branding per project, and an AI that answers from the right docs is the setup that holds up as your list of things grows. Start free with no card, add your first two or three sites this afternoon, and see flat pricing for when your portfolio outgrows Solo and Fleet's unlimited projects starts paying for itself.