Can Tallymeter be vibe coded?
Time tracker that turns tracked hours into numbered client invoices, with a REST API and MCP server so AI agents can log their own time
The solo core is a contained build and nobody should pretend otherwise: a timer, projects with hourly rates, and uninvoiced hours rolled into a numbered PDF. What survives the rebuild is the boring half · two-way Jira worklog sync that reconciles ticket by ticket without double-counting, a hosted MCP server and scoped API tokens your agents can reach from any machine, and invoice numbering plus VAT and bank details that hold up when an accountant reads them. Full disclosure: this entry was submitted by the person who builds Tallymeter. Same rubric as everything else on the list, and the honest answer is that a freelancer billing one client can absolutely one-shot the part they use.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Start and stop a timer against a project, fix entry descriptions after the fact, then roll every uninvoiced hour into a sequentially numbered PDF invoice at the project's rate.
- Model a narrow bookkeeping workflow with explicit review and export steps.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- two-way Jira Cloud worklog sync that reconciles ticket by ticket
- a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution
- invoice numbering, VAT and bank details that survive an accountant handoff
- shared team workspaces and per-member unbilled totals
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Why people still pay
The timer is a contained effort. The failure modes are not. Uninvoiced time that silently double-counts against a Jira worklog, an invoice sequence with a gap in it, or a laptop that was asleep when the agent tried to log its hours are all problems you discover on invoice day, in front of a client. A business billing real money for hours generally decides that maintaining the thing that produces its invoices is not the hobby it wants.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Tallymeter
Context
**Tallymeter** — Time tracker that turns tracked hours into numbered client invoices, with a REST API and MCP server so AI agents can log their own time. It currently costs $10/mo.
The solo core is a contained build and nobody should pretend otherwise: a timer, projects with hourly rates, and uninvoiced hours rolled into a numbered PDF. What survives the rebuild is the boring half · two-way Jira worklog sync that reconciles ticket by ticket without double-counting, a hosted MCP server and scoped API tokens your agents can reach from any machine, and invoice numbering plus VAT and bank details that hold up when an accountant reads them. Full disclosure: this entry was submitted by the person who builds Tallymeter. Same rubric as everything else on the list, and the honest answer is that a freelancer billing one client can absolutely one-shot the part they use.
This brief describes a focused, single-operator replacement for the part of Tallymeter that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Start and stop a timer against a project, fix entry descriptions after the fact, then roll every uninvoiced hour into a sequentially numbered PDF invoice at the project's rate.
Model a narrow bookkeeping workflow with explicit review and export steps.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
An always-on box if you want the timer off your laptop.
PDF generation.
Backups you actually test.
Data and integrations
Jira API credentials if you want worklog sync.
Each of these needs a real account, credential, or quota. Set them up before writing feature code.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build me a freelance time tracker that produces invoices, like Tallymeter. Requirements:
Node + Express + better-sqlite3, one process, server-rendered pages on
localhost:4820. No accounts, no telemetry, everything stays on my machine.
Tables: clients, projects (hourly rate, currency), entries, invoices.
One timer, big start/stop button on the index page: starting a new one stops
the running one first, so two can never run at once. Entries store
description, project, started_at and ended_at as ISO-8601 UTC.
Let me edit a finished entry's description in place, and add one after the
fact with a duration in minutes for the call I forgot to track. Entries
already on an invoice are frozen, reject the edit.
An /unbilled page: finished entries with no invoice_id, grouped by project,
hours shown as "3h 25m" and the money at the project rate.
Invoice a project's unbilled entries: one line per description with decimal
hours, sequential INV-2026-001 numbers that are never reused even if I delete
a draft, bank details and VAT rate from config.json, rendered to
./invoices/INV-2026-001.pdf with puppeteer. Stamp invoice_id on what it billed.
Out of scope: multi-user accounts, payment collection, mobile apps. Skip them.
README: config.json fields, where the PDFs land, and a warning that the
sqlite file is the only copy of my billing history · tell me to back it up.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Two-way Jira Cloud worklog sync that reconciles ticket by ticket.
A hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution.
Invoice numbering, VAT and bank details that survive an accountant handoff.
Shared team workspaces and per-member unbilled totals.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
What you still own after launch
Secure credentials, rotate secrets, and handle provider rate limits.
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Maintain every third-party integration as APIs and OAuth rules change.
Risk
**High consequence.** Use this as a prototype or personal aid. Keep a qualified human and an established provider in the loop for consequential decisions.
Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[kimai](https://github.com/kimai/kimai) — mature self-hosted multi-user time tracking with timesheets, reports and invoices
[solidtime](https://github.com/solidtime-io/solidtime) — modern open-source time tracker, the closest self-host starting point
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/tallymeter
You still own the product
- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.
Open-source prior art
Before you start
Can Tallymeter be vibe coded?
Partly, if you narrow it. The solo core is a contained build and nobody should pretend otherwise: a timer, projects with hourly rates, and uninvoiced hours rolled into a numbered PDF. What survives the rebuild is the boring half · two-way Jira worklog sync that reconciles ticket by ticket without double-counting, a hosted MCP server and scoped API tokens your agents can reach from any machine, and invoice numbering plus VAT and bank details that hold up when an accountant reads them. Full disclosure: this entry was submitted by the person who builds Tallymeter. Same rubric as everything else on the list, and the honest answer is that a freelancer billing one client can absolutely one-shot the part they use.
What can an AI coding agent reproduce from Tallymeter?
Start and stop a timer against a project, fix entry descriptions after the fact, then roll every uninvoiced hour into a sequentially numbered PDF invoice at the project's rate. Model a narrow bookkeeping workflow with explicit review and export steps. A responsive interface with real empty, loading, success, and error states.
What will a DIY Tallymeter replacement still be missing?
two-way Jira Cloud worklog sync that reconciles ticket by ticket; a hosted MCP server and scoped API tokens agents can call from anywhere, with per-agent attribution; invoice numbering, VAT and bank details that survive an accountant handoff; shared team workspaces and per-member unbilled totals; Connectors, OAuth flows, and vendor API changes require constant upkeep.; The last 20 percent is sync, migration fidelity, speed, and edge cases.
What do I still own after building a Tallymeter alternative?
Secure credentials, rotate secrets, and handle provider rate limits. Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss. Maintain every third-party integration as APIs and OAuth rules change.