Let’s build something calm.

Tell us about the product you want to ship, the constraint you are navigating, or the conversation you would like to start. We respond within two business days, by a human, in plain English.

Project brief

The more context you can share, the better our first response will be. We read every message.

By submitting, you agree to our Privacy Policy. We will not share your details with any third party.

Direct channels

// Frequently Asked

Before you write.

A few questions we hear often. If yours is not here, the form above is the right door.

Most projects begin with a 4-week sprint: 1 to 2 weeks of discovery and design, 2 to 3 weeks of prototype build, with a working artefact demoed weekly. If the prototype points toward a real product, we move into an embedded-studio phase of 3 to 6 months.

Sprints are fixed-price. Embedded studios are fixed monthly. Maintenance retainers are quoted against a defined scope. We never bill hourly and we never charge for over-time. A detailed estimate is part of every proposal.

Yes — we audit, then ship improvements. Our rule: we will not take on a codebase that does not build locally on day one, or where the team cannot answer questions about the data layer. If your project is in good shape, we can help. If it is in distress, we can stabilise it first.

Yes. We will sign a mutual NDA before we discuss any specific product detail, and we can run the entire first conversation under NDA if you prefer. We do not disclose client work, ever.

Pragmatic. We use large language models to assist with code, copy, and translation. We do not use user data to train models. When a product ships an AI feature, it is clearly labelled, audited for bias, and has a human review loop. We never ship an AI system that we cannot turn off.

For sprints: yes, our rate card is shared on request. For embedded studios: no — we quote against a defined scope. We will never hide behind a sales process; if our price does not fit, we will say so quickly and recommend an alternative.