Question 1

How does a project usually start?

Accepted Answer

With a discovery phase. We run workshops with the people who do the work, map the current process, and produce a scope document with risks, architecture decisions and success metrics. That document is yours whether or not you continue with us.

Question 2

Do you work fixed-price or time and materials?

Accepted Answer

Both. Fixed-price suits well-defined scopes after discovery. For evolving products, a dedicated team or time-and-materials arrangement usually gives better value because it avoids padding estimates against uncertainty.

Question 3

How long does a typical project take?

Accepted Answer

A focused platform module typically reaches production in three to four months. Full enterprise platforms run six to twelve months, delivered incrementally so value arrives before the end date rather than at it.

Question 4

Who owns the source code?

Accepted Answer

You do. Source code, infrastructure definitions and documentation are handed over as part of delivery. We do not build lock-in into our commercial model.

Question 5

Can you work with our existing systems?

Accepted Answer

Yes — most of our work involves integrating with systems already in place. Where a legacy system cannot be changed safely, we typically put a facade in front of it and migrate capabilities incrementally rather than attempting a rewrite.

Question 6

Do you deploy on-premise or only in the cloud?

Accepted Answer

Both. Our platforms are containerised and can run in your cloud account, on your own infrastructure, or in a hybrid arrangement where data residency requires it.

Question 7

What happens after go-live?

Accepted Answer

Support agreements define response and resolution targets by severity, with monitoring and alerting in place and a named engineer familiar with your system. Incidents receive a written root cause analysis, not just a fix.

Question 8

Can our own team maintain what you build?

Accepted Answer

That is the intent. Handover includes technical documentation, runbooks and knowledge transfer sessions with your engineers. Several clients extend their systems independently after handover.

Question 9

How do you handle security and data protection?

Accepted Answer

Threat modelling happens during design, not after. We apply least-privilege access, encryption in transit and at rest, audit logging on sensitive operations, and dependency scanning in the pipeline. Security findings are retested after remediation to confirm closure.

Question 10

How do you decide whether AI is the right tool?

Accepted Answer

By measuring the current process first. If we cannot state the existing baseline and what improvement would justify the cost, the use case is not ready. We are equally willing to advise that a rules engine or a better form is the correct answer.

Talk to an engineer, not a form filter

Our office

Questions we get asked first