Contact
Let’s build something useful.
Tell us what you’re building, what isn’t working, or what you want to improve. You don’t need a specification, a budget or a finished idea — a clear problem is enough to start.
- Response time
- Within two working days, from an engineer rather than an autoresponder.
- Confidentiality
- Happy to sign an NDA before anything is discussed in detail. Just say so in your message.
What happens next
- 01
We reply within two working days
A real reply from an engineer, not an automated acknowledgement.
- 02
A 30-minute call
We talk through the problem, the constraints and the timeline. No deck.
- 03
An honest answer
Either how we would approach it and what it would take, or who would be a better fit.
Good fits
The conversations we're most useful in.
Not a filter on who may contact us — just an honest description of where we add the most. Message us either way and we'll tell you straight.
- Founders taking a product to market
- You have a clear problem and paying interest, but no engineering team to turn it into software people can buy.
- Businesses that outgrew their tools
- The operation runs on spreadsheets, email threads and an off-the-shelf system that never quite fit.
- Teams that need engineering capacity
- You have a product and a roadmap, and more on it than your current team can deliver this year.
- Companies with software they can no longer change
- It still runs, but every change is risky, slow and dependent on one person who understands it.
Before you write
Things worth knowing first.
- How do you price work?
- Fixed fee for discovery, phased fixed scope for builds, and a monthly rate for embedded teams. You get a cost range before any build starts, and we would rather tell you a number you do not like than discover it together halfway through.
- We don't have a specification. Is that a problem?
- No — it is the normal starting point. That is what a discovery sprint is for. You need to be clear on the problem and who has it; defining the solution is our job.
- Who owns the code?
- You do. All source code, infrastructure definitions and documentation are yours, in your repositories and your cloud accounts, from the first commit.
- Can you work with our existing team?
- Yes. We work inside your repository, your process and your review standards. Embedded engagements are built for exactly this.
- Can you take over an existing codebase?
- Yes, and often. We start with an assessment so that both sides know what is really there before anyone commits to a plan.
- How quickly can you start?
- A discovery sprint can usually start within a couple of weeks. Build capacity depends on what is already running — we will tell you honestly rather than book work we cannot staff.
- What happens after launch?
- Software is not finished at launch, it is only in production. We deploy it with monitoring and alerting in place, hand it over properly, and stay on for support or continued delivery if that is what you want.
- How do you handle security and data?
- Access control, audit trails, secrets management and encrypted data handling are part of the build, not a later phase. We are happy to work to your compliance requirements and sign an NDA before anything is discussed.