[bthallplz]

You could open source it and continue to work on it as a side project and main thing in your portfolio to demonstrate your skills.

And over time you could even offer a hosted/paid SaaS option, if there seems be interest in that and you have more time and resources available to sustain that.

From the perspective that you'd refine this project over time (as you already have), I don't think you should worry too much about how the code and architecture look and are right now or people's reactions to their current state. It'll grow, change, and improve as you do. And others' reactions can help you grow.

> I spent the last 6 months rewriting the architecture for multi-tenancy, overhauling the UI/UX, and adding productivity and compliance algorithms.

Separately, I think it could be really good for you and your career to document somewhere online (even just a blog) some of your thinking/decisions regarding these spaces. And it doesn't need to be too formal, just lay out your thinking.

Your post here is pretty great as an example of your communication skills - which I've heard are highly appreciated/valued in CS -, so you've got the skills, and it'd be great for you to have more public proof of that.

[mohammede]

Thank you for your feedback and I would love your take on something, does it make sense to try and do that blog series to for example build a reputation for an agency or a company?

Like we at ACME changed X on Y because 123 and so on.

Or focus this on my personal branding instead?

[bthallplz]

Just focus this on your personal brand.

You can still relate it to concerns/business requirements or processes that agencies might have, which you considered and factored in when you made design decisions about the code, architecture, or processes. But since this is more of a project that you built on your own and one that you own, it makes more sense to me that you'd present this as "I changed X on Y because 123" and so on.