Skip to content
← All work
2026–PresentCofounder & Full-Stack Engineer

ClosePinger

Client portal for bookkeeping firms. It requests files, chases them automatically, and tracks month-end close, including what is still owed, what is paid, and what extra work to bill.

Visit live site

What it covers

SaaSFinTechAccountingClient PortalDocument CollectionAutomated RemindersBilling TrackingWeb

Tech stack

Next.jsNode.jsPostgreSQLSupabaseCloudflareAWSVercel

The challenge

Document collection was a black hole of email. Every month the firm chased each client by hand, and nobody had a single view of which items were still outstanding, whether the client had paid, or which extra work had been done and still needed a bill.

Collaboration

I cofounded ClosePinger and built it end to end. The product came out of conversations I had with accountants while my cofounder and I were running ProntoMigo in Italy. Month-end close was the pain they described: chasing clients, tracking what each client still owed, whether that client had paid, and how to bill extra work. That tracking became the scope, and I took it from those conversations to a deployed portal.

From discovery to production

  • A client portal where the firm requests documents instead of emailing for them
  • Automated reminder sequences that replace the manual follow-up
  • Structured, encrypted uploads in place of email attachments
  • Tracking for what each client still owes, whether they have paid, and which extra work is billable
  • Separate views for accountants, clients, and staff
  • Month-end close status the firm can see without reconstructing it from a mailbox
  • Backend on Supabase, Cloudflare, and AWS, with the web app and portal on Vercel

How it was solved

Accountants, clients, and staff each get a different view from day one. Uploads land in encrypted storage as structured records, not loose attachments. A scheduled job runs the reminder cadence. PostgreSQL holds the close state: outstanding items, payment, and billable extra work. The API runs on Supabase, Cloudflare, and AWS. The portal is on Vercel.

Key technical decisions

  • 01Role-based access from the start, so accountants, clients, and staff never share one view.
  • 02Structured uploads into the portal instead of collecting files over email.
  • 03A scheduled reminder cadence instead of someone remembering to follow up.

Screenshots

ClosePinger screenshot 1

Impact

  • Manual chasing was replaced by a reminder cadence the firm does not have to run by hand.
  • Sensitive financial files sit in encrypted, structured storage instead of email threads.
  • The firm can see what is still owed, what is paid, what extra work to bill, and how close the month is.
  • The scope came from accountants, and the portal that shipped is the workflow they described.

What I learned

For back-office software, reducing anxiety matters as much as adding features. Clear status and a gentle reminder cadence did more than another inbox.

Want an outcome like this?