Project and task management decision
Harvest
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Harvest, track project time, turn approved entries into simple invoices, and export reports. The hard boundary is team timesheets, integrations, invoicing, reminders, support, and reliability, plus ubiquitous capture, coaching, and team workflow.
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
- Track project time and focused sessions, turn approved entries into simple invoices, review patterns locally, and export reports and a transparent activity record.
What it still won’t have
- team timesheets, integrations, invoicing, reminders, support, and reliability
- cross-device history
- team timesheets and payroll
- behavioral datasets
- blocking across every platform
What remains hard
- Execution quality
- Team collaboration
- Integration maintenance
First-year cost
The build hours below are a category default, not an estimate for this product. Change them to your own numbers and the comparison follows.
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
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 personal replacement for Harvest in an empty repository. Use Tauri 2, React, TypeScript, SQLite, and optional OS accessibility APIs; do not offer alternative stacks. The core loop is: track project time and focused sessions, turn approved entries into simple invoices, review patterns locally, and export reports and a transparent activity record. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create one-click start and stop, manual entries, idle detection, tags, projects, and notes. Keep any application-name tracking opt-in and never record window contents or keystrokes. Add Pomodoro-style focus sessions, break reminders, and an optional allowlist blocker. Provide daily, weekly, project, and category reports with editable corrections. Export CSV and JSON and make the underlying event log inspectable. Add automatic local backups and a privacy screen explaining every collected field. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out employee surveillance. Deliberately leave out payroll and billing automation. Deliberately leave out cross-device blocking and behavioral coaching services. Finish by running the tests and listing the exact commands used.
