Should you build your own Osome?

Honest answer: don't. Osome is not only an accounting dashboard. Its value
includes human-reviewed books, company administration, tax work, and filings under
local rules. A one-shot clone can organise financial records, but it cannot safely
incorporate a company, act as its secretary, verify its accounts, or take responsibility
for compliance.

If what you need is a personal financial-admin hub before handing records to your
accountant, build this safe slice:

- A local web app: Node + Express + better-sqlite3, server-rendered pages on
  localhost:4780.
- Create customers and sequential invoices with line items, tax rate, due date, and paid
  status; render PDFs with Playwright.
- Record bills and receipts with date, supplier, amount, tax, category, and a file
  attachment stored under ./data/documents/.
- Import bank CSV files and apply editable description-to-category rules; keep unmatched
  transactions in a review queue.
- Show cash received, cash spent, outstanding invoices, and expense totals by month;
  export every table as CSV for my accountant.
- Add a manually maintained compliance calendar. Every deadline records its source URL
  and last-checked date, and the UI labels it unverified until a professional confirms it.
- Provide a document vault grouped by financial year and an export command that creates
  one ZIP containing documents, invoices, and CSV reports.
- Back up the SQLite database and document folder nightly to ./backups/YYYY-MM-DD/,
  keeping 30 copies. No accounts, no telemetry, and no hosted service.
- Out of scope: bank API feeds, payroll, incorporation, corporate-secretary work, tax
  calculations, advice, and government filing. Do not imply that the generated reports
  are statutory accounts.
- Include a README with setup, CSV column mapping, backup recovery, and a warning to have
  all deadlines, books, and filings checked by qualified local professionals.