Definitely want to mitigate tax burden. Additionally, the direct indexing model does allow for more flexibility around loss-harvesting.
1 karma · joined April 1, 2022
Definitely want to mitigate tax burden. Additionally, the direct indexing model does allow for more flexibility around loss-harvesting.
We are exploring a few different models for rebalancing. One is to rebalance with new contributions only, another would be rebalancing with each investing (through both buying and selling), and the third would be a more tax-aware rebalancing where it only happens quarterly or annually (perhaps after you've locked in long term capital gains).
Since we lean prosumer / DIY platform, we feel like perhaps we should support a few models. Curious which you'd prefer?
Additionally, we're interested in side-by-side comparisons as well, similar to a code "diff" on Github. So you can see how your modifications changed performance relative to a past version.
We'd love to get your feedback on this. If you have more thoughts, feel free to reach us at hello [at] enombic [dot] com
If you want to stick to more traditional indexing approaches, that’s supported. For example, one user has stayed very close to VTI, but made some modifications to customize VTI to her goals and existing portfolio (https://enombic.com/abby/VTI-15).
We also have some users who want an easier way to automate their investments into a classic Vanguard basket (https://enombic.com/aml/lazy).
Everything on the app is DIY. So, alternatively, if you want to be more active, and test a thesis you may have, that’s supported as well.
Right now each index will track the latest version by default but we're thinking through something similar to version pinning with software dependencies. E.g., something like jdoe-index-0==v2