Harvest

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Build me billable time tracking that replaces Harvest: timers against projects, budgets that warn before they are blown, and invoices out of the hours.

STACK
- Node 20+ with Fastify, server-rendered HTML with a little vanilla JS
- SQLite through better-sqlite3, WAL mode
- Caddy in front

THE DATA MODEL
- clients: id, name, address, currency, payment_terms_days, archived_at
- projects: id, client_id, name, code, billing_kind, budget_kind, budget_amount_cents, budget_hours, budget_is_recurring, notify_at_percent, starts_on, ends_on, archived_at
- tasks: id, name, is_billable_default, default_rate_cents
- project_tasks: project_id, task_id, is_billable, hourly_cents
- rates: id, scope, scope_id, user_id, hourly_cents, currency, effective_from — an entry bills at the rate in force when the work happened, always
- entries: id, user_id, project_id, task_id, notes, started_at, ended_at, duration_seconds, is_billable, is_locked, invoice_id, expense_id, source, created_at
- entry_revisions: id, entry_id, field, old_value, new_value, changed_by, at — append-only
- expenses: id, project_id, user_id, category, amount_cents, currency, incurred_on, receipt_path, is_billable, markup_percent, invoice_id
- invoices, invoice_lines, payments, and a per-year number sequence
- Every instant UTC, every amount integer cents with a currency

BILLING KINDS, WHICH DECIDE EVERYTHING ELSE
- Hourly by person, hourly by task, hourly by project, or a fixed fee
- A fixed-fee project still tracks hours, because the hours are how you learn whether the fee was right. The report shows the effective hourly rate afterwards, which is the most useful number a small studio ever sees
- Non-billable projects exist and are tracked, because internal time is where the margin actually goes

TIME
- An entry is two instants; the duration is derived. Never store a duration alone or a day with a clock change will not reconcile
- One running timer per person, enforced with a partial unique index
- A timer that has run past a threshold is flagged and offered for trimming to the last activity, never trimmed silently
- Weekly timesheet grid alongside the timer, both writing the same rows
- Rounding is a report setting, never a stored change: the raw seconds are kept and rounding is applied when billing. A tracker that rounds on save has destroyed the evidence

BUDGETS AND ALERTS
- Hours or money, one-off or recurring monthly, per project
- Progress visible on every screen where the project appears, not only in a report
- Alerts to the project's manager at configurable percentages, once per threshold per period
- A projection: at the current burn, the budget is exhausted on this date. That warning is the difference between a conversation and an invoice nobody expected
- Over-budget hours still tracked, marked, and reported separately

EXPENSES
- Category, amount, date, receipt photo, billable or not, with an optional markup
- Receipts stored by hash, EXIF stripped, and shown on the invoice as a line
- Expenses in a currency other than the project's are converted at a recorded rate on a recorded date, and both are stored

INVOICING
- Select unbilled, unlocked, billable entries and expenses for a period and generate an invoice from them
- Lines grouped by person, by task or by project, chosen per invoice
- Numbering from a sequence table, per year, allocated inside the transaction that issues the invoice. Gapless, because in most countries that is a legal requirement rather than a preference
- An issued invoice is immutable: a correction is a credit note that references it
- The PDF generated once at issue and stored with its hash
- Marking entries invoiced with the invoice id, so nothing bills twice, ever
- Payments recorded against invoices with the balance derived, and status never typed

REPORTS
- Hours and amounts grouped by client, project, task, person or week, filterable by all of them
- Cost rate against billable rate gives margin, per project and per person
- Uninvoiced work, which is the report that finds the money you forgot to bill
- Everything computed from rows at query time. No stored totals

APPROVAL AND LOCKING
- Submit a period, a reviewer approves, and approved periods lock
- A locked entry cannot be edited without an explicit unlock, which is logged
- Invoiced entries are locked permanently

OPERATIONS
- .env: DATABASE_PATH, STORAGE_PATH, BASE_URL, SESSION_SECRET, SMTP_URL
- Migrations on boot, each once
- Nightly backup off the machine, restore script
- Health endpoint

WHAT MATTERS MOST
The invoice transaction and rates with effective dates. Build gapless numbering and the mark-as-invoiced inside one transaction, then try to double-bill an entry from two browsers at once. Hours are what you get paid for, and the two ways to lose money here are billing twice and not billing at all.

Give me the repository, migrations, .env.example, a seed agency with three clients and a month of work, and a README with deploy steps behind Caddy and a note to check the invoice numbering rules locally.