If you run a one-person business, you know this problem. The proposal gets written in one app. The invoice gets built in another, or worse, in a spreadsheet you copy from last time and edit carefully so you don't leave the previous client's name in it. Payments get tracked in your head, or in a note on your phone, until one day you genuinely cannot remember whether the guy from March ever paid you.
None of that is a bookkeeping problem. It's a "my tools don't talk to each other" problem. So I built something that does.
What SaBooks is
SaBooks does five things: clients, projects, proposals, invoices, and payments. That's the whole app.
You add a client once. You attach a project to them. You write a proposal with line items, send it as a PDF, and when the client says yes you turn that same proposal into an invoice without retyping any of it. Payments get logged against the invoice, and the invoice keeps track of what's still owed.
That's the entire loop, and it's deliberately the entire loop.
The point is what it doesn't do
There's no time tracking. No expense capture. No receipt scanning. No calendar. No inventory. I built some of those, used them for a while, and took them back out.
Every one of them was a reasonable feature on its own. Together they turned a thing I could open and use in thirty seconds into a thing I had to navigate. For a solo operator, an app you can finish using during a coffee break beats an app that can do everything but needs a training session.
So SaBooks stays small on purpose. If you want software that runs your whole business, this isn't it, and I'd rather say that up front than have you find out after entering forty clients.
How it works day to day
Proposals and invoices each carry a status you can read at a glance from the list — draft, sent, partially paid, paid, or late. You don't set those. They're worked out from what's actually happened: whether you've sent it, how much has been paid against it, and how long it's been sitting there. An invoice that's been out more than thirty days with nothing against it turns red on its own.
Everything generates a PDF you can email straight from your phone or hand off to whatever mail app you already use. When you email a proposal or invoice, SaBooks stamps the date it went out, so "did I ever actually send that?" stops being a question you have to answer from memory.
Where your data lives
Your data sits under your own account, and only your account can read it. You sign in with Google, or with Apple on an iPhone — there's no separate password to invent and forget. If you've used both on the same email address, you land in the same place either way.
There's also a delete option that genuinely deletes everything, not one that hides your data and keeps it. I think that should be table stakes, and it's easy to check whether an app has it before you commit any real work to it.
Trying it
The web app lives at SaBooks.app — that's the fastest way to look at it, and it runs the same code as the phone version.
It also installs to your phone from that same address without any app store involved. On an iPhone, open it in Safari and use Share → Add to Home Screen. On Android, open it in Chrome and choose Install app. Either way you get an icon on your home screen that opens full-screen like a normal app.
SaBooks is in open beta. It's actively maintained and small updates ship often. There are rough edges, and I'd rather you hear that from me than discover it yourself. The upside of catching it now is that the roadmap is genuinely shaped by whoever's using it — if something's awkward or missing, tell me and there's a real chance it changes in days rather than never. Feature requests are welcome.
Why this is on a consulting site
Mostly because it's the honest version of what I do for clients. Most of the small businesses I work with around Hopewell, Princeton, and Flemington don't need a platform. They need one specific thing to stop being annoying — the invoicing, the inventory count, the thing two people are re-typing into two systems. Usually the right answer is smaller than what gets pitched to them.
SaBooks is that idea applied to my own paperwork. If you've got a process that's held together by a spreadsheet and a good memory, get in touch and I'll tell you plainly whether it's worth building something — including when it isn't.