Industries we work in

Sector does not change the engineering. It changes the constraints the engineering has to satisfy — what may be stored where, how long an outage is tolerable, what evidence a regulator expects, and how narrow the change window is. These pages set out those constraints per sector, and which of our services are usually engaged first.

What sector actually determines

Four constraints do most of the work in shaping a design.

  1. What the data is, and where it may live

    Clinical records, payment data, student records and citizen data carry different obligations for residency, retention, consent and deletion. Those are architectural constraints, and they are cheapest to establish before the architecture rather than during a review of it.

    Residency and retention
  2. What an outage costs

    Recovery objectives should follow from business consequence rather than from a standard tier. A system that stops physical movement and a system that delays a report warrant different resilience, and paying for the higher one everywhere is a common and expensive default.

    Availability
  3. How narrow the change window is

    Some estates can deploy continuously; others have a handful of windows a year. That single fact changes the delivery model, the testing strategy and how modernisation has to be sequenced.

    Change cadence
  4. What evidence is required

    Where a regulator or auditor will ask how a figure was produced or who had access, lineage and audit trail are functional requirements. Retrofitting them is substantially more expensive than designing them in.

    Evidence

Services these engagements draw on

Industry shapes the work. These are the services that deliver it.

Frequently asked questions

No, and we would be cautious of a consultancy claiming deep specialisation in ten sectors at once. What differs by industry is the constraint set — regulation, data sensitivity, availability expectation, change window — not the engineering. We are explicit about which of those we know well and which we would need to learn from your team.

The obligations and the cost of failure, mostly. A retail checkout outage and a clinical system outage are both incidents, but they warrant different architecture, different change control and different recovery objectives. Those constraints shape the design; the underlying patterns are largely shared.

Usually yes. The ten pages here are the sectors we are asked about most often, not a restriction. The first consultation will establish whether your constraint set is one we can advise on credibly, and we will say so if it is not.

We do not publish case studies, and we do not name clients. Where we can describe relevant work, we do so in a consultation with the identifying detail removed and the client's consent. We would rather say that plainly than present anonymised work as more than it is.

We describe practices rather than credentials. Where a regulation or control set applies to your estate, we design toward it and prepare the evidence trail — but we do not represent NG&NR as holding certifications it has not been awarded.

The service pages describe what we do. These pages describe the constraints a sector imposes on that work, and which services are usually engaged first. Most engagements start from a service and are shaped by an industry, or the reverse.

Yes, and regulation is usually a design input rather than an obstacle. The mistake we see most often is treating compliance as a review at the end, which is the point at which findings are most expensive to act on. Where an obligation constrains architecture, it should be established before the architecture.

Frequently that is the arrangement. We hold no vendor partnerships and take no commissions, so we have no interest in displacing an incumbent who is performing. Where one is not, we will say so with the evidence rather than the assertion.

With the constraint you are actually experiencing rather than the sector. If releases are slow, that is a delivery problem; if the estate cannot answer a question, that is a data problem. The first consultation is free and its main purpose is establishing which problem you have.

No. Pricing is transparent, published and includes GST, and it does not vary by sector or by how regulated you are. What varies is scope, because a regulated estate usually requires more evidence and more careful sequencing.

Next step

Talk to an architect about your sector

A free first consultation covering the constraints your industry imposes, the problem you are actually experiencing, and whether we are the right people to help with it.

No cost, no obligation. Pricing is transparent and includes GST.