It&#x27;s always tough balancing features and staying out of the trap of adding features that don&#x27;t provide a lot of value to your users but takes up a lot of development time.<p>Maybe you can talk to the rest of the team to try to drive new features toward things that take less development time but provide a lot of value to users. Focus on the large value vs. easier development. But value vs. development time&#x2F;cost should be considered when mapping out features.<p>Your three items you mentioned (I know you&#x27;re not asking for solutions but here are some thoughts):<p>1. some apps need a calendar . . . try to keep things simple where it provides value but doesn&#x27;t try to clone more robust calendars&#x2F;features by large teams.<p>2. If this is to help clients get in to your app it&#x27;s probably worth it. At the end though you&#x27;re talking about storage in xls. If users are manipulating data in xls try to move them over to working with in the app instead and definitely get all the data out of xls and in to the database.<p>3. For emails mandrill.com (and similar) have this solved so integrate that in to your app.<p>As long as your work is interesting and you guys are profitable, your job is secure don&#x27;t get to bogged down in what you&#x27;re working on. Maybe build the best calendar integration ever = ). But you can use your knowledge&#x2F;experience to try to improve your app by trying to drive development toward big value&#x2F;low dev cost items.<p>Good luck.