Question 1

What counts as a digital product?

Accepted Answer

Anything people log into and use repeatedly: a SaaS platform, an internal tool, a customer portal, a booking system. The distinction from a website is repeat use by the same people.

Question 2

Do you build it as well as design it?

Accepted Answer

Yes. We design and build, which means the handover gap simply isn't there. We can also design for your own engineering team if you have one.

Question 3

Should we start with an MVP?

Accepted Answer

Usually. Pick the smallest thing that's genuinely useful to a real user, ship it, and learn. Big-bang launches tend to be expensive ways to test assumptions.

Question 4

How do you handle changing scope?

Accepted Answer

We expect it. We work in stages with a fixed scope per stage, so changes go into the next one rather than quietly inflating the current bill.

Question 5

Do you test with real users?

Accepted Answer

Yes, and it's usually the highest-value part. Five users on a prototype will tell you more than a room of stakeholders.

Question 6

Who owns the designs and code?

Accepted Answer

You do, once it's paid for. Files, components and repositories all transfer.

Question 7

We've got a limited budget. Is a digital products project still worth discussing?

Accepted Answer

Yes, and tell us the number early. We'll say honestly what's possible with it. If it won't stretch to what you actually need, we'd rather tell you than take the work and hand over something thin. Often the answer is to do one piece properly now and come back to the rest later.

Question 8

Why not use a template, or someone cheaper?

Accepted Answer

Sometimes you should, and we'll say so. If you need something simple and quick, cheap is a sensible use of money. It stops making sense once the thing has a real job to do, because the workarounds cost more than doing it properly.

Question 9

What if we don't like it?

Accepted Answer

You tell us, and we change it. You'll see the work as it develops rather than at a big reveal at the end, so there's rarely a moment where anyone is surprised. If something isn't right, saying so early is genuinely welcome, not awkward.

Question 10

Are we too small for you?

Accepted Answer

Almost certainly not. We're a small studio ourselves and plenty of our work is for owner-run businesses. Either way you deal directly with the people doing the work, not an account manager relaying messages.

Building something people will use every day?

This is probably you if

What that involves

Product discovery

Prototyping

Interface systems

Onboarding

States and edge cases

Roadmapping

Meet the people who'll actually do the work.

Ready to get started?

Luke Jagger

Kryspin Parchliniak

Charlotte Daw

Ollie Beckwith

Daniel Reilly

Roger Smith

Why people choose us.

You talk to the people building it

A fixed price before we start

You own all of it

We'll tell you not to spend

Offices you can actually visit

We stay after launch

Questions, answered.

Discover Our Projects

ViewLoop ‣ Digital Signage Platform, Custom Software

Pennine Gymnastics ‣ Booking System, Website & Brand Identity

Halifax Steam ‣ Brand Identity, Packaging

Excellerate Bioscience ‣ Custom Website & CMS

Pursue Talent ‣ Website Design & Build

Start a project