hey, love what you're building. Incidentally I've considered building in this same space. In spite of the crowded nature of it, I believe there is still room for new variations and evolutions of "how it's done". Kudos on getting this far.
Curious how you've thought of positioning yourself -- what's a typical team look like that should pick your tool? How long have you been building this? How do you convince teams to pick you over say Linear (one of the new darlings)?
Thanks for your feedback and questions! Constructor is a great choice for teams using Trello that are feeling the pain of its limitations but don't want to sacrifice its glorious simplicity, or teams using GitHub Issues for similar reasons, or non-dev tools like Notion or Asana looking for something that understands software dev but isn't extremely complex to configure and use. We've been building it for a little over a year now, having onboarded our first customers in Jan 2021 and raised our first round shortly thereafter.
Our differentiator is lightweight flexibility, supported by conceptual models that reflect reality and don't impose one particular way of doing things on teams. Our goal is for teams to be able to "start simple and evolve easily" because for many teams their process is always being adjusted as they grow and mature. Our approach is essentially "Trello is like 90% of what many teams need, let's redesign it from the ground up for software teams and get it to 100%". It's early days but it's an approach that seems to resonate with many teams. At least partly this is because PMs and designers readily understand Constructor instead of being annoyed/overwhelmed, so everyone is happy using the same tool, and that's pretty important (to avoid tool schisms).
Curious how you've thought of positioning yourself -- what's a typical team look like that should pick your tool? How long have you been building this? How do you convince teams to pick you over say Linear (one of the new darlings)?
It would be great to hear some of the backstory!