One of my least favorite genres of email to get: "I've spent $LONG_AMOUNT_OF_TIME making software which does $X. How should I market or sell it?"
Ideally you start working on that before or contemporaneous with building the thing; it informs what you build and how.
Ideally you start working on that before or contemporaneous with building the thing; it informs what you build and how.
Also, just in terms of being able to give useful advice quickly, saying "I have materially no work to share on a really big topic" makes answering this kind of email really hard.
It's like "I have a pretty good idea how to sell project management software. How do I make it?"
It's like "I have a pretty good idea how to sell project management software. How do I make it?"
"That's a pretty deep topic..."
"Well let's start somewhere tractable then: how does one Javascript?"
"Well let's start somewhere tractable then: how does one Javascript?"
Really specific questions are easier to answer and the answers are more likely to be useful, like:
"We sell X with pricing page here but we've begun to get indications that it's being used in true enterprises and I've been asked for an RFP. How do we even think through that?"
"We sell X with pricing page here but we've begun to get indications that it's being used in true enterprises and I've been asked for an RFP. How do we even think through that?"
