Web, Mobile & Cloud

Web Platform Engineering

Customer portals, SaaS products and internal platforms — built to a standard your own engineers can extend after we leave, with performance and accessibility treated as requirements.

Overview

Software your team can still change in three years

Part of our Web, Mobile & Cloud Engineering practice.

Plenty of agencies can ship a first release. The harder test is whether your own engineers can extend it eighteen months later without rewriting it.

We build on mainstream, well-supported technology, write tests where they earn their keep, document decisions as we make them, and run a proper handover. The goal is a code base that outlives the engagement.

Capabilities

What we deliver

SaaS & product platforms

Multi-tenant architecture, subscription and entitlement models, admin tooling, audit logging and the operational features B2B buyers ask for in procurement.

Enterprise portals

Customer, partner and employee portals with SSO, role-based access, document workflows and integration into the systems of record behind them.

APIs & microservices

REST and GraphQL API design, event-driven services, versioning strategy, and integration with ERP, CRM, payment and legacy systems through documented contracts.

Legacy modernisation

Incremental migration of monoliths — strangler-fig refactoring, data migration and parallel running — so the business keeps operating through the change.

Performance & accessibility

Core Web Vitals budgets, bundle discipline, WCAG 2.2 AA conformance and audit reports you can hand to a procurement team.

Quality engineering

Unit, contract and end-to-end suites in CI, a preview environment per pull request, and error and performance monitoring wired up from day one.

How we work

A predictable path from first call to handover

No two engagements are identical, but the shape is consistent — so you always know what happens next and what you get at the end of each stage.

Discover

A short discovery to agree scope, users, non-functional requirements and the riskiest assumption. Output is a backlog and an architecture sketch, not a 90-page document.

Design & prototype

Clickable prototype and design system first, so disagreements happen over a Figma frame rather than a finished sprint.

Build in increments

Two-week sprints, working software at the end of each, deployed to an environment you can click through.

Launch & hand over

Production launch, monitoring, runbooks, documented architecture and a working session with the team taking it on.

Outcomes

What changes for you

  • A release you can demo from sprint two, not a big reveal at the end.
  • Test and deployment automation included, so the second release is faster than the first.
  • Accessibility and performance evidence for procurement and public-sector tenders.
  • Documentation and handover built into the plan rather than squeezed in at the end.

Tools & standards

What we work with

  • React
  • Next.js
  • Vue
  • Angular
  • TypeScript
  • Node.js
  • .NET
  • Java Spring
  • Python FastAPI
  • Go
  • PostgreSQL
  • GraphQL
  • Redis
  • Playwright
  • Storybook
  • Sentry

Questions

Frequently asked

Can you take over an existing application?

Yes. We start with a code and infrastructure audit, give you an honest assessment of what should be kept versus replaced, then agree a sequence.

Who owns the code?

You do, unconditionally, from the first commit. We work in your repositories where possible, or hand over a complete repository with full history.

Do you build the mobile app too?

That sits with our Mobile Application Development service — usually the same engagement and often a shared API and design system.

Let’s scope your next build.

Tell us what you are trying to ship. We will come back with an approach, a team shape and an honest estimate — we aim to reply within two working days.