Qrew LegendHi Mark,
It has been a great tool, we just have more complexity than the platform supports. Really, we've used this as a functional prototype tool as we've figured out our unusual business model. We use this for back-office management of real estate transactions as a brokerage in 32 states, and for back-office management of a multi-state real estate title insurance company.
I really didn't want to invest the time in the API-backend of QB, which I'm sure would do more of what we need. But I can see our future is bigger.
So for an example, in the web UI version, freezing data points with SNAP has been good EXCEPT undoing them is not good. And we need to freeze lots of lookup data on each real estate contract that we can do admin override to correct if needed.
I do a lot of odd things to pull data between forms to match multiple scenarios that is really hacked. In a SQL environment, it would just be some simple views and queries.
We also will need far more digital document management and interaction between digital form data points and our software.
And we need more interaction between our back-end system and our new website that is coming out soon. (You can see our current website at www.LakeHomes.com which attracted about 6 Million very active visitors last year).
I'm not casual in my assessment. I love the tool for most of what we do. While I'm leadership now, my background is Computer Engineering and data system design and development (including Innovations Awards and case studies on our work from Harvard, Auburn Univ, Dell, etc.).
I anticipate the next generation of our system will be a three to four programmers/data engineers for a year, even with a good framework.
Appreciate the interest!
G
Qrew Legend
