We want to help your business refocus on the things that matter most and use technology to take care of as much of the rest as possible, when you get it right it will make your life easier and your business more profitable.

We provide businesses with different solutions, depending on which types of problems they need solving. Typically this falls into one of two camps:

  1. For Software Companies, or development teams, we can help you conquer legacy code, deliver new features and squash bugs, improve your workflows and get the best out of your existing code and your team.
  2. For Other Businesses we can assist in digital transformation: getting technology to work for you to save you time and money.
In all cases we will use our technical expertise to help you Organise, Simplify, Streamline and Automate.

Latest Posts

    • Case Study
    • CRM
    • Oracle Service Cloud
    • PHP

    Smooth Customer Service

    When a CRM system perfectly matches a company’s business model, it becomes a frictionless interface between the business and its customers. When it doesn’t, everything is expensive, time-consuming and frustrating. That’s why TwinkleBob Solutions were commissioned to perform a CRM migration for a multinational company.

    Their old system had grown organically with the business, or perhaps “mutated” describes it better. Either way, it was no longer fit for purpose. The software was clunky, outdated and was no longer compliant with the relevant standards. So we needed something completely different, a system that would direct support tickets to the right person, on the right team, in the right country. It had to be fast, efficient and, ultimately, lead to happier customers. The problem? There wasn’t a solution on the market that was able to do all of that at the desired budget. So we rolled our sleeves up and built that solution.

    • Tech Tools
    • Technology

    Tech Tools: Have better meetings

    One our main goals is to use software to make life easier and business better. Sometimes it’s not about developing new software, sometimes it’s just as much (if not more) about knowing which off the shelf tools to use and how to put them together to solve a problem. Why reinvent the wheel?

    If you ever have meetings in your business then there’s a couple of tools that might be helpful to you. The first is one I use all the time, the second is one I’ve recently discovered that might be helpful to some of you.

    • PHP
    • Programming
    • Web Development

    In Defence of Legacy Code

    If there’s one thing that Developers love to hate, the biggest enemy of their creativity, the worst drain on their time, it’s “Legacy Code”. It’s a strange term really, when you think about it. Usually we think about a legacy as being a positive thing left behind after a particular person is gone. Whether that’s tangible or financial, like a bequest, or the legacy of a famous or influential person who has left an impression on the world - leaving it a different place to how they found it. In software terms, however, the term “legacy” almost always comes with a negative connotation.

    A lot of developers, at the mere smell of legacy code will shout to redevelop from scratch, to seek out the latest new shiny and rebuild the product from the ground up. There can be benefits to that, for sure, but it isn’t the only way. I’m mostly a fence sitter on this one, but if pushed I’d probably fall on the Maintain Legacy side of the fence. I don’t think it’s a black and white decision, though.

    • Case Study
    • Automation
    • Streamline
    • PHP
    • C#

    Automating Production

    It’s possible in a few companies to get by with very little technology, but for the rest there are decisions to be made, equipment to be bought and processes to be laid down. If you’re an expert in anything other than technology, you might not be able to solve those problems easily.

    As an example of a problem we helped to solve, there was a small factory that had a couple of ecommerce websites, selling directly to consumers and making on demand. They had a production management system and a team taking telephone orders.

    Each process had a separate evolution, created by different teams to solve different problems, except over time they had been brought together in a perfect example of the spaghetti approach.


subscribe via RSS