Got thrown into the deep in today for sure, but that's part of the fun.

I want to try and distill my understanding of things so far and not exactly sure who I should include on an email like this, but here we go.

1) It seems clearer and clearer that "Generational Wealth" is increasingly becoming the focal point of the messaging. My first thought in that regard is to approach it initially through the lens of an education 'product' (i.e. "ed.fund") with the expectation that there will be several additional products "funds" down the road to cover the gamut of wealth creating endeavors.

2) I think it is very wise to focus on releasing products that we know we have end-to-end control over (custodial). Supporting our existing customers is absolutely critical but we clearly know the roadblocks associated with both UT and AR with respect to the 529s. I think we should prove that we can gain traction on our own products (will only increase our valuation). At the same time, that does not mean to rush things like UX. My suggestion would be to slow down on new front end dev and be very picky with respect to UX. We can experiment though with respect to things like plaid vs. stripe vs. authorize.net or docusign vs. adobe vs foxit while building out the Sootchy API.

3) Centering focus on the UX of custodial accounts is not just about the end users of an app, it is also about the back office operational tools that our staff will have to employ in order to support that. I've got a bunch to learn in that world but an operational dashboard is probably going to be a major tool we'll have to build. (Does one of those exist already?)

4) I want to get into the OKRs more deeply. If we are clear about those then it makes it easier to make decisions about what we should prioritize once we get ready to launch code.

5) Last: a reminder to self about a list of the various tools we use (and pay for).