When writing software, I almost always reach first for Erlang these days—not because it's the most performant platform, but because it allows for an architecture where individual Erlang processes (tasklets/green threads) can crash and be restarted producing only events in a log that I can debug at my leisure, rather than waking me up at 3AM to fight a fire.
If I were a CEO (and I have been, but only as a single founder, so I've never felt that "others depend on me to not go hungry" feeling), I'd be looking for similar wins in that dimension: fault-tolerant strategies allowing me to know that nobody's going to go hungry because of one mistaken assumption, so that I can sleep at night.
If I was doing consulting, I'd try to productize it; if I had a product, I'd try to sell it to enterprises; if I had enterprise customers, I'd try to get them on a yearly pre-payment schedule; if I was in one vertical, I'd try to "clone" my product for other verticals with their own brands and marketing; etc.
Are you looking for these? Or are you prioritizing growth: trying to, effectively, sprint for three years, rather than figuring out how to run a marathon?