01
Individual specialists
One engineer
One tested engineer joins your team to fill a skill gap, such as Go, AI or automated testing.
- Led by
- Your team lead
- Minimum term
- 3 months
- Notice
- 30 days
- Replacement
- Within 10 working days
Service 10 of 10Technology & Intelligence
We add one engineer, an AI specialist or a full team to your company. Our senior engineers test each person first. You choose who joins.






An illustrative team strip. Six role chips move from the photos into a team board marked “Cycle 24, day 1 of 10”. The board then reads “Team ready, 6 roles”. A readout shows four and a half hours shared between India and the UK.
Team options
The options differ in who runs the work and how much risk we carry. All 4 share the same engineer tests, onboarding and security.
01
One engineer
One tested engineer joins your team to fill a skill gap, such as Go, AI or automated testing.
02
2–4 engineers
Engineers for one area, such as mobile or data, with one contact. They check each other’s work first.
03
All the roles, with a lead
A tech lead, engineers, testers, a designer and a project manager. They work to a goal, not to hours.
04
A team that becomes yours
We hire, test and run the team. Then we hand it to you, on terms agreed at the start.
Illustrative These are typical terms. We set them for each project. Book a call
Team builder
Choose a mission, roles and time zone. Shared hours, capacity and estimated cost update as you go. Screens marked Illustrative are examples, not client results.
The team builder needs JavaScript. Below is the “Launch a new app” team it opens with and all 5 time zones.
Who is in the team9 people
A price unit is one engineer’s standard monthly rate, set in your contract. Capacity assumes 6.5 focus hours a day over 10 working days, after meetings and reviews.
Shared working hoursFive zones, 3–8.5 h shared
United KingdomLondon · GMT (UTC+0)4.5 h shared
Your working day09:00–17:30
Team shift, in your time04:30–13:30 · 10:00–19:00 IST
From late March to late October, London’s clocks go forward, so shared time grows to 5.5 hours.
EU CentralBerlin · CET (UTC+1)5.5 h shared
Your working day09:00–17:30
Team shift, in your time05:30–14:30 · 10:00–19:00 IST
From late March to late October, Central Europe’s clocks go forward, so shared time grows to 6.5 hours.
GulfDubai · GST (UTC+4)8.5 h shared
Your working day09:00–18:00
Team shift, in your time08:30–17:30 · 10:00–19:00 IST
Neither place changes its clocks, so shared hours never change. Meetings follow the Sunday-to-Thursday week.
SingaporeSingapore · SGT (UTC+8)5.5 h shared
Your working day09:00–18:00
Team shift, in your time12:30–21:30 · 10:00–19:00 IST
Neither place changes its clocks, so shared hours never change.
US EastNew York · EST (UTC−5)3 h shared
Your working day09:00–17:30
Team shift, in your time03:00–12:00 · 13:30–22:30 IST
US East needs a later India shift, set in the contract and shared out fairly. From mid-March to early November, shared time is 4 hours.
Skill coverage7 of 7 met
OnboardingSigned → first approved code change
An interactive team builder. Choosing a mission loads a suggested team, and the plus and minus buttons change it. Choosing a time zone shows your shared hours and meeting times. It opens on “Launch a new app” in the UK time zone. That is 9 people and about 91 work points every two weeks. A short demo changes the mission once, silently, and stops when you touch a control. Your changes are announced below. All figures are illustrative.
How we test
Our engineers test candidates in the role’s own tools. A named person scores each step. You see every scorecard.
Illustrative pass ratesA chart that narrows through six steps. Of 100 applicants, 32 pass the profile check, 17 the live coding interview and 10 the practical task. Seven pass system design, five AI tools and secure code, and four communication and references. Those four reach your shortlist. The figures are illustrative.
01 Profile check Senior engineer, 20 min
We check their code history and live products against what their CV says.
32 of 100 continue 32% pass
02 Live coding interview Senior engineer, 60 min
Coding in the role’s language: fixing unfamiliar code, explaining choices and writing a test first.
17 of 32 continue 53% pass
03 Practical task Tech lead, 2–3 h
A small, realistic problem, like a broken service. Ideally we work on it together, to see how they ask questions.
10 of 17 continue 59% pass
04 System design Principal engineer, 60 min
Building a system: size, what could fail and how to undo a release, scored on judgement.
7 of 10 continue 70% pass
05 AI tools & secure code Tech lead, 45 min
How they use and check AI assistants, plus security basics: user input, passwords, outside code and common web risks.
5 of 7 continue 71% pass
06 Communication & references Project manager, 45 min
Clear writing and how they handle disagreement and problems, plus 2 references from people who reviewed their code.
4 of 5 continue 80% pass

