Tell us what you are trying to build
Email, WhatsApp or the form below all three reach the same people. We answer every genuine enquiry within one working day, including the ones where the answer is that you should hire somebody else.
What is useful to include
- What you are trying to build, in whatever detail you have a paragraph is enough to start.
- What has to be true for it to be worth building. This is usually the most useful thing you can tell us.
- Any deadline that is real, and why it is real.
- A link to what exists today, if anything does.
- A budget range, if you have one. It changes what we recommend, not whether we reply.
- Worldwide / remote first
Before you get in touch
Within one working day, to every genuine enquiry, including the ones we are not the right fit for. If we cannot help we will say so and point you somewhere more useful.
Yes. We are remote-first and work across time zones. Most collaboration happens asynchronously over shared documents and deployed previews, with a regular call scheduled in a window that suits you.
A short call to understand the problem and decide whether we are the right people for it. If we are, you get a written scope with an architecture, an estimate and what it will cost to run afterwards. If we are not, you get that answer quickly rather than a proposal.
No. Discovery the structured phase that produces a specification and an estimate is a paid piece of work on larger projects, and it is agreed separately. The conversation that decides whether that is even worth doing is not.
Frequently. It starts with an audit of the codebase, build, dependencies, security posture and performance, so you get an honest picture of what is worth keeping before anyone proposes a rewrite.