Services

Focused practices, joined up delivery

Each practice below can be booked on its own or combined into a single engagement. Every one of them ends the same way: something useful, documented, and yours to keep.

Practice 01

Web Development

Websites and web applications that stay fast, secure, and editable.

Typical work

  • Marketing and content sites built as static or server-rendered pages with editing workflows your team can use without engineering help.
  • Web applications: accounts, dashboards, billing, admin tooling, and the APIs underneath them.
  • Replatforming and rescues — inheriting an existing codebase, stabilising it, and moving it forward without a full rewrite.
  • Performance and security hardening: payload budgets, caching, dependency hygiene, and sane server configuration.

What you get

A deployed, monitored product; source code under version control with automated tests and deployments; and documentation covering setup, operations, and the decisions future maintainers will ask about.

Practice 02

Digital Product Design

Interfaces shaped around tasks, not decoration.

Typical work

  • End-to-end product design: flows, wireframes, interactive prototypes, and pixel-level interface design.
  • Design systems — component libraries, tokens, and usage rules that keep a growing product consistent.
  • Design-to-development handover with real components, not just pictures of them.
  • Design reviews of in-progress work from internal teams.

What you get

A tested design language, a source design file, and — when we build it too — a front end that matches it exactly, including states like empty, loading, and error that mockups tend to forget.

Practice 03

User Experience

Evidence about your users, gathered respectfully and cheaply.

Typical work

  • Moderated and unmoderated usability testing with people who match your actual audience.
  • Journey mapping and prioritised findings — what breaks, how often, and what it is worth fixing.
  • Accessibility evaluations against WCAG 2.2 AA, with a practical remediation plan rather than a compliance theatre score.
  • Content and information architecture reviews for products that have outgrown their original structure.

What you get

A short findings report written for decision-making: observations, severity, and recommended changes, each traceable to what was actually observed. Session recordings are shared only with participant consent.

Practice 04

Technical Consulting

An experienced second pair of eyes, on your side of the table.

Typical work

  • Architecture and stack reviews before a major commitment — or after a questionable one.
  • Vendor and contractor due diligence: what a proposal actually implies in maintenance cost.
  • Performance audits of live systems, from database queries to render-blocking assets.
  • Hands-on enablement: pairing with your team on the practices we leave behind.

What you get

A written assessment with findings ranked by impact and effort, a walkthrough session with your team, and — if you want it — an implementation plan you can give to any competent engineer.

Engagement

How working together goes

  1. Conversation

    A call or a written exchange about your problem. If we are not the right studio for it, we will say so and suggest who might be.

  2. Proposal

    A written plan within a few days: scope, stages, price, and the assumptions the estimate stands on. No obligation.

  3. Delivery

    Work in reviewable increments with a fixed weekly rhythm. You see everything as it happens and can redirect early and cheaply.

  4. Aftercare

    Launch support is included in every project. After that, many clients continue on a light retainer; none have to.

Start with a conversation