All work

Full stack · React, Node.js + MongoDB · Fintech · Accounting SaaS

suzobooks

Engineering an accounting SaaS: team access, correct balances, one-click deploys and alerts before customers notice.

Client
Eyemesto
Year
2026
Services
Full-stack development, Cloud & DevOps, Monitoring, Release management
SuzoBooks interface

Overview

The brief

SuzoBooks is a cloud accounting product: companies, chart of accounts, journals, sales and purchase invoices, and bank reconciliation. We work as its engineering team across the React front end, the Node.js API, MongoDB and the AWS servers it runs on, shipping features and keeping production healthy.

Problems & fixes

What was in the way

Pick a problem to see what was wrong, what we built and what changed.

The problem

Business owners could not bring in their accountant or staff, or limit what each person could see and change.

What we built

Team management with email invites (72-hour signed tokens) and View/Create permissions per module. Owners decide, company by company, who has access.

What changed

Firms run several companies with their staff from one account. It shipped to production after a 96-check automated smoke test.

1 / 5

Impact

What it changed

96Automated release checks
60 sHealth check interval
34Journal entries reposted
5Services on keyless deploys
  • Accounting firms can now give staff and accountants exactly the access they need.
  • Ledger balances are correct again and checked after every repair.
  • Releases are routine, and the team hears about problems before customers do.

How it works

Under the hood

Click any part of the system, or play the flow from start to finish.

Step 1 · React · Next.js

Web app

The accounting interface: companies, ledgers, invoices, reports and team settings.

01 —

Permissions per module

View and Create rights for each area of the app, set per user and per company.

02 —

Boring deploys

Merge, build, deploy, smoke-test. The same pipeline for every service.

03 —

Alerts with context

Slack messages name the server and container, then post again when it is back.

Timeline

  1. Aug 2026Keyless, containerised deploys for every backend service
  2. Sep 2026Container and URL health monitoring into Slack
  3. Oct 2026Team management, company access and permissions
  4. Oct 2026Balance repair and the move to suzobooks.com

Tech stack

ReactNext.jsNode.jsExpressMongoDB AtlasDockerAWS EC2GitHub ActionsAWS Secrets ManagerCloudWatchSlack

got an idea?let's lift it.

Tell us what you're building. A senior engineer, not a salesperson, replies within one business day.

Start a project
Start a project