Describe the problem in whatever state it is in, and a founder reads it and replies.
A few lines are enough to start. Everything sent here goes straight to the founders.
A founder reads every message and will reply to you directly.
The same founders read the inbox and answer the phone.
Two founding partners run the firm and there is no layer above the work, so what you write here lands with one of them rather than with an account manager, a business development desk or a queue deciding whether your problem is worth passing upward. The partner who replies is the partner who would scope the engagement and stay with it through delivery, so nothing you explain here has to be explained a second time to somebody more senior.
The first conversation is about your problem rather than about us. We ask what the system has to do, which systems it would touch, where the data lives, who depends on the answer being correct, and what happens in the business when the answer is wrong. We say plainly whether the use case is worth building, what we would build first, and where the hard part is likely to sit. You should expect direct opinions rather than a capability overview. If we think your own team should build it, or that a different kind of firm fits the problem better, we say that in the conversation instead of after a proposal.
If both sides want to continue, we write up what we heard: the use case as we understand it, a target architecture, the scope of a first build, and the assumptions that would change either of them. That write-up is useful to you even if you build with someone else, because it is written so your own engineers can act on it. Scope and terms are agreed in writing before any work begins, and the partner who scoped the engagement is accountable for what gets delivered. If the fit is not there, we say so and the conversation ends cleanly. Nothing follows it unless you come back to us.
This is not a demo request queue. There is no product to book a slot against and no sequence of automated emails behind the form. It is not a mailing list, and writing to us subscribes you to nothing. It is not the route for contract placement enquiries, because we do not sell people by the head, and it is not the route for a strategy document with no build behind it. If what you want is our engineers working inside your teams, that is forward deployed engineering and it starts in the same conversation as anything else. Nor is it unlimited intake: we turn down engagements we cannot staff with senior people, and we would rather say that in the first conversation than have you find it out after a contract is signed.
If you are writing about a role rather than a problem, send it to rather than through this form, and a founding partner reads that inbox as well.
