Project and task management decision
Tallymeter
A competent developer can reimplement the core track→report→invoice loop and a REST API in ~30 hours and run it for a small team; Tallymeter's durable value (MCP server, integrations, hosted polish) is not a strong technical moat shown in the pages.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.
What a replacement has to do
- Start/stop a timer → store time entries by project → compute date-range reports/totals → render numbered PDF invoices
What it still won’t have
- Native MCP (Streamable HTTP) server and built agent tooling
- Built-in two-way Jira worklog sync
- Per-agent attribution and token-scoped auth tailored for AI fleets
- Polish, reliability, and UX refinements of a shipped product (mobile/responsive edge cases)
- Hosted uptime, backups, and legal/privacy guarantees
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 3 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted time-tracking + invoicing service in Node.js (Express) + Postgres + React. In-scope: REST API (GET /timer, POST /timer/start, POST /timer/stop, GET /projects, entries CRUD), single-user auth (token-based), simple React tracker UI with one-click start/stop and project selection, CSV date-range report endpoint, numbered PDF invoice generation from a report, idempotent timer behaviour (only one running timer), and CSV/PDF export. Out of scope: two-way Jira sync, MCP server protocol, multi-tenant billing, and agent-specific features. Include input validation, error handling, unit tests for API endpoints, containerized deployment (Docker), and a README with setup and migration steps.
How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- Evidence score89
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productTallymeter — homepage
- official docsTallymeter API docs
- open sourcefrappe/erpnext
- open sourceopf/openproject
Integrity checks
What held up, and what did not.
