Eight sectors. One way of working.

Retail banking, lending, trading and the back-office systems that run alongside them. The team has built and supported core account processing, customer-facing channels, compliance and regulatory reporting — alongside the trading-floor side: FIX protocol integrations, order routing, position keeping.

Financial software earns its keep when it reconciles to the penny, every figure is traceable to its source row, and the audit log answers a question nobody has asked yet. That's not bolt-on work. It's designed in from the first commit, and tested against the standards the FCA and PRA expect.

Stacks span the new and the old: .NET / SQL Server reporting layers, COBOL back-end interfaces, ISO 20022 and SWIFT messaging, OAuth2 in front of legacy authorisation systems.

Production tracking, stock and inventory, picking and dispatch, integration with ERP and shop-floor machinery. The kind of software a factory floor actually trusts at 4am, on a scanner, with a gloved hand.

Half the work is on the floor: scanner-based picking, offline tolerance for intermittent networks, large hit targets and clear errors for shift conditions. The other half is integration — OPC UA from legacy PLCs, MQTT message buses, ETL pipelines into the warehouse reporting database, and the WMS / ERP layer above.

Stack-wise: SQL Server, VB.NET and modern web front-ends most often, with industrial protocols (OPC UA, MQTT, ASTM) where the machinery demands it.

Sample tracking, instrument integration, results management, electronic signatures and audit trails for industrial, clinical and pharma laboratories. The audit trail isn't a feature; it's the product.

These environments share a strict regulatory burden: 21 CFR Part 11 for electronic signatures and record integrity, ISO 17025 for testing competence, GxP across the wider pharma supply chain. Records become immutable on signature; amendments are tracked as versions; every state change has an actor, a timestamp and a reason.

Instrument integration is the part that breaks most builds: Beckman, Roche, Thermo analysers each speak their own dialect of HL7 v2 or ASTM, and the data they emit isn't always clean. The team has done direct and middleware-mediated integration across all of them.

Software for the operational side of healthcare delivery — private medical practices, community pharmacy chains, dental groups, private testing laboratories and veterinary practices. Practice management, appointment scheduling, patient or client records, dispensing, billing.

These environments share a common shape: care delivery as a regulated business operation. GDPR and data protection sit on top of professional regulator requirements (GPhC, GDC, RCVS, CQC depending on the sub-sector), dispensing standards in pharmacy, FMD for medicines verification. Integration with payment processors, accounting systems and clinical equipment is the day-to-day work.

NHS-side clinical messaging and patient-flow work is handled by our government & public sector practice — this section is strictly the private and operator-side of healthcare.

Case management for solicitors and small-to-medium firms — matter management, time recording, document handling, court timetabling, undertakings. The team built one of the early bespoke case management systems for a UK law firm back in 2003 and has stayed close to the sector since.

Legal software is workflow software where the workflow IS the work. A missed limitation date, an unrecorded undertaking, an untimed phone call — each one has a financial and professional consequence. We build the system to make the right thing the easy thing and the wrong thing impossible. Jurisdiction-specific rules — limitation, court timetables, LBA Pre-Action Protocol, SRA / Law Society of Scotland accounts rules — are designed in, not bolted on.

Most firms aren't looking for a wholesale replacement. They want the matter discipline that off-the-shelf packages won't bend to, the time recording fee-earners will actually use, and the document handling that respects how the firm already names and stores its files.

Accountancy, consultancy, advisory, surveying — the firms whose product is their process. Secure client portals, time and billing systems, document management, engagement workflows.

The shared concerns: capturing time at the point of the work (not the end of the week), client-side portals that respect confidentiality, document repositories that survive a regulator's review. Integration with the accounting and tax platforms the firm already uses — Xero, Sage, IRIS, Practice Engine and the like — is usually part of the brief.

Stacks typically involve .NET / SQL Server back-ends with modern web front-ends, secure document storage, and the API plumbing into the firm's existing accounting and CRM systems.

Most of the team's public-sector work has been inside NHS environments — patient flow, bed management, HL7 messaging, integration between clinical systems. Clinical safety, information governance and legacy systems that cannot simply be ripped out are the constraints we design around.

The wider public sector shares a common shape: workflow software where the workflow has stakes, secure data handling treated as a design constraint rather than a sign-off step, audit-grade traceability for every state change. Integration with existing estates — modern FHIR APIs over older HL7 v2, Mirth Connect between systems never meant to talk — is most of the day-to-day work.

Stack-wise: HL7 v2, FHIR, Mirth Connect, SOAP, SQL Server, VB.NET and React on the front end, with clinical safety standards applied from the first sprint.

EPOS integration, multi-channel stock, fulfilment, and the integration layer between commerce platforms and back-office systems. Retail systems live at the seams; the work is rarely a new system, it's making the existing systems agree on the same version of the truth.

Operationally critical concerns: stock that reconciles between till, web and warehouse; order pipelines that survive a Friday-afternoon spike; returns workflows that don't lose the customer or the audit trail. Payment integration, accounting integration, and the long tail of channel-specific APIs sit on top of that.

Stacks span modern e-commerce platforms (Shopify, Magento, BigCommerce, bespoke) with older EPOS estates, classic ASP and VB.NET stock systems, message-queue-driven order pipelines, and the ETL into finance and reporting.