A friend of ours recently got a fantastic job at the UK end of one of the world's biggest gaming platforms, at the internal software development team behind the console. Everything you do on these devices gets captured: every point scored, every bit of progress, all sucked back into a very big data warehouse somewhere.

The theory was that the company had a fantastic resource it could mine and slice, getting all sorts of interesting answers about how people engage with the games, and sharing those insights with partners to improve future versions. For years they'd been capturing masses of data, but had never quite got round to doing anything with it, and by the time they did, it had become such a massive amount that it was hard to know where to start.

Our friend was recruited to tackle exactly that problem, but admitted he didn't know quite where to start. Most companies, faced with terabytes of data, would model it all, talk to a dozen vendors, spend six months deciding on the perfect tool, and commit a lot of money upfront. He knew that was risky, would take too long, and could send his team down a rabbit hole hard to escape from. He wanted a low-risk, low-cost approach, with quality work done by experts, that mapped the territory more than anything else.

A low-risk approach that promises very good returns

He picked up the phone to us. Two weeks of prototyping later, we'd built some simple reporting functionality to explore what might be possible. We walked away once good early results were in, which he used to justify setting up a proper team. He's now at the corporate HQ overseas, leading a team of forty people doing what we did, at a much bigger scale, using what we'd shown was the right way to do it.

That project was a modest cost, but he used it as justification to do things properly at enterprise budget level: a low-risk approach that promised very good returns. We call this phenomenon the cheap art of the highly promising.

What we mean is that we get a lot of great, satisfying work from short-term projects like that. If an IT manager needs to achieve some goal, there are a few routes: do it in-house, if resource allows; bring in the management consultants, which is never a stupid move but might not meet budget or time; or hire a junior, with all the recruitment and onboarding that involves. All legitimate. But there's a fourth route: for smaller projects that still deliver real benefits, a quick, focused engagement with a small software house is often the perfect answer.

A bit of work that you've been dying to get done

Not every company is interested in small pieces of work like this. But we think they can be a lot of fun, and a good initial job tends to have a long tail of follow-on work once trust is established. We're happy to work with a fixed price, and you're getting a team, not an individual.

If there's a bit of work you've been dying to get done, but haven't had the internal resource to get round to, why not challenge a small, experienced, trusted team like ours and see what we can do? Worst case, a bit of money is spent and you learn the approach wasn't the right one. Best case, and most likely, you end up with something that finally gets a big item off the corporate to-do list.