Questions we get asked

With a thirty-minute call, free and non-committal. We will tell you honestly whether this is a problem we can help with. If it is not, we will usually know someone who can. Most clients then start with a fixed-scope diagnostic before committing to anything longer.

The two diagnostics are fixed price, so you know before you start: Technology Health Check Essentials at £2,000 plus VAT, and the full Technology Health Check from £8,000. Everything else is quoted after a call, because the honest answer depends on what we find. We would rather scope it properly than publish a day rate and discover it was the wrong shape of work.

Usually within a week or two, and faster when something has already broken. We have picked up a CTO seat with two days of handover and gone on to deliver a certification deadline three months later. If we cannot give you the attention the problem needs, we will say so rather than take it and under-serve you.

Most of our work sits alongside one rather than over the top of them. A good CTO usually knows where the problems are and wants an independent voice to help make the case, or cover they cannot get from inside the business. We make a point of agreeing with the CTO what we are there to do before we start, because an engagement that arrives over someone's head rarely works.

Yes. Interim CTO cover, fractional technology leadership, go-to-market leadership and board-level advisory through a raise are all common. What we do not do is place a junior consultant and invoice for a partner.

Yes, and we are specific about how. The Essentials diagnostic uses AI to read the codebase, map dependencies and check configuration, which is the groundwork that would otherwise take a consultant a fortnight. A partner reviews every finding before it reaches you. On confidentiality: we agree the access and the tooling with you in writing before anything is shared, your code is not used to train anything, and we will tell you exactly which services are involved. If your policy rules out part of that, say so early and we will work within it.

You do. It is yours to share with your board, your investors or an acquirer. Where an investor has commissioned the work and the company is the subject, we agree who sees what before we start, because that is a conversation that goes badly if it happens afterwards.

Yes, and we do. Technical due diligence before an investment, a second opinion on a portfolio company that is worrying someone, or ongoing technology support across a portfolio. We have also acted as the technology adviser to a family office across five businesses, which included recommending that one of them be wound up.

An agency builds what you ask for. Our first job is to work out whether it is the right thing to build. Where the answer is yes, we can build it too: either through Aldemis Foundry, with a senior technologist attached throughout, or as an ongoing engagement with our own team working alongside yours.

Foundry is our build arm: AI-assisted development with a senior technologist attached to every engagement, on a monthly subscription. Use Aldemis when the question is what to do. Use Foundry when you already know what you want built and need it built properly, usually a first product or a significant piece of one, without hiring a team to do it.

Mostly between seed and Series B, which is where a technology decision is most likely to decide what happens next. We also do turnaround and due diligence work in larger businesses, up to a few hundred million in turnover, where the underlying problem is one we recognise.

Fintech, payments, embedded finance, capital markets, SaaS and regulated environments generally. We take work outside those sectors where the underlying problem is one we recognise.

Yes. We are based in London and Surrey and work across the UK and Europe, remotely and on site.

Yes, as a matter of course, and before any detail is shared. Everything discussed in a first call is confidential whether or not paperwork is in place. We do not name clients in public material either, which is why the case studies on this site are anonymised.