Closes flow great, but tasks pop up that need to be addressed outside a regular close cadence! Things happen outside a MEC that we have to manage in a separate task-management system, and it creates immense friction.
You might say, why not use task view?
My good friend, Task View is absolutely horrendous. Try working with 60+ concurrent clients and 10+ task MECs. Task View causes things to get lost, and it requires heavy filtering that essentially renders it useless for planning a bookkeeper's day.
Double's main workspace is limited to that of the Close rather than the Client itself. If the client becomes a workspace, we can manage multiple sub-objects: their close itself (not the 10+ tasks within it), tasks that don't fall into a Close, internal client notes, and status updates on the work being done.
This workspace reorientation improves the task view by making Closes an actual "task" type object within the view, alongside the other ancillary outside-of-close tasks. It would be much easier for my bookkeepers to plan their workload, catch non-MEC tasks, keep their own notes, and, most importantly, eliminate another redundant task-management system from our purview.