What working with us looks like, from the first conversation onwards.

How we work

Every engagement is different in what gets built. But the shape of how we work isn't. Whether you're figuring out where AI fits, building something specific, adding to what already exists, or handing the running of it over, the same seven stages sit underneath.

Working out where you are, and what's worth doing

Working out where you are, and what's worth doing

Understand

We spend the first two to four weeks mapping the current state — the data you have, the systems you use, the documents that carry the actual knowledge, and the way work moves through the organisation. This usually involves a small number of conversations with the people who do the work, a look at the systems, and honest questions about what's slow, expensive or fragile.

You end up with a picture of where you are, a shortlist of things worth doing, and the case for each.

Setting out what we're going to build, and why

Design

Once we know the shape of the problem, we set out the architecture. What data connects to what. Where the knowledge lives. Who's allowed to see what. Which model does the reasoning, and why that one.

The design gets worked through with the people who'll live with it. You end up with a document that describes what will exist, in language you can hand to your board.

The foundation, and the first system on top of it

Build

The build stage does two things at once. We stand up the foundation — the data connections, the structured knowledge, the identity and permissions, the audit and observability. And on top of that, we build the first working system: the reporting, or the automation, or the assistant, or the agent that the design set out.

The foundation is deliberately built first, even though it's not the visible bit. It's the work that makes everything else work.

Real people, real work, real outputs

Deploy

The first system goes live. Real people use it, doing real work, and it produces outputs the business relies on.

The first system is chosen to exercise every part of the foundation — data flowing in, knowledge being used, permissions being honoured, the audit trail being written, and a human somewhere reviewing before anything final happens. Not just the visible bit.

Making it yours to run

Hand over

Handover is where the engagement becomes yours.Your team gets documentation and training on how the system works, how to maintain it, what to do when something breaks.

If you decide to bring everything in-house from here, you can. Nothing we build is designed to keep you dependent on us.

More systems, on the same foundation

Expand

Once the foundation exists, adding more to it costs less each time. The connections are already made. The knowledge is already structured. The oversight is already in place. What you're paying for on the second, third and fourth system is the specific work of that system.

Expansion tends to be smaller, faster engagements — usually four to six weeks per system rather than months.

A specialist team, without recruiting one

Manage

Some organisations want to run the whole estate in-house from handover. Others would rather someone else keep it working while they focus on their business. If you're the second kind, we can take that on — monitoring how the systems are performing, tuning where they drift, adding new data sources as things change, and upgrading the underlying models as better ones arrive.

You get the benefit of a specialist team without recruiting one.

We're not tied to one vendor

Some organisations are committed to Microsoft and want everything to sit inside it. Others prefer to use the strongest component available for each part of the system, regardless of vendor. Both are reasonable, and we work fluently with both.

The method doesn't change. What changes is which technology earns its place in a given design.


How we're set up

Defined scopes, fixed fees where we can. Where the scope allows a fixed fee, we quote a fixed fee. Where it doesn't yet (usually because there's real uncertainty about what needs building) we'll say so plainly rather than pretending otherwise.

Built to be handed over. Everything we build is documented and belongs to you. If you decide to run it in-house, you have everything you need to do that.

Honest about fit. If we're not the right firm for what you're trying to do, you'll hear it in the first conversation. Not the third invoice.

Have a conversation with us.

Half an hour, no preparation needed. Bring the thing that's slow, expensive or frustrating, and we'll tell you honestly whether it's worth doing something about.

Concise,
St. Sampson,
Guernsey
GY2 4PW