CRM Solo: a CRM for a one-person web agency, built to work with AI agents
Clients, retainers, tasks, time, leads and the monthly close in one app. My agents use it through an MCP server and a CLI, and every write lands in the web UI at once.
CRM Solo
- Product
- CRM Solo, my own product
- Role
- Product, design and development
- Started
- November 2022
- Demo
- demo.crm-solo.com ↗
- Stack
- Laravel 12, PHP 8.4, Inertia, React 19, TypeScript, MariaDB, Valkey, Horizon, Reverb
- Languages
- English and Polish
- Commits 1,417
- Tools for AI agents (MCP) 54
- Interface languages 2
- In development since 2022
Counted in the repository on 14 November 2026.
The problem
A one-person web agency carries the admin of a bigger one: retainers, hours, monthly reports, invoices and leads. CRM Solo keeps all of it in one place, down to the monthly close for every maintained site.
It does not run agents itself. My own agents connect through an MCP server and a CLI. They read a client’s state and a task’s brief, start timers, log time and write back what they did.
Screen by screen
Today
The day plan. Suggestions come first with deadlines on top, and the helper explains why each task is there. At most five picks a day.
Month close
Each maintained site is pulled, updated, verified and reported once a month. The month card shows which days are already closed.
Agents work in it too
The same verbs the web UI uses, as a CLI and an MCP server. An agent can plan the day, time a task and close it, and I see it in the app right away.
# what is on today, as JSON for an agent
crm today --json
# time a task from the terminal
crm timer-start "contact form"
crm timer-stop
# close it, recurrence included
crm task-done 412 Example commands with made-up task names. App screens are from the component library with demo data.
How it is built
-
Laravel and Inertia
Laravel 12 on PHP 8.4, Inertia with React 19 and TypeScript, MariaDB and Valkey. FrankenPHP and Octane serve production.
-
An MCP server and a CLI
Claude Code, Codex or a chat client work through the same verbs. Every write shows up in the web UI at once.
-
Registries, not conditionals
Task sources, report writers and AI providers each resolve through a registry, so a new one is a class, not a branch.
-
English and Polish
The interface ships in both languages. The report prompt and the lead funnel are configuration, not code.
Next project
