[t3e]

We don't disagree and we've heard from non-technical managers and designers that Constructor has the potential to be simply "a better Trello for everyone". This is probably because despite being designed for software teams we try to serve all roles equally well, i.e. make sure we create an outstanding UX for the non-developers on those teams. Something we've seen happen at a lot of places is a "tool schism" where part of the team (design or PM) will cleave off and use Trello or Basecamp and leave the devs to Jira because they find it unusable, but the devs need their Jira for various good reasons. Constructor is designed to prevent tool schisms.

Your 80% observation is if anything an underestimate; there's almost nothing in Constructor that makes it dev-specific beyond the GitHub and devops integrations that are mostly absent if you don't activate them, and would be easy for us to make totally optional. This surprised us when we realized it, because we are quite devoted to serving software teams specifically.