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.
WHERE YOUR MESSAGE GOES
Three kinds of enquiry
New project
You have a product or workflow to build and want to understand the scope, risks and likely starting point.
Share the user, desired outcome and any systems it must work with.
Business & partnerships
For procurement, an ongoing engineering need or a partnership proposal.
Tell us what kind of collaboration you have in mind.
General enquiry
For careers, press, supplier questions or anything outside a project brief.
Use this category and include enough context for a useful reply.
WHAT HAPPENS NEXT
From enquiry to a possible next step
An enquiry starts a conversation; it does not commit you to an engagement.
Send the context
Describe the problem, the intended users and any constraints you already know. A full specification is not required.
We assess the fit
We review the enquiry and may ask for missing details before suggesting a call or a scoped starting point.
Agree on a next step
If the work is a fit, we can discuss whether a Product Blueprint, a tightly scoped Launch Sprint or another approach makes sense.
What should I include in my enquiry?
Tell us what problem you want to solve, who uses the product or process, and what you have already tried. A budget range, relevant systems and constraints are helpful if you know them.
Do I need a specification?
No. A short description of the problem is enough to begin. If the scope is unclear, a Product Blueprint can help define one workflow and the decision needed before a build.
Can I ask about the technical approach?
Yes. Mention the technical decision in your enquiry and the context needed to discuss it. We can decide who should join a follow-up conversation once we understand the scope.
What if the project is not a fit?
We may say that the proposed work is outside our scope or needs a different starting point. We will not promise to take on a project before reviewing its requirements.
Can we discuss confidentiality first?
Yes. If you need confidentiality terms, mention that before sending sensitive product, customer or business information so those terms can be discussed first.