Feature Requests

I have found Dora exceptionally helpful in cleaning and analyzing all of my transaction data, as well as allowing me to import data from other apps. It would be helpful to have a restricted version of Dora enabled for the client, just for the spending tab, so that they can both clean up data imports and incorporate their exports from other tools, and ask dora questions about their spending.

this will be considered full retirement distribution planning to enable more detailed retirement conversations

it'd be great to be able to craft a annual check in walkthrough for the client to do. maybe an ability to flag various things they need to update within the system (like manual accounts, or quick questionnaire to flag changes that tells them to upload tax returns or new insurances, etc.) this would be similar to the initial onboarding guided process, but less steps and focused on "what has changed since we last talked"

v1: similar to the date tracker for when beneficiaries are last updated, it would be helpful to have a date field to track manually added accounts. v2: the date triggers an insight or client task for the client or advisor to update the manual account based on some trigger (advisor set? 6 months, annually, bi-annually?)

Would be nice to see some sort of widget or tracker or graph to see how net worth has done over time. Fun to see the journey with clients

The spending tab is robust as a personal household would ever need. Clients would like to see that kind of a "dashboard" for their small business which helps advisors separate business and personal spending/assets.

pain point: this has always been either a manual process or a tool that lives outside of the core financial planning process, which doesn't make sense. request: integrate into Kerdora a questionnaire that gauges a client's risk TOLERANCE. It can be the Grable-Lytton scale or something more simple like Michael Reynolds CalibrateIQ. the benefit Kerdora can then add is to also calculate the clients risk CAPACITY and risk REQUIRED. This would be similar to https://www.riskprofiling.com/How-it-Works . Risk Tolerance is the level of financial risk the client is emotionally comfortable with. Risk Capacity is the level of financial risk the client can afford to take. Risk Required is the risk associated with the return required to achieve the client's goals from the financial resources available. having these three overlapping venn diagrams would then allow for an interesting conversation at the intersection between them. The client might have a very high risk tolerance and capacity but the plant needs almost no risk required (near retirement tech exec perhaps). Alternatively, a client might have a low risk tolerance with high risk capacity and risk required (fearful young accumulator). Kerdora should be able to calculate the risk capacity and risk needed from the financial plan whereas risk tolerance would have to be a questionnaire. These would actually be fruitful conversations to have with a client rather than just throwing them into a standard risk tolerance questionnaire. The financial advisor should be able to override any of the sections if needed then an automated ISP should be generated with the ability to easily flag which accounts it applies to. The risk tolerance would be global per client/household but risk capacity/required would be specific to each investment goal.

As a Slant user, it would be great to have an ability to use an assigned Google Drive folder as the "storage space" for all document uploads (and for Kerdora to also see any documents uploaded/changed in Google Drive). This would allow both Slant and Kerdora to have full access to the clients documents. It would also allow print outs of client's financial plans to be put into Google Drive for Slant to be able to reference until a 2-way integration sync is enabled.

Mobile app (iOS and Android) for clients to: view plans, upload documents link accounts Advisors can: view client and plan information manage/assign tasks

Integrate with CRM, contact info, notes, tasks to prevent fragmented data on multiple platforms.