# Build brief — a focused alternative to Osome

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

## Context

**Osome** — Company incorporation, bookkeeping, accounting, tax filing, and corporate secretarial services with software and human experts. It currently costs $58.42/mo.

The DIY bookkeeping interface is buildable, but full Osome combines it with human-reviewed books, tax and registry filings, corporate secretarial work, jurisdiction-specific advice, and responsibility for keeping a company compliant. Those services cannot be replaced safely by a one-shot app.

This brief describes a focused, single-operator replacement for the part of Osome 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 a local financial-admin hub for invoices, receipts, CSV bank imports, rule-based categorisation, cash reports, compliance reminders, and accountant-ready exports, while leaving filings and professional advice to qualified experts.

- 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.
- Bank CSV imports.
- Secure document storage.
- Reliable backups.
- Accountant and tax review.
- Local company secretary and compliance expertise.

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

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.

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

- Company incorporation, government registry filings, and corporate changes.
- Qualified bookkeeping review, tax preparation, and statutory filings.
- Corporate secretary, annual returns, registered address, and nominee services.
- Live bank and ecommerce feeds with verified reconciliation.
- Jurisdiction-specific advice, deadline ownership, and human support.

## 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: high. No reviewed project 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; it can replace part of the software layer, but not professional filings or compliance responsibility

---

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