What we do for clients

Three ways of working with us: think it through, build it, or keep it evolving. Whichever you start with, the commitment is the same — a clear view of what you are getting, and responsibility for whether it works.

Consulting

Independent advice on the technology decisions that are expensive to reverse — cloud, artificial intelligence, blockchain, and the wider question of how a business becomes digital without becoming dependent. We look at how the organisation actually works before recommending anything that changes it, because a technology that fits the diagram and not the business is a cost, not a capability.

• Where cloud, artificial intelligence or blockchain genuinely fit your business — and where they would only add cost
• Digitalisation and transformation planned around how you operate, not around a product we would like to sell you
• An honest assessment of what you run today, with the findings in writing
• A roadmap you own outright and can execute with us, with someone else, or alone

Software design and delivery

Custom systems, designed and built to an enterprise standard and handed over as something you own — from the first conversation about what the business needs, to a system in service that someone is accountable for. We prefer sound architecture over temporary fixes and steady progress over quick wins, because what a system is worth is measured by how long it keeps working.

• A system specified against business outcomes rather than a list of features
• Scope agreed and written down before the build begins
• Progress you can see and judge at every stage, rather than a status report
• Documentation, access and ownership transferred with the system

Managed IT

Software does not stop needing attention on the day it launches. From that point we take full ownership of the product: its continued development, its maintenance, its expansion, and its availability. One party is accountable for the product doing its job — not a support queue, and not an assumption that somebody will notice.

That is ownership of the product, not of your operations. Your business, your estate and your people remain yours; what we carry is the system itself and the obligation that it keeps working.

• Development that continues: new capability as the business changes, at a pace you set
• Maintenance and correction, including the things only real use uncovers
• Expansion into what the product did not do when it shipped
• Accountability for the product being available and working — held by one party, not shared until nobody holds it
• The infrastructure, domains and mail the product needs — maintained as part of it, in accounts that stay yours

How an engagement runs

Every project has its own shape, but the sequence rarely changes.

Understand

What the business needs, and what success would look like — before anything is designed. What we agree here is what we build to.

Design

The shape of the solution, sized to the problem and to your organisation rather than to our preferences.

Build and prove

Delivered in working stages you can see and judge for yourself. Nothing is called finished on our word alone.

Hand over

The system, its documentation and the access to it come to you — it runs in your name, on your accounts. We stay on for the work that follows only if you want us to.

How we build it →

Where an engagement ends

Some end at handover: you get the system, the documentation and the access, and we step back. Others carry on, with us holding the product — developing it, maintaining it, keeping it available. Both are normal — which one you want is something we ask early rather than assume, because it changes how the work is built. What never changes is where the system lives: in your accounts, under your control, from the first day.