4 ms·

Yeah exactly. You can't just roll out of bed one morning and grustle out a stable enterprise application. Also: > customers paying $20k/yr or more have extreme

Yeah exactly. You can't just roll out of bed one morning and grustle out a stable enterprise application. Also: > customers paying $20k/yr or more have extremely high expectations across the board. They definitely do, in certain ways. But also a lot of the software companies use sucks shit. But this part of the other comment cracked me up. > a medium sized traditional industry that has ancient, crummy software This is actually how to do it but the thing they're leaving out is that you have to already have knowledge of the specific industry and its players, their niches, and the software they use within them. You have to know where standards are high, and where the current options are bad, and how to market that improvement to the companies that are juuuust flexible enough to switch to your product while being conservative enough not to dump you if exactly one VP leaves. Once you have all that in place, sure, you can "just" sell your software to them lol.

palmfacehn 2y ago
>This is actually how to do it but the thing they're leaving out is that you have to already have knowledge of the specific industry and its players, their niches, and the software they use within them. In most cases, this requires at least one former employee who used the crummy software. Most likely this person would be the one to identify the problem and propose an alternative solution. Information like this is extremely valuable. It forms the core of the biz opportunity. Casual comments often overlook this. Builders doing their own thing may not overlap with employees using office horror software 9-5.
- cj 2y ago
  Boiled down into 1 sentence: Create a company that solves a problem you’ve personally experienced. (If you feel like you haven’t experienced any problems worth creating a company to fix, consider putting yourself in situations where you’ll be exposed to different/new problem sets)
- sourcepluck 2y ago
  Lol @ "office horror software". So apt.
foxglacier 2y ago
Yes, get industry experience! You have to be pretty special to be just a software developer with no domain knowledge who can somehow make something more valuable than the bazillion other just-a-software-developers out there. I sell fairly high priced software to companies and I'm doing fine. Though I'm kind of lucky in how I got into it and by now most of my domain knowledge has come from my previous customers asking for things.

palmfacehn 2y ago

>This is actually how to do it but the thing they're leaving out is that you have to already have knowledge of the specific industry and its players, their niches, and the software they use within them. In most cases, this requires at least one former employee who used the crummy software. Most likely this person would be the one to identify the problem and propose an alternative solution. Information like this is extremely valuable. It forms the core of the biz opportunity. Casual comments often overlook this. Builders doing their own thing may not overlap with employees using office horror software 9-5.

cj 2y ago
Boiled down into 1 sentence: Create a company that solves a problem you’ve personally experienced. (If you feel like you haven’t experienced any problems worth creating a company to fix, consider putting yourself in situations where you’ll be exposed to different/new problem sets)
sourcepluck 2y ago
Lol @ "office horror software". So apt.

foxglacier 2y ago

Yes, get industry experience! You have to be pretty special to be just a software developer with no domain knowledge who can somehow make something more valuable than the bazillion other just-a-software-developers out there. I sell fairly high priced software to companies and I'm doing fine. Though I'm kind of lucky in how I got into it and by now most of my domain knowledge has come from my previous customers asking for things.