You are the product person, the marketer, the support desk and the finance team. Brief your AI Chief of Staff on one of those jobs and it builds a team for it. The work comes back as drafts for you to check.
Free and open source. macOS, Windows and Ubuntu.
An example view. The teams are real, from the library. None of them is running yet.
Teams
Everything is your job. Every hour on the inbox or the investor update is an hour off the product.
The follow-ups you meant to send. Leads from last month’s calls, still waiting on a note from you.
One chat, one answer. A good chat answer still leaves you to split the job up, chase each piece and put it together.
Hand this off first: research
“Should we sell to dental practices? Who would we be up against, what do they charge? One page, with sources. Include a reviewer who checks the sources and marks unsupported claims.”
Still yours: the go or no-go call. Anything the team wants to send or spend waits for you on Ask.
The jobs to hand off first. Each one ends with a draft or a question for you.
From Murage’s team library. Look inside any team before you import it, then export it once and share it with your staff.
Founder Setup
Organize formation questions, financial planning, brand positioning, and operating processes into a practical setup plan.
Validate Before Build
Turn your hypothesis into customer-research questions and an offer test with clear evidence to seek.
SaaS MVP Sprint
Get an MVP specification, validation plan, landing-page copy, and visual direction.
First Customers
Sharpen your target audience, prepare outreach and sales copy, and choose practical channels for initial conversations.
Product Launch
Coordinate audience research, positioning, launch copy, channels, and sales preparation into one launch plan.
Fundraise
Develop your pitch deck, financial model, and investor narrative so the numbers and story support each other.
Why it fits this work
The Validate Before Build team turns your idea into customer-research questions and an offer test, with the evidence to look for, before you write a line of code.
Claude Code, Codex, Hermes and more, each bot on the engine that suits its job. Keep the one you use; Murage puts them on one team, you can switch any bot’s engine later, and the app is free.
Murage is free and open source. Your bots run on the AI plan you already pay for, and a busy team uses its allowance faster. Connected apps and voice use optional Flux Router credits or your own keys.
New bots start on Ask. On Full access, a bot stops before messaging anyone new, posting publicly, paying, or deleting outside its folder, unless you have allowed it for that task. Replies in an existing conversation go ahead on Auto and Full access. No limits turns the stop line off. On Hermes and other ACP engines, Ask and the stop line cover only what the engine asks Murage about: shell commands and file edits.
Memory, files and conversations are stored on your computer, not on our servers. The AI and apps you connect receive what each job needs.
Yes. The app is free and open source. You pay your AI provider for usage. Flux Router, Ferrox Labs’ optional credit-billed service for models, connected apps, voice, images and web search, is only needed if you choose it; your own keys work instead.
Yes, each person on their own computer. Build the team once, export it, and every co-founder or first hire imports the same bots, skills and routines. Logins never travel with it. Each person can message their Chief from Slack, Discord or Telegram, and bots can post drafts to your team’s Slack channels through connected apps, with your approval and up to five labeled accounts per app. Shared, always-on workspaces come with Murage Cloud, which isn’t open yet.
Download the free app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
