contact
start a project.
Tell us what you run and where it hurts. The more concrete you are, the more useful our first reply will be. We answer every message ourselves.
thanks - your message is in.
We read every enquiry ourselves and will get back to you shortly. If it is urgent, email us directly at hello@whetstone.works.
credentials & partners
questions
before you write.
do you only fix existing systems, or build new ones too?
Both. The bias is toward sharpening what you already run, because that is usually the faster win. But when something genuinely needs building, we build it to the same standard and hand it back legible.
how do we start?
Send a message with what you run and where it hurts. We read every enquiry ourselves and reply with either some questions, a call, or an honest note that we are not the right fit. No sales sequence.
how big is a typical engagement?
It varies from a short advisory review to a multi-month build. We take on a small number of engagements at a time so each gets real attention, which also means we sometimes have a short wait before we can start.
will we work with the people who actually write the code?
Yes. You work directly with the engineers doing the work, not an account manager relaying messages. The people who scope your project are the people who build it.
what do you hand over at the end?
Working software, plus the things that keep it working: tests, dashboards, and a short runbook so your team can maintain and extend it without us. Clever code that only we can read is a failure, not a feature.
which technologies do you work in?
We are not precious about the stack - we pick what fits the problem and what your team can maintain, and we are happy to work in your existing codebase. In practice a lot of TypeScript, Python, Go, PostgreSQL, and the major cloud and AI providers.