Non-tech until you start getting asked tech questions. When you're selling something you're trying to persuade your user that it's going to save them money, mak

Non-tech until you start getting asked tech questions. When you're selling something you're trying to persuade your user that it's going to save them money, make them money, or get them laid. As a technical person who's often in an advisory position on purchase decisions once the sales process has advanced a bit, I'll usually want to visit your website for the info I need. There I'm looking for a clear list of features (which shouldn't be an initial selling point but can be a differentiator or dealbreaker late in the decision making process, if your product doesn't do something I consider important or if I notice another way it could save us time or add capabilities). Then I'll go read your documentation on APIs and integrations. I'm seldom interested in what tech is under the hood of a SaaS product; and my non-tech colleagues never are. I want to know that it does what I need from it; it's stable; I can integrate with it/customize it easily and thoroughly. I also need to have confidence that you're not going to either expose my data to the world or run out of runway in 6 months and go out of business, leaving me hanging.