This is a list of features I'd like to see in a markdown tool to make writing docs easier.
Finding software developers is either hard or expensive. There is no reliable source of information an employer could search for skills, location and salary expectations to build a shortlist of suitable candidates.
On the other hand, developers with popular public profiles are bombarded with mostly irrelevant offers while many very capable developers are never even considered.
It won't tell you if the name is good, but it should save you the pain of picking a bad name.
Usually it's the first one to go
Just go to the URL
This decision making framework is based on the premise that startups are about growth. If you are not growing you are not a startup. You may be a business, but not a growing one. In most cases if the business is not growing it is shrinking (occupies smaller market share).
Let's say you are surviving.
This list was inspired by a small 50-page book with 24 lessons from Colin Powell: The POWELL Principles by Oren Harari.
There are no "correct" answers here. It is just a framework to make you think where you stand and how you can improve. Write down your answers and then read the book to check them against those of Colin Powell.
Founders are a better experts in their startup. Treat the investors as just one more data point.
If you have $1m in the bank it doesn't mean you have to hire 10 people. Focus on product-market fit and get traction first.
Trying to solve too many problems at once. Solve one and become indispensible at that. Expand from there.
I wouldn't call this a manual for "fanatical" customer support, though.
In most cases it is something the user did wrong at their end.
Ask them to perform an action. There is nothing more off-putting than homework.
