Bookkeeping Software
Runato Books
Runato Books (Bookkeeping Software): Cash-flow forecasting and bookkeeping for trades contractors, built on five imported QuickBooks reports.
Overview
Runato Books is bookkeeping software for trades contractors. You import five QuickBooks reports and get a double-entry ledger, a 13-week cash-flow forecast and 26 CFO ratios that show their working.
The brief
The promise the product is built around: "Know which week you run out of cash, and which job is losing money — while you can still do something about it."
What we built
Import and ledger
Five QuickBooks reports are imported into a double-entry ledger. The code that reads them ties to real QuickBooks exports to the cent, and a fixture suite must pass to the cent before any change ships.
Custom Systems Architecture →Forecast and weekly update
A 13-week cash-flow forecast, a weekly update wizard and a setup wizard. The home screen shows whether setup is unfinished, the weekly update is due, or the books are current, with tiles for cash today, owed to you and what you owe.
Custom Systems Architecture →Reports
65 of 70 reports are built. A products and services list imports from QuickBooks.
API & Third-Party Integration →Quotes, proposals and invoices
One price per deal: the estimate holds the line items and the arithmetic, and the proposal is the view of it. The flow runs from estimate to proposal, send, e-signature, payment and invoice. Customers sign and pay from public links.
Custom Systems Architecture →The marketing page
runato.app is a scroll-driven page. In a mobile Lighthouse lab test on production it scored 100 for accessibility, best practices and SEO, 89 for performance on the fast path and 77 on the full animated path.
Front-End Development & Experience →How it helps
- It forecasts cash 13 weeks ahead.
- Every ratio shows its working, so an owner or bookkeeper can see where a number came from.
- Each company's books stay separate: row-level security in the database is checked by an adversarial test suite.
Every figure on this page is a count from a build record or a test run. A business result goes on this site only when it traces to a source we can open on a call: Results.
What it runs on
Supabase for Postgres, authentication, storage and edge functions; React and Vite with Tailwind and shadcn; Cloudflare Pages, deployed on push; Resend for email; Accept Blue for card payments.
How the work ran
This is how we run every engagement. It describes the process, not a timeline for this project.
The audit
We map what you already run and show you where it leaks. You keep the map either way.
The plan
What we would change, in what order, what it costs, and what number we will judge it on. You approve before anything is built.
The build
Each piece goes live on its own, so you see progress weekly instead of waiting for a big reveal.
The run
Managed, measured, month to month. Every channel judged on what a booked job costs you.
Builds are quoted once and built once; retainers you can stop any month. The full process and the published prices: How we work.
Questions
Is there a long-term agreement?
What does a build like this cost?
Do you use AI on this kind of work?
Read the full charter: The AI Charter.