Keeping a SaaS codebase clean as it scales is mostly about the decisions you make early — and the discipline to keep it honest as features pile on. That’s the part of the work I care about most, and it lines up with what you’re after: clean architecture, long-term maintainability, products that hold up.
I recently built Aqualytix, a production Ruby on Rails monitoring platform, solo and end-to-end — domain model, role-based auth, a reporting suite with server-side PDFs, a full Rails test suite, and zero-downtime Kamal deploys. I shipped it as seven independently deployable vertical slices, so there was always something working to demo instead of a big-bang reveal at the end.
A few things from your post that match how I already work:
- Clean, maintainable code: at DOST I took a backend service from 0 to ~90% test coverage and made it safer to change.
- Comfortable on existing codebases: most of my DOST work was reading and improving code I didn’t write.
- Strong debugging: I optimized slow queries through root-cause analysis, and codified framework-level bugs (like a Turbo-Frame double-request issue) so the team stopped hitting them.
On React: my recent Rails apps lean on Hotwire, but I work in React/TypeScript too and I’m comfortable on either side of the stack.
A long-term partnership is exactly what I’m looking for as well — so starting small makes sense to both of us.
Point me at that first task (or the repo) and I’ll scope it back to you before writing any code. Sound good?