CONTACT

Tell us the problem. We will tell you what it takes.

No obligation, no pitch deck. A conversation with the people who would build it.

START HERE

Send us an enquiry

The more you can tell us about the business problem, the more useful our first reply will be. Fields marked with an asterisk are required.

We reply within 24 hours, usually from an engineer.

WHERE YOUR MESSAGE GOES

Three kinds of enquiry

New project

You have a business problem and want to know whether software is the answer, what it would take, and what it would cost.

Goes straight to an engineer, not a sales queue.

Business & partnerships

Enterprise engagements, dedicated teams, long-running retainers, vendor onboarding and procurement questions.

Handled by the team who would run the engagement.

General enquiry

Careers, press, supplier questions, or anything that does not fit the other two.

Reviewed daily and forwarded to the right person.

WHAT HAPPENS NEXT

From enquiry to a written next step

You should know exactly what you are signing up for when you press send.

01

We read it properly

Every enquiry is read by someone technical. You will not get an automated qualification sequence.

02

We reply within 24 hours

Either with questions, a suggested call, or an honest note that we are not the right fit for this one.

03

Discovery call

45 minutes. You describe the problem; we ask about users, constraints and the systems already in place.

04

A written next step

What a first phase would look like, what it would deliver, and what it would take. Yours to keep either way.

BEFORE YOU WRITE

Common questions

More on how we work in the delivery process and the full FAQ.

What should I have ready before the call?

Nothing formal. The problem in your own words is enough. If you already know your deadline, budget range, compliance requirements or the systems it must integrate with, bring those — they shape the answer more than a feature list does.

Do I need a specification?

No, and often it is better that you do not. A specification written before any user research usually encodes assumptions that turn out to be wrong. Discovery exists to turn the problem into a scope worth building.

Will I be speaking to a salesperson?

No. The first call is with someone who would actually work on the project. We do not put an account manager between you and the people making technical decisions.

What if you are not the right fit?

We will say so on the first call, and where we can we will point you toward someone better suited. A bad-fit engagement costs us more than it earns.

Will you sign an NDA?

Yes, before any detailed discussion of your product or data. Send yours across or ask us for one.