# Build brief — a focused alternative to Xero

> **Verdict:** Not faithfully · **Buildability:** 6/100 · **Category:** Finance Accounting
> **Source:** https://www.canitbevibecoded.com/xero
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Xero. Verify current pricing and capabilities before acting.

## Context

**Xero** — Cloud accounting, invoicing, bank reconciliation, payroll add-ons, and reporting. It currently costs $25/mo.

Invoices and reports are buildable, but Xero's real product is bank feeds, accounting workflows, accountant collaboration, compliance expectations, integrations, and trust.

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

Build simple bookkeeping with invoices, expenses, CSV imports, chart of accounts, and reports for personal/internal use.

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

## Requirements

### Functional

- Accounting model.
- Secure hosted database.
- Backups.
- Accountant/tax review.
- Payment integrations.

### Data and integrations

- Bank import/API.

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 freelancer bookkeeping app covering the personal slice of Xero:
invoices, expenses, and quarterly reports. Requirements:

- A local web app: Node + Express + better-sqlite3; income and expense entries
  with date, amount, category, client, and an attached receipt file.
- CSV import from my bank's export, plus a rules table (description pattern to
  category) so repeat transactions auto-categorize.
- Invoices numbered sequentially, rendered to PDF with pdfkit, one paid/unpaid
  flag. Nothing more.
- Reports: quarterly income, expenses by category, and a one-page cash P&L I
  can print for my accountant.
- Binds to localhost only, no accounts, no telemetry; write a nightly copy of
  the SQLite file to a dated backup.
- Out of scope: bank feeds, reconciliation, payroll, tax filing, and audit
  history. Do not build any of them; if I need real accounting, Odoo or
  Invoice Ninja is the honest route.
- README: state that this is a ledger for staying organized between real tools,
  not accounting. Xero's product is bank feeds, reconciliation, and books an
  accountant will accept, and no one should sign off these numbers unchecked.

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

- Bank reconciliation.
- Accountant workflows.
- Payroll/tax integrations.
- App marketplace.
- Compliance, licensing, and legal accountability are core features.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.

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

- [Odoo](https://github.com/odoo/odoo) — Open-source business suite with accounting modules; heavier than a solo DIY clone

---

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