Cambridge, UK

Four connected practices, one way of working.

We move between digital delivery, infrastructure, operations, and ongoing care because they’re rarely separate problems. The expertise below is what we draw on when an engagement begins; we use the parts that fit.

01  /   04 Digital platforms

Modern websites and ecommerce, built to remain clear, usable, and effective long after we step away.

Marketing sites, content systems, ecommerce, integrations, payments, and deployment. We select proven, well-documented tools, minimise complexity, and document thoroughly so it can be understood and maintained without relying on us.

The right framework is usually the one you can still explain in two years.

What we do

  • Site design, build, and launch on static-first frameworks
  • Ecommerce setup, product structure, payments, fulfilment plumbing
  • Content systems and editorial workflows for non-technical owners
  • Performance, accessibility, and SEO basics done before launch
  • Deployment, environments, preview branches, and rollback paths

Tools we reach for

AstroNext.jsTypeScriptHTML/CSSJavaScriptReactCloudflareVercelSanityStripeGitHubResend

Typical engagement

  • 4–10 week build from kickoff to launch
  • Source in your GitHub, hosting in your Cloudflare
  • Optional platform care after handover
02  /   04 Infrastructure & Security

Cloud, migrations, security, and the quieter work that keeps systems honest.

Cloud and platform architecture and delivery across Azure and VMware, NetApp-backed storage, identity and hardening. The unglamorous side of digital transformation. From review to design to phased migration, with the rollback plan written first.

A working rollback plan is the cheapest insurance you can write.

What we do

  • Cloud and platform design across Azure and VMware
  • Compute, storage, and host refresh programmes
  • Network, identity, and landing zone setup
  • Security hardening, policy baselines, and access governance
  • Migration planning, phased change, and rollback preparation

Stack we operate

AzureVMwareNetAppWindows ServerLinuxBeyondTrustCloudflarePowerShellTerraformAnsibleJenkins

Typical engagement

  • Discovery and review first, written brief before any change
  • Phased migration with documented rollback at each step
  • Handover docs aimed at the team that will operate it
03  /   04 Platform care

Optional support after delivery - quiet and easy to leave.

A small ongoing arrangement to keep things running: hosting coordination, domain and email administration, updates, monitoring, and the technical questions a busy owner doesn’t want to chase.

Care should feel like leaving a key with a neighbour, not signing into a vault.

What’s included

  • Hosting and DNS coordination across Cloudflare or chosen provider
  • Domain renewal and email administration (Google Workspace, etc.)
  • Framework, dependency, and security updates on a steady cadence
  • Uptime and certificate monitoring with sensible alert thresholds
  • Small content and copy edits, links, redirects, page changes

Tooling

CloudflareGoogle WorkspaceMicrosoft 365LinearMonitoringZabbix

What we won’t do

  • Hold a domain or account in our name; ownership stays with you
  • Lock you into a contract you can’t exit with a month’s notice
  • Charge for emergencies that turn out to be a missing renewal email
04  /   04 Operational systems

Quality, safety, training, and process - the people side of the system.

Many of the same habits we apply to code work on a quality manual or an EHS rollout: legible structure, useful documentation, a small surface, an exit plan. We bring operational practice from regulated environments and apply it without ceremony.

A process that no one can find is not a process. It’s a memory.

What we do

  • Quality management, EHS, and Zero Harm programme design
  • Training content, induction packs, and competency frameworks
  • Process design, rollout planning, and internal communications
  • Audit preparation and documentation for regulated work
  • Operational dashboards and reporting structures

Practice areas

EHSQualityZero HarmTrainingRolloutAudit prepSOPs

Typical engagement

  • Short discovery to map the existing system honestly
  • Drafting and review with the people who do the work
  • Rollout support and a quiet review point a quarter later

Bring us the bit you keep putting off.

The work we’re best at sits between disciplines - a website that needs a real ops handover, a PKI estate that needs a designer, a quality manual that needs a version-control habit. Start with the awkward bit.

Start a conversation See track record