SaBooks

About SaBooks

Last updated: July 27, 2026

SaBooks is a small, deliberately focused app for the paperwork side of running a one-person or small business: sending proposals, turning them into invoices, and keeping track of what has actually been paid.

What SaBooks Does

Most invoicing software grows in every direction until it needs an onboarding call. SaBooks goes the other way. It does five things, and it tries to do them without friction:

A home dashboard charts proposals, invoices, and payments over a date range you choose, so you can see what is outstanding without running a report.

Who It's For

SaBooks was built for the people who invoice a handful of clients a month and do not want an accounting suite: contractors and tradespeople, freelancers and consultants, and small service businesses. If you have been quoting jobs in a notes app and invoicing from a spreadsheet template, this is meant to replace both.

How It Works

SaBooks runs on iPhone, in any modern web browser at sabooks.app, and on Android. The web version installs to your home screen or desktop as a progressive web app, so it behaves like a native app without an app store. Sign in with Google or Apple and your data follows you across every device, because an account is keyed to your email address rather than to a particular phone.

Documents are generated as real PDFs on your device and sent through your own email account — nothing routes through a third-party sending service.

Signing In with Google or Apple

Using your Google or Apple account to sign in does not give SaBooks access to that account. It is worth being precise about what actually happens, because "Sign in with Google" is often assumed to mean more than it does.

When you tap the button, SaBooks hands you off to Google's or Apple's own sign-in screen. You authenticate there, with them. They then hand back a single piece of information: a verified email address. That is the whole exchange.

This approach is more secure than the usual alternative, not less. Because sign-in is delegated, SaBooks never stores a password — there is no password database here to be breached, leaked, or reused against your other accounts. Your sign-in is protected by Google's or Apple's own two-factor authentication, device checks, and fraud monitoring, which are considerably better resourced than anything a small independent app could build.

Your verified email address doubles as the key to your data, which is why signing in with Google and with Apple under the same address lands you in the same account.

Privacy, Plainly

Your business records are yours. SaBooks does not read them, does not run analytics over them, does not sell them, and does not use them to train anything. Each account's data is isolated at the database level so no other user can reach it. The app collects anonymous, install-level usage and crash statistics so bugs can be found and fixed — never tied to your identity or your records. It contains no advertising, no trackers, and no cross-app tracking, and it requests no device permissions at all. The full detail is in the Privacy Policy.

About the Developer

SaBooks is designed, built, and maintained by Michal Sabo, an independent software developer. It is a solo product: the same person writes the code, answers the support email, and decides what ships next. That is intentional — it keeps the app small, keeps the roadmap honest, and means feedback reaches the person who can act on it rather than a ticket queue.

SaBooks is a shipped, production product rather than a side experiment — a full cross-platform application spanning iOS, Android, and the web, with its own authentication, cloud data layer, PDF generation, and release pipeline across the App Store and the open web.

You can see more of Michal's work at michalsabo.com. Professional and consulting inquiries are welcome — contact details are on the Support page.

Status & Feedback

SaBooks is in open beta. It is actively maintained and ships small updates often. If something is awkward, missing, or broken, write in — feature requests are genuinely read, and small fixes frequently ship within days. See the Support page for how to get in touch.