A few weeks ago I shared Reporting SaaS here, and the feedback was clear: nobody wants "automated reports", people want to stop losing money without noticing.
So that's what it does now. Every Monday, a Shopify store owner gets a PDF report that explains why sales moved. And when discounts, refunds or cancellations run well above normal, the report puts a dollar figure on the loss, names the cause (the discount code, the most refunded product, the main cancellation reason) and suggests one action. If there's no clear cause, it doesn't invent one.
I've been working on Free Invoice Generator, a simple tool for freelancers and small businesses who just want to create a professional invoice without having to learn complicated accounting software.
While building it, I kept coming back to a simple question:
What are the features people actually care about when creating an invoice?
I've been building RentoX, a vehicle rental platform, as a way to work through some real product and engineering problems rather than just building another CRUD project.
The current version lets users:
Browse vehicles
Check availability for specific dates
Make and manage bookings
Receive real-time updates
On the engineering side, I've worked with Node.js, Express, PostgreSQL, Prisma, Redis and Socket.IO, including background workers and booking conflict handling.
