Mundo Sanchez built software to make businesses bankable and found a critical flaw in TurboTenant's design: it let users record transactions at any level in the hierarchy, causing property-level financials to become inaccurate. The fix is forcing every transaction to the property level so numbers roll up correctly. He's now cleaning up years of corrupted data.
So I'm building out a software to help businesses become bankable, and I'm looking at TurboTenant. Now, TurboTenant was a great software for what I needed and very cheap for real estate portfolio, but they have made a few huge infrastructure mistakes. So the way they work is they have a portfolio level which aggregates all their financials, then they have sub-portfolios. Which you can think of them more as like holding companies, and you can have multiple. And then they have the property level. And so the big infrastructure, uh, or architecture mistake that TurboTenant made that I am correcting is that when you are processing transactions as far as bookkeeping at the individual level, TurboTenant left it open in terms of it was optional. You didn't have to classify a portfolio or a sub-portfolio or a property, and that was the biggest mistake that they made. Because if you were to drill down into property-level financials and someone went in and categorized a transaction at the portfolio level or sub-portfolio level, you now have messed up financials. So huge exposure in terms of the quality of financial statements. What they should have done was forced every single transaction to occur at the property level, so that way when it gets aggregated up to the sub-portfolio level, which is like the holding company level, or the portfolio level, which I would equate to like the enterprise, your overall financial, uh, infrastructure, it would all get aggregated up and reported correctly. And that's not the case, and that's affected me. So now I'm having to go through and just clean up this huge mess.
