Founders

(since I put my preferences out there, only fair that I put more such content in this channel)

Here is something I believe in + recommend: 

Avoid "champagne problems" - problems that arise after customers use your product enough.

_what happens if we get 100 users and don't have a glasses for the celebratory champagne? let's get the glasses first so we are ready_

this is the same as:
- what if our server can't scale to N requests/min? No need to solve that till your product is at N rpm. 
- customers will immediately ask for feature Y after trying feature X. Yes probably, get them to try X and care enough to ask for Y.

Musk is iterating on rockets that go to space. Iteration works. Do not get champagne glasses, just launch.

https://warpcast.com/rish/0x10585304

okay continuing on this theme

another thing that I personally like — building things where founders are the target customers 

build stuff the founding team will want to use, and then use it — makes it much easier to alpha test 

if you keep using it, see if others want it, most chances are someone will 

tweak as needed to expand market

(obv this is just one of the many ways to stumble upon something that works, happens to be something I’ve enjoyed personally)

working @ /neynar   🪐  casting @ /rish

I feel like founders might also make good customers because they're willing to test new things and provide feedback

Interested in social infrastructure (URL & IRL) | slowly building /firstdraft, curating /concretejungle | markfishman.xyz