[natdempk]

Its really hard to say without being in your situation, but assuming that you keep growing, it sounds like there's inevitably going to be a point where you need to do some major infrastructure refactoring/quality of life changes. I think that you should plan for that. Looking at your current situation and trying to estimate when you'll need to make these changes for some feature down the line or some major goal should give you an idea of when they'll actually be necessary. That isn't saying keep accruing technical debt infinitely, but rather figure out a natural point of growth/stability where the changes make sense and the debt needs to be erased.

[nRike]

That makes sense. In a personal note, I think doing monkey-patching code is okay in a discovery mode, but now we have a small revenue stream, we should focus on make the platform more reliable, and probably taking our users as the proxy to understand where the product lacks quality.