“Hello World” is a common expression used in programming, when trying something out for the first time. It seemed appropriate to use it for this first post, since keeoon is also an experiment, an experiment in changing how software is experienced.

In this post, we aim to describe why the company came into being; we’ll start with a couple of stories.

A startup founder’s story

Imagine you’re a startup founder: you have a business idea that you’re trying to validate.

Your idea needs some software, though, and you don’t have the expertise to build it, so you hire a team to build it for you.

You tell them what you want, work with them for a few months… and you have nothing to show for it; or maybe you have something, but it’s definitely not what you had in mind: the interface is hideous and clunky, and trying to do anything is an exercise in frustration because it takes so long… before failing.

You’ve spent most of your money away and, at this point, it’s very likely that your business is going to fail; there are customers interested in your solution but they don’t want to pay for something that gives them headaches.

A struggling company

In another company, in business for over a decade, there is a growing sense of unrest: their once well established position in the market is increasingly under attack from new entrants and, so far, they’ve been unable to innovate quickly enough to fend off the threat.

The engineering team is hard at work but, for some reason, the results just don’t seem to show up; in fact, productivity is going down because some of the most senior engineers have left due to being unhappy with the how the company works.

A better way?

We’ve seen the scenarios above play out too often and we want to do something about it. We want a world where businesses of all kinds can rely on software development teams to deliver, while promoting the right environment for engineers to be productive.

Our journey is just getting started though; if you’re excited by what you’ve just read, get in touch.