# Build brief — a focused alternative to FreshBooks

> **Verdict:** Partly, if you narrow it · **Buildability:** 43/100 · **Category:** Finance Accounting
> **Source:** https://www.canitbevibecoded.com/freshbooks
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from FreshBooks. Verify current pricing and capabilities before acting.

## Context

**FreshBooks** — Invoicing, expenses, time tracking, payments, and accounting for small businesses. It currently costs $23/mo.

For freelancers, invoices, time tracking, and expense logs are buildable; payments, tax/accounting reports, bank feeds, client portal, and reliability make it more than trivial.

This brief describes a focused, single-operator replacement for the part of FreshBooks 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

Generate invoices, track clients/projects/time, record payments/expenses, export reports, and email PDFs.

- Model a narrow bookkeeping workflow with explicit review and export steps.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Database.
- Invoice PDF generation.
- Email service.
- Stripe/PayPal optional.
- Backups.
- Simple reporting.

### 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 freelancer invoicing app to replace FreshBooks. Requirements:

- A local web app: Node + Express + better-sqlite3, binds to localhost.
- Tables: clients, projects, time entries, expenses, invoices, payments.
  Invoices get sequential numbers (INV-2026-001).
- Time tracking: a start/stop timer per project plus manual entries;
  uninvoiced time rolls into the next invoice draft at the project's hourly
  rate.
- Invoice PDFs: an HTML template rendered with Puppeteer, my logo and bank
  details from config.json, saved to ./invoices/INV-XXXX.pdf.
- Send an invoice by email via SMTP creds in .env, BCC me; mark paid manually,
  with an overdue list on the home page.
- Expenses: amount, category, optional client, receipt image attached.
- Reports: income by month, unpaid invoices with aging, income by client, and
  a yearly totals CSV export for my accountant.
- No accounts, no telemetry, all data local; nightly copy of the SQLite file
  to ./backups/, keep 30.
- Out of scope: card payments and a client portal, clients get a PDF and pay
  by bank transfer. Skip bank feeds and double-entry accounting.
- README: setup, SMTP config, and how to edit the invoice template.

## 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:

- Payment collection.
- Bank imports.
- Accounting reports.
- Client portal.
- Compliance, licensing, and legal accountability are core features.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.

## What you still own after launch

- 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: medium. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Invoice Ninja](https://github.com/invoiceninja/invoiceninja) — Open-source invoicing platform with payments, clients, and quotes

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/freshbooks