Admin Dashboard & CRM

Before (the problem)

Running a firm’s numbers meant living in three places at once: revenue in Stripe, the books in QuickBooks, and the client pipeline in spreadsheets. Reconciling them was manual, periodic, and error-prone — the kind of work that is always slightly out of date the moment it is finished. There was no single surface where revenue, cash, and pipeline agreed with each other.

What we built

A production admin dashboard and CRM that merges all three sources into one governed financial-reporting surface:

• Financials surface that merges Stripe, QuickBooks (OAuth), and local CRM data
• Client pipeline and financial KPIs in the same view
• A single backend (server.js) holding routes, schema, seed data, and migrations
• A vanilla HTML/CSS/JS frontend — no bundler, no framework

How it works

1. Stripe API supplies live revenue and subscription data.
2. QuickBooks OAuth supplies the books (P&L, balance sheet, AR/AP).
3. A local SQLite CRM holds clients, pipeline stages, and tickets.
4. The financials surface merges all three into one reconciled view.
5. Optional Bearer-token auth gates the surface; /health stays public.

Outcomes

• 3 disconnected systems → 1 reconciled view of revenue, pipeline, and cash
• Replaces manual spreadsheet reconciliation with a governed, always-current surface
• Runs live in production (Railway), not a prototype

Stack & role

Node.js · Express · better-sqlite3 (SQLite, WAL) · Stripe · QuickBooks · Railway. Built & operated in-house.

Timeline

Built in-house and deployed live to Railway; in daily use as the firm’s control plane.

What it proves

A one-person firm can run governed, reconciled financials from a single surface — the same problem every SMB has, solved with the discipline of a larger finance team.