The problem
What isn't working, in your own words. Precision beats polish and plain language beats a deck; a paragraph that names the ceiling you keep hitting tells us more than a brief that names the solution you expect.
Contact
We take on a few engagements at a time, and every one of them begins with a note. You tell us the problem, in your own words. We tell you whether it is one we should take on, and what we would build if it is.
Write to us
Operating remotely, with responses in days rather than weeks. We read every note ourselves; if the problem is right for us you will hear back from the people who would do the work, and if the timing is not right we will say so plainly and tell you why.
What to include
What isn't working, in your own words. Precision beats polish and plain language beats a deck; a paragraph that names the ceiling you keep hitting tells us more than a brief that names the solution you expect.
What makes it urgent, or newly possible. Timing tells us as much as the problem does: a constraint that just appeared, a capability that just became real, or a system that has outgrown the foundations it was built on.
A name and a way back. That is all we need to begin. If there is a date by which an answer matters, say so, and we will be honest about whether we can meet it.
What happens next
Within a few days you will hear whether the problem is one we should take on. If it is, the first conversation is an hour in which we listen more than we talk, followed by a short written note saying how we would build it, how long it would take, and what we would need from you.
Either way, nothing you tell us travels further than the people who read it. No mailing list, no follow-up sequence, and no reuse of what you shared. If we decline, we will say why, and if we can point you somewhere better, we will.