Yes, it is rudimentary for now -- it's a prototype after all. There's only one 'financial philosophy' built in to the algorithm, and it's quite conservative about lowering risk. But we think in the future it'll be useful to be able to switch philosophies with a single click.
Regarding life insurance, it only recommends it if you have a spouse, partner, or children. If not, it explicitly says, "Life Insurance: Until you have a spouse, a partner, or kids you probably do not need life insurance." If you're seeing something different it's a bug. I'd love a screenshot if you have one: victor@nickelhq.com
It should only allocate savings for vacation and the user-defined goal after saving for everything else. There's two separate loops in the code. But I'll verify it's working correctly.
It also allocated to the user defined goal before children's college education.
My advice would be to reduce the number of inputs and achieve a testable range of permutations as the minimum viable product...then test the hell out of it so that features can be added without regressions.
My impression is that the state space is enormous given the number of options and it is unlikely that any individual can hold the corner cases in their head given the combinatorial explosion.
Comments
Thanks for the feedback!
Yes, it is rudimentary for now -- it's a prototype after all. There's only one 'financial philosophy' built in to the algorithm, and it's quite conservative about lowering risk. But we think in the future it'll be useful to be able to switch philosophies with a single click.
Regarding life insurance, it only recommends it if you have a spouse, partner, or children. If not, it explicitly says, "Life Insurance: Until you have a spouse, a partner, or kids you probably do not need life insurance." If you're seeing something different it's a bug. I'd love a screenshot if you have one: victor@nickelhq.com
It seems to prioritize savings for a vacation over savings for children's education.
It should only allocate savings for vacation and the user-defined goal after saving for everything else. There's two separate loops in the code. But I'll verify it's working correctly.
It also allocated to the user defined goal before children's college education.
My advice would be to reduce the number of inputs and achieve a testable range of permutations as the minimum viable product...then test the hell out of it so that features can be added without regressions.
My impression is that the state space is enormous given the number of options and it is unlikely that any individual can hold the corner cases in their head given the combinatorial explosion.
Good luck.