orignally shared this on startup school... i thought id' share it here.i'm using a `nocode communication tool` (a web-based interface... a single browser tab!) for all of these things:1. landing page — the landing page is the product and i wanted for folks to feel "transported" right into the app without having to walk through a shitty b2b marketing-style content. this is akin to my experience back in the `BBS` days of the mid-90's where you were immediately into the app, community, and tool. no terms of service, no privacy policy. just pure, immediate value.2. building community — we talk about life and startups and the metaverse and bitcoin and writing and all of the things that i love to think about and talk about! since this is my workspace (they are called "yeniverses") i want to love it more than anyone else. and as an artist, i want to love it even more. so, the community that's there every single day is there because they like these topics and want to talk and discuss them with me. this is nice because no one is really there that doesn't want to be there... instead, these are highly-qualified community members (and customers). it naturally weeds out folks who aren't interested in those things.3. a feedback system on the product — using a simple `public` room (which you can see at the very [bottom]( i can get direct feedback on the product itself which is the most important part in the very early-stage... i just want to know what works and what doesn't and then i can make those changes and fixes immediately. this is also super-useful because my entire team also can engage with the community and see, for themselves, the needs / wants / wishes / desires of the community at-large. this fixes a lot of the problems where team members are too distant or removed from their customers, which is a common problem as teams scale and grow. keeping this in the same interface as #4 is a total win.4. internal communication with my team / contractors (slack replacement) — this is probably one of the best parts is that i can use as many `private rooms` as i need to communicate with my fully-distributed team in both real-time and async. i use it for my development team that's helping to build the product as well as unique private rooms for contract teams and special projects. i can create them quickly, invite via email (any email works so you don't have to lock-in any specific domain) and then just get to work. delete them when you're done.(cont'd in the first comment...)