Book a Technology Review

Home/Technology stack

Trust

What we build with.

The full stack, published. Chosen so the system still makes sense to whoever inherits it.

Every technology on this page is already named on one of our service pages. Nothing here is aspirational: it is the set we build with, support and hire for. We publish it because a technology choice you cannot see is a lock-in you find out about later.

The rule we apply is boring on purpose. A system we build should be legible to a competent developer who has never met us, five years after we last touched it. That rules out most of what is fashionable in any given year, and it is the single decision that does most to protect what you spend.

Languages and frameworks

The long-lived middle of the industry, not the edge of it. Every one of these has a deep hiring pool in the Midlands, a documented upgrade path and a support horizon measured in years, which is what matters when the system has to still be here in 2033.

  • TypeScript
  • C# / .NET
  • PHP / Laravel
  • Python
  • TypeScript / Node
  • Astro / Next.js
  • React Native
  • Swift / iOS
  • Kotlin / Android

Data and storage

Relational by default. Most business problems are relational problems, and a schema you can reason about beats a document store you cannot query three years later.

  • PostgreSQL
  • SQL Server
  • Redis
  • SQLite / WatermelonDB
  • Azure Synapse
  • BigQuery
  • Snowflake
  • dbt
  • Airflow / Dagster
  • Change data capture

Cloud and delivery

Both major clouds, because the right one is usually the one your business already pays for. Deployments are scripted and repeatable: nothing reaches production by someone copying files onto a server.

  • Azure
  • AWS
  • CI/CD pipelines
  • Automated test suites
  • Observability
  • Load & uptime monitoring
  • Run monitoring

Integration

The part that decides whether a project lands. Systems are joined over documented interfaces with retries, queues and an audit trail, never by a nightly spreadsheet somebody has to remember to run.

  • REST & GraphQL
  • OpenAPI
  • Message queues
  • Webhooks & polling
  • EDI
  • OAuth 2.0
  • Azure Service Bus
  • AWS SQS / Lambda
  • Integration middleware

Business systems we connect to

We do not replace your finance or CRM system. We connect to it, and we have done so often enough to know where each one hides its edge cases.

  • Sage 200 & 50
  • Dynamics 365 Business Central
  • SAP Business One
  • Epicor
  • NetSuite
  • Infor
  • HubSpot
  • Salesforce
  • Pipedrive
  • Zoho
  • Xero
  • Stripe

AI and automation

Applied where it removes a named piece of manual work, with a human review step and an accuracy figure you can audit. Not sprinkled over the product as a feature.

  • Azure Document Intelligence
  • AWS Textract
  • Large language models
  • Layout-aware extraction
  • Validation rules engine
  • Power Automate
  • Logic Apps
  • n8n
  • Rules engines
  • Scheduled jobs

Reporting

Numbers people actually open. Reporting is built on modelled data with row-level security, so the figure on the wall display and the figure in the board pack come from the same place.

  • Power BI
  • Looker Studio
  • Metabase
  • Grafana
  • SQL & dbt models
  • Embedded dashboards
  • Row-level security
  • Threshold alerting

Identity, access and accessibility

Authentication is federated wherever your business already has an identity provider, so leavers lose access the moment HR removes them rather than whenever someone remembers.

  • SSO & MFA
  • OAuth 2.0 / SAML
  • MDM & biometrics
  • WCAG 2.2 AA testing
  • Core Web Vitals budget

What we will not do

We will not build on a framework one person in the company understands. We will not put a proprietary layer between you and your own data. We will not hold your source code hostage: it is yours, in your repository, from the first commit. And we will not recommend a rewrite where an integration would do — see legacy system replacement for how we decide that.

How this is run day to day

Hosting, backups, authentication, deployment and monitoring are covered in detail on security and infrastructure.

Next step

Start with a technology review, not a proposal.

A short, structured conversation about where your systems are costing you time, margin or growth — and what the realistic options are. No pitch deck.