# Why I Built Mahaam: Open Source Project Management for Agencies

> Projects, time sheets and invoices lived in three tools that never agreed. Why I built Mahaam, open source project management for agencies, on ToGO.

*2026-10-19T12:49:03Z*

# Why I Built Mahaam: Open Source Project Management for Agencies

I run a software studio. For years our projects, time sheets and invoices lived in three different tools that never agreed with each other. Mahaam is the one place I built to fix that, and I built it as open source project management for agencies like ours.

![Why I built Mahaam](https://fadymondy.com/uploads/sites/3b93f650-28ec-4093-99aa-e7b16c2a2e2f/media/why-i-built-mahaam-en.png)

## The problem I had

Hours were tracked in one place, budgets lived in another and the invoice was typed from memory and a spreadsheet. Every handover between those tools was a place for a number to go wrong. I wanted hours tracked against a project budget, and the invoice drafted from the same entries, so nothing is retyped.

## What I built

Projects, issues, time tracking and invoices share one dataset. A few choices matter more than the feature list:

- **Clients get a portal.** They see what you choose to show: their projects, their issues and their invoices, without taking a staff seat.
- **A feedback widget for client sites.** One script tag, and bug reports with screenshots and diagnostics land on the right project's board.
- **Arabic and English**, right-to-left included.
- **An MCP server.** Claude Code can pick up an issue, work it and report back on the board, under the same permission checks as a person.

## The first week

The repository starts on 2026-09-14. The first commit already had tenancy, Postgres row-level security, the user and admin MCP servers and the feedback intake. The project was still called Managy then. By the end of that day it had the schema for clients, projects and tasks, a kanban board and the first version of time entries with database-enforced invariants.

I did not plan to add MCP late. The domain layer in `internal/work` serves both the REST API and the MCP tools, so an agent and a browser go through one authorization path. That is a design choice, and its effect is that I do not maintain two sets of rules.

## Why ToGO

Mahaam is built on [ToGO](https://github.com/togo-framework/togo), the Go framework I also work on. I wanted the boring parts, such as mail, queue, scheduler and storage, to arrive as plugins. ToGO did not give me multi-tenancy, so I built that myself with Postgres row-level security. The [case study](https://to-go.dev/en/blog/mahaam-togo-case-study) has the code, the numbers and the places where the framework got in the way.

## What is not done

I do not have usage numbers, customer quotes or benchmarks to show, so I am not showing any. The repository is public under AGPL-3.0 and the README lists the framework notes I collected while building it. Some of them may be fixed in newer ToGO releases.

## FAQ

**Who is Mahaam for?** Agencies, studios and freelancers who bill by the hour or by the project.

**Is it open source?** Yes, AGPL-3.0, at [github.com/fadymondy/mahaam](https://github.com/fadymondy/mahaam).

**How can an AI agent use it?** Through the MCP endpoint with a scoped token. See the [product article](https://mahaam.app/en/blog/project-management-mcp-server-for-ai-agents).

## What I would like from you

Tell me what would make you move your time tracking over, and what is missing from the invoice flow. Open an issue on GitHub or find me on [Discord](https://discord.gg/a59RzxnB2H).

## Next steps

- Product article: [A project management MCP server for AI agents](https://mahaam.app/en/blog/project-management-mcp-server-for-ai-agents)
- Case study: [How Mahaam is built on ToGO](https://to-go.dev/en/blog/mahaam-togo-case-study)
- [mahaam.app](https://mahaam.app) · [GitHub](https://github.com/fadymondy/mahaam) · [Product Hunt](https://www.producthunt.com/products/mahaam)

---

Source: https://fadymondy.com/en/blog/why-i-built-mahaam
