Free AI resources for consultancies

    Get to knowAssumeAI.

    The AI maturity assessment, the governance template and the free training, then every film we have made: the service walkthroughs, the client stories, the Oxford sessions and the team. All of it free.

    07More on YouTube

    Everything elseis on the channel.

    New films most weeks: the monthly roundups, the talks, the client stories and the walkthroughs, at youtube.com/@Assume_AI.

    08FAQs

    Beforethe call.

    What actually happens on the call?

    Forty minutes. We ask how your firm runs, where the work stalls, and what you have already tried. Then we tell you honestly whether there is enough in it to be worth building. No deck, no pitch.

    Who should be on it?

    Whoever can say yes, and whoever knows how the work really moves through the firm. That is often two different people. Bring both if you can.

    What does this cost?

    We will not quote you before we know where your hours go, and neither should anyone else. The first step is finding the leaks and putting a cost against each one, ranked. You then sign off exactly what gets built, so you see the number and the return it is based on before committing to build anything. What we are not is the cheapest option, and if you want a quick hack we are the wrong firm.

    What about our data and our clients' confidentiality?

    We do not build on top of your business, we build inside it. Everything lives in your existing infrastructure and you own all of it. We run our own firm’s confidential data through the same systems every day, so if they were not secure we would be the first to know.

    Do we need someone technical in house?

    No, and that is usually the whole reason firms your size have not started. The barrier is rarely the money, it is not having anyone who can build it. That is our part. Afterwards we train your team, hand over the documentation and leave you a roadmap you can run without us, because we do not want you dependent on us.

    What if the tools improve and leave what we build behind?

    They will improve. That is a reason to start rather than a reason to wait. We build around your processes, not around one model, and because you own the code you can change what sits underneath it. If better tools tomorrow are your reason not to act, you have chosen a reason that never expires.