In tax and accounting practice, the suitability of software tools directly impacts work efficiency and accuracy. However, different products (such as Drake, ProSeries, Prosystem fx, Lacerte, etc.) each have their own design strengths, and users often encounter missing features or inconveniences in certain areas during actual use. To this end, we are collecting real-world experiences from frontline users, hoping to systematically identify those details that are "nice to have" or "troublesome when missing" from a functional requirements perspective.

Although there have been scattered discussions about individual products previously, this call for input places greater emphasis on a cross-product, common perspective: if a new system could be built based on all known pain points and "must-haves," what functional framework should that system have? We look forward to hearing your specific descriptions, rather than general statements.

In response, I may personally develop mobile applications as temporary workarounds for some of the issues. If such applications are realized, they will be provided free of charge to users who participate in the discussion. Additionally, for key respondents who help me gain a deeper understanding of this field, I may also express gratitude through gift cards or similar means—this is not mere politeness, but a genuine commitment. Feel free to reply directly to this post to share your experiences and suggestions.