Let's build something together
Whether you have a detailed brief or just a spark of an idea, we'd love to hear it. We reply within one business day.
Prefer to reach out directly? Here's how to find us — or use the form and we'll come back with next steps.
What happens after you send this
No sales sequence, and nobody will chase you. Four steps, and you can stop at any of them.
You send the problem
A detailed brief is welcome but not required. The most useful thing you can describe is the problem — what is slow, expensive or breaking — rather than the solution you have in mind. We often propose something different, and cheaper, than what people arrive asking for.
We reply within one business day
Either with questions, or with an honest first read on whether this is work we are the right team for. If it is not, we will say so at this point rather than after a proposal.
A scoping call
Thirty to sixty minutes, no charge and no obligation. We walk through the process or product, the systems involved, the constraints you are working under, and what a good outcome would look like.
A written proposal
Scope, approach, assumptions and what is deliberately excluded. Where the requirements are still unclear, we will propose a short paid discovery phase instead of quoting a number that would only be a guess.
Before you get in touch
How quickly can you start?
It depends on current commitments, and we will tell you honestly on the first call rather than promise availability we do not have. A well-scoped automation or a single workflow can usually start sooner than a full product build.
What does a project cost?
Scope decides it, so we do not publish a price list that would be meaningless. What we will do is tell you the range early, before you have spent much time on us, and explain what moves it. If your budget cannot support what you are asking for, that is worth knowing in week one.
Do you work with small teams and startups?
Yes, and a large share of our work is exactly that — MVPs scoped to answer one commercial question, or a first automation that removes the most painful hour of someone’s week. Small does not mean unserious.
Can you take over an existing project?
Frequently. We start with an audit — architecture, dependencies, security, test coverage — and give you a written assessment of what is sound, what is risky and what stabilising it would cost, before committing to ongoing work.
Who owns the code?
You do, from the first commit, in your own repository and your own cloud account. No licensing arrangement, no hosting lock-in, and documented handover so you are not dependent on us for the next change.
Our data cannot leave our network. Is AI still possible?
Usually yes. We deploy self-hosted models with Ollama and a local vector database where data residency rules out a hosted provider. It costs more in engineering and hardware and the quality ceiling is lower than a frontier model, so we will tell you honestly whether your use case can afford that trade.