How we work with teams abroad.
We're based in India and work with teams in the UK, Europe and the US. Here is exactly how that works day to day, so you don't have to guess.
Working hours that overlap with yours
| Your region | Live overlap with our team | What you can expect |
|---|---|---|
| UK and Western Europe | 4–5 working hours a day, from your morning to early afternoon | A written update every day, two live syncs a week, a demo every week |
| US East | 1–2 hours in your morning. We shift an engineer's day when needed | A written update every day, a fixed weekly call, a demo every week |
| US West | Limited. We work async first, with a scheduled early-morning call | Written updates, recorded demos, a weekly call |
Every engagement follows the same shape
- Scope in writing. The deliverables, dependencies, acceptance criteria and payment points are agreed before any code is written.
- Code in your repository from day one. You see every commit. Nothing is held back until the end.
- A written update every day. What changed, what's next, and any decision we need from you, in a few lines.
- A demo every week. Working software, not slides, recorded for anyone who can't attend.
- Acceptance and handover. We verify against the criteria together, then hand over architecture docs, runbooks and a recorded walkthrough.
Contracts
- A mutual NDA before we see any code or data.
- A master services agreement signed once, then a short statement of work for each audit or milestone.
- IP assigned to you on payment. We keep only our pre-existing tools and general know-how.
- A data processing agreement whenever personal data is in scope.
- Fixed prices per milestone. We don't bill by the hour, and scopes never renew automatically.
What we don't do
- Staff augmentation or open-ended hourly billing.
- Thin "wrapper" demos that won't survive real users.
- Starting work without a defined first milestone.
- Testing or probing any system you haven't authorised in writing.
Questions teams ask us first
Who owns the code?
You do. IP is assigned to you in the contract, and the code lives in your repositories from the first commit.
Can we see your code?
Our product code is private, but we'll walk you through real code from our production systems on a call, under mutual NDA. Our case studies cover the architecture in depth.
How do you handle our data?
Read-only, time-limited access, no production data on personal devices, and a data processing agreement on request. We can deploy private or local models when data can't leave your infrastructure. Security and data handling
What if the first milestone goes badly?
Every milestone has written acceptance criteria, and the audit is useful on its own, so you're never locked in.
Do you take on full product builds?
Sometimes, but always starting with a bounded first milestone. We don't sign open-ended scopes.