KelvinX
kelvin@work — ~/kelvin/projects case study · 2024

ledger

invoicing and payments for a twelve-person design studio · 2024 · still in use

A studio of twelve was losing the last four working days of every month to invoices. Spreadsheets were copied, totals were retyped, and two people checked each other’s arithmetic because they did not trust it. Nobody was wrong to distrust it.

The brief

  • clientDesign studio, Kochi — twelve people, about 40 invoices a month
  • my roleEverything technical: schema, API, UI, deploy, training, handover
  • stackNext.js, Postgres, a small PDF worker, Stripe for the payment links
  • timeNine weeks, part time, alongside their bookkeeper

What I built

One screen that lists the month, one screen per invoice, and a shared numbering rule so two people cannot create the same number twice. The PDF is generated from the same record the client sees — there is no second template to drift out of sync. Payment links are created once and stored, so a reminder email never creates a duplicate.

The part the client actually noticed was small: when an invoice is paid, the row turns green and the totals at the top move. That is all. But it meant the month-end check went from two people to one glance.

The invoice list screen
the month view, after about forty invoices

What changed

  • month-endFour working days of two people’s time → about two hours for one
  • errorsThree retyped totals in the month before launch → none in the nine months since
  • remindersNow sent from the app. Late payments dropped from about a fifth to under a tenth
Whiteboard diagram of the invoicing model
the whiteboard the schema came from. It survived the build almost unchanged.

The one bug worth mentioning

Six weeks after launch, a client was charged twice for the same invoice. The cause was ours, not Stripe’s: the payment link was regenerated when a draft was re-saved, and the old link was still live. Fixed by making the link a property of the invoice rather than an event.

- // regenerate the link whenever the invoice is saved - const link = await stripe.createLink(invoice) - invoice.paymentUrl = link.url + // one link per invoice, created once, reused by every reminder + const link = invoice.paymentUrl + ?? await stripe.createLink(invoice) + invoice.paymentUrl = link.url // idempotent

Twenty-two lines of test cover it now. There was no test before, which is the honest reason it shipped.

What I would do differently

I built the reminders before the bookkeeper had used the invoice screen for a week. She did not want reminders — she wanted a print view that fit on one page without shrinking the type. We built that in an afternoon in week seven, and it is the feature she uses most. Ask first, then build.

Next

railyarddeploy tooling for a rail logistics team2023
scannerstock counting that works offline2022

Start a conversation →

mainUTF-8LF● saved Markdown1,240 wordsno spell errors

© 2026 Kelvin Rodrigues Client name withheld. Numbers verified with the client.