What we build, and who it’s for.

eCommerce & Shopify

DTC brands, Shopify Plus merchants, and stores outgrowing a purchased theme.

Your storefront converts worse than it should, and every fix breaks something else.

Theme 2.0 storefronts built on sections and schema, so the store stays editable without a developer — and stays fast once it fills up with products.

What you get

• Custom Theme 2.0 development
• Headless and Hydrogen storefronts
• Product bundles, filters, cart and coupon logic
• Shopify app development
• Sales channel and third-party integrations
• Theme migrations and performance recovery

• Liquid
• Theme 2.0
• Hydrogen
• Storefront API
• Admin API
• Shopify Plus
• Markets

Custom Websites

Companies whose website is a sales asset rather than a brochure.

Your site was built on a page builder and now nobody can change anything safely.

Sites built on a real content model, so editors edit content and developers change code, and neither breaks the other.

What you get

• Marketing and brand sites
• WordPress theme and plugin development
• Headless CMS builds
• Content modelling
• Technical SEO and schema

• Next.js
• React
• WordPress
• PHP
• Tailwind

Web Applications

Founders past the MVP, and teams replacing a system they have outgrown.

The prototype proved the idea. It will not survive the users.

Applications with the boring parts done properly — auth, permissions, background jobs, and a data model that still makes sense in two years.

What you get

• SaaS platforms and dashboards
• Authentication and role-based access
• REST APIs and integrations
• Queues, jobs and scheduled work
• Admin and internal tooling

• Laravel
• PHP
• Node.js
• React
• Next.js
• MySQL

Mobile Apps

Brands and platforms where the phone is the primary surface.

Your customers live on their phones and your product does not.

Native and cross-platform apps that talk to the backend you already have, rather than requiring a new one.

What you get

• iOS and Android applications
• API design for mobile clients
• Store submission and release process
• Ongoing release support

• iOS
• Android
• React Native
• REST APIs

Backend & Scalable Systems

Teams whose growth has started to cost them uptime.

It works fine until traffic arrives, and then nobody knows which part gave way.

We find what breaks first — queries, indexes, queues, caching — and rebuild those, rather than rewriting everything.

What you get

• API design and development
• Database design and query optimisation
• Background processing and queues
• Third-party and ERP integrations
• Performance and scalability work

• Laravel
• Python
• Django
• Node.js
• MySQL
• REST

UI/UX Design

Teams who need design that survives contact with engineering.

The design looks good in Figma and falls apart at 375 pixels.

Interface work done with the constraints of the build in mind, and decisions you can point at a reason for.

What you get

• Wireframes and user journeys
• Interface and design systems
• Figma-to-production handoff
• Accessibility review
• Conversion-focused UX

• Figma
• WCAG 2.2
• Design systems

QA, DevOps & Support

Anyone running production software without a safety net.

You find out about the bug when a customer emails you about it.

Testing and deployment set up so releases are boring, and someone is watching production who is not your customer.

What you get

• Manual and automated regression testing
• CI/CD pipelines and deployment
• Performance monitoring and Core Web Vitals
• Long-term maintenance retainers

• CI/CD
• Git
• Lighthouse
• Automated testing

Technology

How we choose a stack

We are not paid to recommend a platform. The decision is made against five things, in this order:

1. 01What the project actually has to do
2. 02How far it has to scale, and how soon
3. 03What it costs to run, not just to build
4. 04Whether someone else can maintain it in three years
5. 05Performance under real traffic, not benchmark traffic