Question 1

Where does our data go?

Accepted Answer

Nowhere. Everything we build runs on infrastructure you control: your cloud tenancy or on-premises. Your data is never used to train foundation models, and data-protection exposure is assessed explicitly during the Diagnostic before anything is built.

Question 2

Who owns the software and the IP?

Accepted Answer

You do, outright. The code lives in your repositories, the documentation and runbooks are handed over, and nothing is licensed back to you. When the engagement ends, your team owns the system, understands it, and can extend it without us.

Question 3

How do you handle FCA, MiFID II, and GDPR requirements?

Accepted Answer

Compliance is designed in from the start, not retrofitted. Every system ships with a full audit trail from day one, human-in-the-loop checkpoints wherever your risk team requires them, and a regulatory and data-protection exposure assessment as part of the Diagnostic. We have deep experience across FCA, CIMA, MiFID II, SEC, and GDPR frameworks.

Question 4

What if the AI isn't accurate enough for production?

Accepted Answer

Then it doesn't go to production. Every Delivery ends in an evaluation gate: accuracy is measured against your real data, above a threshold we agree together, and you receive the evaluation report as the evidence for go-live. Where the system replaces existing software, we run the two side by side and benchmark against it. If the new system can't clear the bar, you stop: that's the point of the gate.

Question 5

Which AI vendors and models do you use? Will we be locked in?

Accepted Answer

We're model-agnostic. The model is chosen at Discovery for the job and your constraints: Azure OpenAI, AWS Bedrock, Anthropic, or open-weight models running on your own infrastructure where data residency demands it. Because you own the system and it runs on your infrastructure, models are a swappable component, not a dependency on us or on any one vendor.

Question 6

How much of our team's time does the Diagnostic take?

Accepted Answer

It's designed to be light on your side: a handful of interviews with the people who actually do the work, and someone who can answer questions about your systems and data. For most firms that's a few hours spread across the one to two weeks, not a project your team has to staff.

Question 7

Why is the Diagnostic paid?

Accepted Answer

Because it's real work, done by senior people, with real deliverables: a ranked opportunity map, a regulatory exposure assessment, a target architecture, and a costed recommendation. It's also credited in full against the next stage, so if we go on to build together the assessment has cost you nothing.

Question 8

How long until we're in production?

Accepted Answer

The Diagnostic takes one to two weeks and Discovery three to four. Delivery is planned at Discovery sign-off as a series of fixed milestones, each ending in working software you can see and test, so progress is visible throughout, not a big-bang reveal at the end. There is an explicit go/no-go decision at every stage, and you are never locked into the full journey.

Question 9

What happens after handover?

Accepted Answer

Your team owns and runs the system: that's the default, and we train them for it. If you'd rather we operate it, the optional Run & Monitor service covers drift monitoring, updates, and a weekly cadence, cancellable at any billing cycle.

Question 10

Do you work with firms outside finance and law?

Accepted Answer

Our depth is in regulated financial services, wealth management, and legal: that's where the regulatory frameworks we know best apply. We take on other regulated businesses case by case where the problem shape is similar. The fastest way to find out is the readiness scorecard or a short application.

Start small. Prove it. Then build.