01
New projects
A paragraph about the problem is enough to start. We reply within two working days, usually with questions rather than a quote.
FAQ What people ask before they work with us.
How engagements start, how we price, who owns what, and how we handle security, AI data and on-chain risk.
Working together
How does an engagement start?
- With a short call about the problem, then usually a two-week discovery at a fixed price. Discovery ends with a written scope, a list of risks and a number — not a slide deck. If you already know exactly what you need, we can quote directly.
How quickly do you reply?
- Within two working days. A paragraph about the problem is enough to start; we usually reply with questions rather than a quote.
Who actually does the work?
- Senior engineers. The people who scope your project are the people who build it, and they stay on it through launch. There is no handover to a junior team after the contract is signed.
Where are you based, and which time zones do you cover?
- We are based in India and work remotely. Overlap hours with your team are agreed up front, and we can cover working hours in India, the UK, the EU and the US.
Can you work alongside our in-house team?
- Yes. A dedicated engineering pod works in your repository, your planning cadence and your review process, as part of your team rather than beside it.
What happens after launch?
- Either a handover — runbooks, documentation and a walkthrough your team can follow — or we stay on as the team that runs and extends the system, with a named engineer and an agreed response window.
Pricing and contracts
How do you price work?
- It depends on the engagement. Product builds are fixed-scope and paid by milestone. Dedicated pods and fractional CTO work are monthly retainers. Audits and security reviews are a fixed fee by scope. The pricing page sets out each model.
Do you publish prices?
- Yes — starting prices for each engagement are on the pricing page. The final figure depends on scope, so every engagement gets a written, fixed quote before work starts, and discovery exists so that quote is based on evidence.
Will you sign an NDA before we share details?
- Yes. Send yours or ask for ours, and we will sign before you share anything confidential.
What if the scope changes during the build?
- We show you the effect on time and cost before the change is made, in writing. You decide whether to swap something out, extend, or leave it for a later phase.
Ownership and security
Who owns the code and the infrastructure?
- You do, from the first commit. We work in your repository and your cloud accounts, and keys and admin roles are held by your people. Documentation is written as we go, not assembled the week before we leave.
How do you handle our data and credentials?
- With least-privilege access granted for the engagement and removed at the end, secrets kept out of code and chat, and production data used only where the task needs it.
How is security built into the work?
- A threat model before the first commit, dependency and secret scanning in CI, a second engineer reviewing every change, and a written review before anything touches money or customer data.
AI projects
Which AI models do you use?
- We choose per task and keep the provider behind an interface, so it can be changed later. An evaluation suite built from your own data is what decides whether one model is better than another for your workload.
Will our data be used to train AI models?
- We use provider APIs under terms that exclude training on your data, and before anything is sent we tell you which provider receives it and where it is stored.
How do you know an AI feature works?
- By measuring it. Each feature gets a test set from real inputs that runs on every change, plus a trace of every production run, so problems show up in a score before they show up in a complaint.
Blockchain and Web3 projects
Does your security review replace an external audit?
- No. For contracts holding meaningful value we recommend an independent audit as well. Our review means the auditor spends their time on hard problems rather than obvious ones.
Which chains do you work with?
- Ethereum and EVM-compatible networks, including the main layer-2 rollups, plus Rust-based chains where a project needs them. The choice follows your users, assets and partners.
Do you give legal or regulatory advice?
- No. We work with your legal counsel and build systems that enforce the rules they define — for example transfer restrictions on a tokenized asset.
Still have a question? See how pricing works, the five ways to engage, or ask us directly.
06 / Let’s build
Bring us the difficult problem.
02
Careers
Engineers, designers and researchers who like systems that are hard to get right. Send something you built and what you would change about it now.
03
Studio
Based in India and working remotely, with overlap hours agreed up front so your team always has a time to reach us.
04
Read
Guides on AI agents, RAG, MCP, tokenization and chain abstraction, written by the engineers who build them.