Community Discussions

Something similar happened on a side project I joined, where each contributor already had a system they loved, so merging everything felt impossible at first. We resolved it by agreeing on one “main hub” and keeping everything else optional, which cut down on confusion a lot. During that cleanup I found myself checking usage patterns with the help of https://www.spendbase.co/ halfway through the process, just to see what we could safely drop without disrupting anyone’s workflow. It made our toolset leaner and communication much easier.