Skills and tools
We offer 3 levels. Mid-level engineers do good work from week 1. Seniors decide how the team writes code. A lead or architect owns system design and review rules. We use these tools but are not their partners.
Shading shows how easily we can staff that level today. We review it monthly. Ask for an engineer profile in any cell and we will send the scorecard. Ask for profiles
First 30 days
Each step has an owner and a date. We aim for a first code change in week 1, to prove access, set-up and reviews all work.
Typical timingsA 30-day timeline. Six steps fall in the first ten days, and the fit review is at day 30. We aim for a first code change by day 5 and a first work demo by day 10. The cards below give every date.
Day 0Ours
Signed before we name anyone, with background checks complete.
Day 1Yours
Accounts live in your system, so you give access and you take it away.
Day 2Both
90 minutes with your tech lead, recorded so the next person does not need it live.
Day 3Ours
The code builds from your set-up notes. If it does not, fixing the notes is our first job.
Day 5Both
A small change, such as a bug fix, a new test or a docs fix.
Day 10Ours
The engineer shows their work to your team after the first 2 weeks.
Day 30Both
A short review with your team lead: quality, communication, pace and anything to change.
“Ours” takes none of your team’s time. “Yours” needs about an hour from someone on your side. “Both” means we do it together.
How we use AI
AI drafts code and tests. An engineer approves every change. The AI runs on your accounts, under the controls below.
A mock code editor. An AI assistant suggests capping the wait between retries at five seconds, and the engineer accepts it. Below, the change passes four automatic checks. The engineer owns it, and it still needs a human review.
Where we work from
Our teams work on India time (UTC+5:30). The contract sets your shared hours, with a later shift if your time zone needs it.
Project and client teams 01
Project management, system design and client contact, including interviews, kick-offs, reviews and planning in your shared hours.
Engineering office 02
Engineering, testing and data work, with the same tools, review rules and security controls as New Delhi.
Shared hours, on a 24-hour India clockPale band: team shift · Blue band: hours shared with you
Times assume standard time in each zone. The UK and Central Europe get one more shared hour in summer. The Gulf and Singapore do not change.
We work remotely and meet in person when it helps, such as at a kick-off or a launch. These figures are targets we report on.
Security
Adding engineers to your systems is a security change. The 6 controls below are in every contract, so your security team checks them once.
Reporting
A cycle is 2 weeks of work. Each report shows the same numbers, in good weeks and bad.
Promised against deliveredWork points · last six cycles
An illustrative bar chart of cycles 19 to 24. Promised points: 34, 36, 38, 40, 42 and 42. Delivered points: 31, 36, 35, 40, 41 and 42. Under each column, the bugs that reached users: four, three, three, two, one and one.
Risks and blockersCarried forward until closed
“Cycle 24 closed as promised. The refunds work moves to cycle 25 until the payments test account is open. That is on your side, and I have asked for a date. I propose we drop one frontend engineer from cycle 27, when the redesign is done.”
Replacement target10 working days Set in each contract.
What you get
Most items come with every option. The table shows each item’s format, timing and which options include it.
| What you get | Format | When it arrives | Individual 6 of 9 | Pod 8 of 9 | Full team 8 of 9 | Transfer 9 of 9 |
|---|---|---|---|---|---|---|
| Tested candidate profiles 2–4 profiles per role, each with its test results, so you choose on evidence. | Profiles + scorecards | 5 daysWithin 5 working days of your request | Included for Individual | Included for Pod | Included for Full team | Included for Transfer |
| Tested engineers or a full team The same named engineers stay on your project for the full term unless you ask for a change. | Named people | Start dateOn the agreed start date | Included for Individual | Included for Pod | Included for Full team | Included for Transfer |
| Role profiles & test results Your role details and a score for each of the 6 test steps. | Scorecards | Pre-interviewBefore you interview | Included for Individual | Included for Pod | Included for Full team | Included for Transfer |
| A named project manager One person responsible for fit, quality and problems, reachable in your shared hours and named in the contract. | Named contact | Kick-offFrom kick-off | Not included for Individual | Included for Pod | Included for Full team | Included for Transfer |
| Onboarding plan A day-by-day plan for access, set-up and a code tour. We aim for a first code change in week 1. | Checklist | Day 0Signed off on day 0 | Included for Individual | Included for Pod | Included for Full team | Included for Transfer |
| Progress numbers Work done, promises kept, review speed and the DORA release measures. | Dashboard | Cycle 1From the first full cycle | Not included for Individual | Included for Pod | Included for Full team | Included for Transfer |
| Monthly review We review quality, fit, risk and next quarter’s team size with your tech lead. We write down each decision. | Report | MonthlyMonthly, in your calendar | Included for Individual | Included for Pod | Included for Full team | Included for Transfer |
| Handover plan & notes Design decisions, how-to guides and set-up notes in your wiki, written as we go, so knowledge stays when people leave. | Docs | Cycle 1+Written from cycle 1, updated every cycle | Included for Individual | Included for Pod | Included for Full team | Included for Transfer |
| Transfer and hiring terms For build-operate-transfer: the steps and notice, plus which people, accounts and documents move to you and when. | Contract schedule | Start / transferSigned at the start, run at transfer | Not included for Individual | Not included for Pod | Not included for Full team | Included for Transfer |
Scroll sideways for all 4 options.
Profiles, plans, tasks, documents and numbers live in your own accounts, so the record stays with you when we finish.
If you use a different tracker or wiki, we work in yours.
We set each report below at kick-off and name its owner.
Illustrative Timings are typical. We fix them for each project in a written scope. Ask for samples
What we measure
These show whether the extra engineers pay off: speed, promises kept, quality and engineers who stay.
Engineers work in your code within weeks, without months spent hiring.
2–4 weekstypical start, with a first code change targeted for day 5
Every 2 weeks you get the team’s output, speed and review numbers.
2 weeksbetween progress reports, if you choose a pod or a team
Add engineers for a launch, then reduce. Written notes keep the know-how with you.
30–90 daysnotice by option, with a replacement target of 10 working days
Targets Each row shows a target range on its own scale. We measure your starting point in the first 2 weeks. Then we confirm each target in writing.
Each measure is a horizontal scale with its target range marked. The text beside each row gives the same figures.
01
From an engineer’s first day to their first change, reviewed, approved and added to your code.
≤ 5working days
Lower is better
02
Work done against work planned, averaged over 3 cycles so one bad cycle does not look like a trend.
85–100per cent done
Inside the range is better
03
Bugs found in live use within 30 days of a release and traced to our code. Your team counts them.
≤ 1per team, per cycle
Lower is better
04
A DORA measure: the typical time from a saved change to running it live. Your release process affects it, so we measure your starting point first.
≤ 2working days
Lower is better
05
Engineers still on your project after 12 months, not counting changes you asked for. People who stay keep the know-how.
≥ 85per cent at 12 months
Higher is better
06
A DORA measure: the share of releases that harm the live service and need a fix or undo. Other bugs do not count.
≤ 15per cent of releases
Lower is better
Each measure has a named owner and a place in the monthly review. Ask about measures
Offers & plans
Add one engineer or AI specialist, a full team or a tech leader. We test everyone first. They use your tools. Grow or shrink the team as the work changes.
How to buy
How we work with you
Ask a quick question, send your project details or request a quote. The person who will lead the work reads each one in full. Services in your enquiry go with it.
Or book a 30-minute call01
For a first chat, a press request or anything not ready to plan yet.
You get A reply from a named lead
02Recommended
Goals, who it is for, budget and timing, so our first reply can outline the work.
You get Options and prices after one call
03
Your documents, deadlines and the purchasing and security rules to meet.
You get Confirmation and a named lead
How it is priced
Each plan shows how it is priced. Work starts once we agree a written scope and price.
Opens the project form with this plan chosen.
In your enquiry
In your enquiry
In your enquiry
| Plan | What you get | Best for |
|---|---|---|
| SquadOur specialists join your team and work in your tools. |
|
Teams with a clear plan that need senior people fast |
| RetainerA monthly team that runs and improves what we built. |
|
Monthly social media and ads, or care for live sites and apps |
| EnterpriseA large, long project with its own team and agreed response times. |
|
Large companies making changes across markets, brands or business units |
Questions
We hear these on first calls. Each answer links to the part of this page that backs it up.
Answer sheet · Tech Workforce 8 of 8 answered · evidence on this page
Usually 2–4 weeks from signing. Profiles reach you in about 5 working days. Interviews run the next week. It can be sooner if a suitable engineer is free.
Shown in Your first 30 days
Yes, and we expect you to. You see their test results first. You can say no without a reason. Then we send the next profile.
Shown in The 6-step test
Your team lead directs specialists and pods. Our project manager runs full teams to your goals. We review quality and fit with you monthly.
Shown in Who runs the work, by option
Our teams work from India. We agree shared hours with you, so calls, reviews and urgent fixes fit your day.
Shown in Shared hours, by time zone
We stay responsible after the engineer starts. Our senior engineers test everyone first. We check their work and replace anyone who is not the right fit.
Shown in What we report, and when
Tell us and we replace them. In the first 2 weeks, you do not pay for their time. After that, your contract applies, with a handover where notice allows. We note why, to choose better next time.
Shown in How we replace an engineer
What we make for you is yours once it is paid for. Tools we already had stay ours, and you get a free, permanent licence to use them. Engineers follow your security rules and confidentiality agreements. They get only the access they need, removed when they leave.
Shown in The 6 security controls
Yes. The contract sets the hiring terms up front, so there is no dispute later.
Shown in Build-operate-transfer terms
Send us your own questions in any format and we will answer them in writing.
Before you decide
We can send any of these before you sign, so you see what the work looks like first.
Send the roles, tools and start date. We reply in writing.
You will talk to the lead who would run your work.
Three ways to start
We always agree a written scope and price before work begins.
Choose one of the three ways above