Tell us what you're working on.

None of this is required — a paragraph and a deadline is plenty to start. But the more of it you include, the more useful our first reply is, because we can tell you what we actually think rather than asking four questions back.

• What you're building, in a sentence or two — the product and who it's for, not the architecture. We'll ask about the architecture.
• Where it actually is — nothing yet, a prototype, a live product, or a build that has stopped moving. If it's stuck, what the last three attempts were.
• The constraint that matters — a launch date, a funding round, an App Store deadline, a regulator, or a team that needs to keep shipping while this gets fixed.
• What you want from us — build it, unblock it, review it, lead it, or tell you whether it's worth doing at all. If you don't know yet, say that instead.

Happy to sign an NDA before you tell us anything sensitive — send us yours, or ask and we'll send ours.

The practice is two people, deliberately, so the person who answers is the person who would do the work. Nothing is triaged by someone who then has to go and ask.

Dominic works between Dubai and Europe, and Alex is in Europe — so between them the day is covered from early European morning through to the end of Gulf business hours. We work with clients well outside both, so timezone has never been the deciding factor; say where you are and we'll fit around it.

We keep the practice small. If an engagement isn't a fit — wrong shape, wrong timing, or something you'd be better served doing in-house — we'll say so early rather than take it on and find out later.