Jeremy Helvey, CPA

Jeremy Helvey, CPA

Building at the intersection of finance, data, and AI

CPA and finance-systems builder with 10+ years across FP&A, month-end close, and enterprise ERP — now designing and shipping the tools that automate finance work: accounting engines, data warehouses, and LLM-powered workflows. Below are two projects I built end to end.

Selected Work

Projects

AI Finance Analytics Warehouse

Analytics engineering + an LLM natural-language query layer

An end-to-end analytics warehouse that transforms raw general-ledger, project, and chart-of-accounts data into decision-ready models — an income statement, project profitability, and budget-vs-actual — using dbt on DuckDB. On top of it sits a natural-language layer: ask a plain-English question and an LLM writes validated, read-only SQL, runs it, and returns the answer.

The AI Finance Analytics Warehouse: a plain-English question returns a written answer, a result table, and the validated read-only SQL the model generated.
Ask in plain English → the model writes validated, read-only SQL and returns the answer, the rows, and the query it ran. (Synthetic demo data.)
PythondbtDuckDB SQLLLM / natural languageStreamlit

Small-Business Accounting & Reporting Platform

A standalone double-entry accounting application, built in Go

An all-in-one accounting and reporting tool for a small practice. It imports and parses revenue and expense data (including QuickBooks exports), reconciles everything into a double-entry general ledger that re-posts from source on every change, and produces P&L, chart-of-accounts, cash-flow, and monthly reports with PDF and Excel export.

The accounting platform's business dashboard: filterable revenue, expense, and net-income totals with a per-worker profit-and-loss breakdown and Excel/PDF export.
The business dashboard: date-filterable P&L totals, a per-worker profitability breakdown, and one-click Excel/PDF export. (Synthetic demo data.)
GoDouble-entry ledgerData parsing / ETL PDF & Excel exportUnit-testedAI-assisted build

Runs entirely on the local machine. Real client data never leaves the device — the screenshot above and any public demo use a fully synthetic dataset.