Service 10 of 10Technology & Intelligence

Engineers and AI specialists who join your team when you need them.

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.

Two engineers reviewing code together on a monitor in an open office
Senior backendGo · Kubernetes
A team gathered around a whiteboard while a colleague walks through a plan
Project managerPlans · reports
Four colleagues gathered around a desktop screen, one pointing at the work under discussion
Tech leadArchitecture · review
A developer pointing at a laptop screen of code while a colleague leans in
AI engineerAI search · testing
An engineer working through an editor full of code at a table at home
FrontendReact · TypeScript
A hand typing on a laptop keyboard beside an open notebook and a pencil
Test engineerPlaywright

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.

Typical start
2–4 weeks
Team size
One engineer to a full team
Shared hours
3–8.5 h with your day

Team options

4 ways to add engineers, from one person to a team you own.

The options differ in who runs the work and how much risk we carry. All 4 share the same engineer tests, onboarding and security.

  1. 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
    • Skill gap
    • Fastest start
  2. 02

    Pods

    2–4 engineers

    Engineers for one area, such as mobile or data, with one contact. They check each other’s work first.

    Led by
    Your team lead, with our tech lead on quality
    Minimum term
    3 months
    Notice
    30 days
    Replacement
    Within 10 working days
    • One skill area
    • Checked by peers
  3. 03

    Full teams

    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.

    Led by
    Our project manager, to goals you set
    Minimum term
    6 months
    Notice
    60 days
    Replacement
    Within 10 working days
    • Agreed goal
    • Reports every 2 weeks
  4. 04

    Build-operate-transfer

    A team that becomes yours

    We hire, test and run the team. Then we hand it to you, on terms agreed at the start.

    Led by
    Ours, then yours
    Minimum term
    12 months
    Notice
    90 days
    Transfer
    Agreed up front
    • You own the team
    • Planned handover

Illustrative These are typical terms. We set them for each project. Book a call

Team builder

Build the team your plan needs.

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.

team-builder · Your company · draft plan Illustrative

The team builder needs JavaScript. Below is the “Launch a new app” team it opens with and all 5 time zones.

01 · Mission

A first version, live and in use, with tests and automatic releases behind it.

02 · Roles
  • Tech leadArchitecture · review · standards 1
  • Frontend engineerReact · Next.js · TypeScript 2
  • Backend engineerNode.js · Go · Python · APIs 2
  • Mobile engineerFlutter · Swift · Kotlin 0
  • AI engineerAI search · testing · PyTorch 0
  • Data engineerKafka · dbt · warehouses 0
  • Test engineerPlaywright · Cypress · k6 1
  • Cloud engineerKubernetes · Terraform · releases 1
  • Product designerFigma · screens · styles 1
  • Project managerPlans · reports · risks 1
03 · Your time zone

Who is in the team9 people

  • Tech lead× 1
  • Frontend engineer× 2
  • Backend engineer× 2
  • Test engineer× 1
  • Cloud engineer× 1
  • Product designer× 1
  • Project manager× 1
Team capacity
91 work points / two weeks
Engineering hours
585 focus hours / two weeks
Estimated cost
9.25 price units / month

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

  1. Team calldaily09:30 your time · 15:00 IST
  2. PlanningMonday10:00 your time · 15:30 IST
  3. Review & demoFriday12:00 your time · 17:30 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

  1. Team calldaily09:30 your time · 14:00 IST
  2. PlanningMonday10:00 your time · 14:30 IST
  3. Review & demoFriday13:00 your time · 17:30 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

  1. Team calldaily09:30 your time · 11:00 IST
  2. PlanningSunday10:00 your time · 11:30 IST
  3. Review & demoThursday15:00 your time · 16:30 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

  1. Team calldaily13:00 your time · 10:30 IST
  2. PlanningMonday14:00 your time · 11:30 IST
  3. Review & demoFriday16:30 your time · 14: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

  1. Team calldaily09:15 your time · 19:45 IST
  2. PlanningMonday09:30 your time · 20:00 IST
  3. Review & demoThursday11:00 your time · 21: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

  • System design, code review and standardsCovered
  • App screens in React and TypeScriptCovered
  • Data and links to other toolsCovered
  • Automated tests before every releaseCovered
  • Screen design and a shared style kitCovered
  • Going live: servers, releases, supportCovered
  • Plans, reports and risksCovered

OnboardingSigned → first approved code change

  1. Day 0Contract and ownership terms signed
  2. Day 1Log-ins from your system, only the access needed
  3. Day 2A tour of your code with your tech lead
  4. Day 3Code runs locally, tests pass
  5. Day 5First code change added
  6. Day 10First work demo to your team

Start a project

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

How we test engineers before you meet anyone.

Our engineers test candidates in the role’s own tools. A named person scores each step. You see every scorecard.

Illustrative pass rates
Applicants for one role 1004 screened, to reach your shortlist

A 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.

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

Two people at a laptop during a technical interview, one talking through the code on screen

After the tests

  • A shortlist, not a pile of CVs. Usually 2–4 engineers per role, each with a scorecard and interview recordings.
  • Your own interview. Interview anyone on the shortlist and turn down anyone, for any reason, at no cost.
  • Background checks. We check identity, education and past jobs before an offer, as far as your policy requires.
  • A replacement promise. If the fit is wrong in the first weeks, we replace the engineer. You never pay for both.

Skills and tools

Skills we offer, by tool and level.

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.

Illustrative availability Many available Available Limited

  • React Mid-level: Many available Senior: Many available Lead / architect: Available
  • Next.js Mid-level: Many available Senior: Many available Lead / architect: Available
  • Angular Mid-level: Many available Senior: Available Lead / architect: Limited
  • Tailwind CSS Mid-level: Many available Senior: Many available Lead / architect: Available
  • Flutter Mid-level: Many available Senior: Available Lead / architect: Available
  • React Native Mid-level: Many available Senior: Available Lead / architect: Limited
  • Swift Mid-level: Available Senior: Available Lead / architect: Limited
  • Kotlin Mid-level: Available Senior: Available Lead / architect: Limited
  • Node.js Mid-level: Many available Senior: Many available Lead / architect: Many available
  • Python Mid-level: Many available Senior: Many available Lead / architect: Many available
  • Go Mid-level: Available Senior: Available Lead / architect: Available
  • Spring Boot Mid-level: Available Senior: Available Lead / architect: Limited
  • .NET Mid-level: Available Senior: Limited Lead / architect: Limited
  • Laravel Mid-level: Many available Senior: Available Lead / architect: Limited
  • PostgreSQL Mid-level: Many available Senior: Many available Lead / architect: Available
  • MongoDB Mid-level: Many available Senior: Available Lead / architect: Available
  • Apache Kafka Mid-level: Available Senior: Available Lead / architect: Limited
  • Snowflake Mid-level: Available Senior: Limited Lead / architect: Limited
  • Databricks Mid-level: Available Senior: Limited Lead / architect: Limited
  • PyTorch Mid-level: Available Senior: Available Lead / architect: Limited
  • Anthropic Mid-level: Many available Senior: Available Lead / architect: Available
  • OpenAI Mid-level: Many available Senior: Available Lead / architect: Available
  • LangGraph Mid-level: Available Senior: Available Lead / architect: Limited
  • AWS Mid-level: Many available Senior: Many available Lead / architect: Available
  • Microsoft Azure Mid-level: Available Senior: Available Lead / architect: Limited
  • Google Cloud Mid-level: Available Senior: Available Lead / architect: Limited
  • Kubernetes Mid-level: Available Senior: Available Lead / architect: Available
  • Terraform Mid-level: Available Senior: Available Lead / architect: Limited
  • Playwright Mid-level: Many available Senior: Available Lead / architect: Available
  • Cypress Mid-level: Many available Senior: Available Lead / architect: Limited
  • GitHub Mid-level: Many available Senior: Many available Lead / architect: Available
  • Figma Mid-level: Available Senior: Available Lead / architect: Limited

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

From signed contract to first code change.

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 timings

A 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.

  1. Day 0Ours

    Contract, confidentiality, ownership

    Signed before we name anyone, with background checks complete.

    • Both agreements signed
    • Background checks on file
    • Named engineer confirmed to you
  2. Day 1Yours

    Accounts in your log-in system

    Accounts live in your system, so you give access and you take it away.

    • Only the access needed
    • Code and task access
    • Briefing on your security rules
  3. Day 2Both

    A tour of your code

    90 minutes with your tech lead, recorded so the next person does not need it live.

    • Map of your systems
    • Code review rules
    • On-call and how-to guides
  4. Day 3Ours

    Code running on their laptop

    The code builds from your set-up notes. If it does not, fixing the notes is our first job.

    • App runs locally
    • All tests pass
    • Set-up notes fixed
  5. Day 5Both

    First code change added

    A small change, such as a bug fix, a new test or a docs fix.

    • Change reviewed by your team
    • Automatic checks pass
    • Released your usual way
  6. Day 10Ours

    First work demo

    The engineer shows their work to your team after the first 2 weeks.

    • Promised work done
    • Demo to your team
    • Starting pace recorded
  7. Day 30Both

    Fit review

    A short review with your team lead: quality, communication, pace and anything to change.

    • Written fit review
    • Actions agreed
    • Replacement option still open

“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 coding assistants, used under your rules and review.

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

New Delhi and Ludhiana, inside your working day.

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

New Delhi

Project management, system design and client contact, including interviews, kick-offs, reviews and planning in your shared hours.

Runs from here
Project management · system design · client reviews
Working week
Monday to Friday, or Sunday to Thursday for Gulf clients
Time zone
IST, UTC+5:30, no daylight saving

Engineering office 02

Ludhiana

Engineering, testing and data work, with the same tools, review rules and security controls as New Delhi.

Runs from here
Engineering · testing · data
Working week
Monday to Friday
Time zone
IST, UTC+5:30, the same shift as New Delhi

Shared hours, on a 24-hour India clockPale band: team shift · Blue band: hours shared with you

  • United KingdomLondon · GMT (UTC+0) 4.5 h · 14:30–19:00 IST
  • EU CentralBerlin · CET (UTC+1) 5.5 h · 13:30–19:00 IST
  • GulfDubai · GST (UTC+4) 8.5 h · 10:30–19:00 IST
  • SingaporeSingapore · SGT (UTC+8) 5.5 h · 10:00–15:30 IST
  • US EastNew York · EST (UTC−5) 3 h · 19:30–22:30 IST, later shift

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.

Remote work, with planned travel

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.

≤ 2return trips per team, per year
A kick-off and one progress check. Any other trip needs a reason and your agreement.
4 yearsbefore we replace a laptop
We repair and reuse managed laptops within that period.
SCIreported every 2 weeks
SCI is the Green Software Foundation’s measure of software carbon. If you track it, we report our share.

Security

Security and ownership, agreed before anyone starts.

Adding engineers to your systems is a security change. The 6 controls below are in every contract, so your security team checks them once.

  1. Agreements signed first Each engineer signs confidentiality and ownership terms for your company before you meet them.
  2. Background checks We run them before any offer, as your policy requires. We keep the results for your audit.
  3. Only the access each role needs Accounts sit in your own log-in system, under your security rules, with live-system access only where needed.
  4. Company laptops, encrypted Your work stays on encrypted company laptops with updates and virus protection, never on personal devices or USB drives.
  5. Access ends in 1 working day When an engineer leaves, we remove all their access within 1 working day and confirm it in writing.
  6. Data handling agreed in writing The contract sets which data our engineers may use and where it may go. It also says if tests may use live data.

Reporting

Progress reports every 2 weeks.

A cycle is 2 weeks of work. Each report shows the same numbers, in good weeks and bad.

progress-report · Your company · cycle 24 Illustrative

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.

  • Work done as planned97%Done against promised, six-cycle average
  • Bugs in live use1Reaching users last cycle, down from 4 in cycle 19
  • Time to code review6 hTypical time from a change sent to its first review
  • Engineers who stay≥ 85%Target: engineers still on your project after 12 months

Risks and blockersCarried forward until closed

  • Open Test log-ins for payments still due from your provider; blocks the refunds work from cycle 25. Your finance team · raised cycle 23
  • Watching Test data for the move is thinner than live data. We are making sample records rather than copying customer data. Data engineer · raised cycle 24
  • Closed Unreliable checkout tests failed three releases. Set aside, fixed at the root and turned back on. Test engineer · closed cycle 24

“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.”

Project managerMonthly review · illustrative note

How often

Weekly
Written update: done, in progress, blocked, decisions needed.
Every 2 weeks
Demo and report to the people involved, run by the team.
Monthly
Review: numbers, quality, fit, team size and what changes next month.

Replacing an engineer, in 4 steps

  1. 01You askIn writing or at the monthly review, for any reason.
  2. 02We replyWithin 1 working day, with a handover plan for work in progress.
  3. 03ShortlistNew candidates, already tested. You can interview them if you wish.
  4. 04HandoverOld and new engineers overlap to hand over. You do not pay for the overlap.

Replacement target10 working days Set in each contract.

What you get

Everything else you get, and when it arrives.

Most items come with every option. The table shows each item’s format, timing and which options include it.

your-project / what-you-get.list Typical 9 included

What you get with Tech Workforce: each item’s format, when it arrives and which of the 4 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.

Kept in your own tools

Profiles, plans, tasks, documents and numbers live in your own accounts, so the record stays with you when we finish.

  • GitHub
  • Jira
  • Linear
  • Confluence
  • Figma

If you use a different tracker or wiki, we work in yours.

Reporting schedule

We set each report below at kick-off and name its owner.

Weekly
Written update: progress, blockers and decisions needed
Every 2 weeks
Review with a recorded demo of working software
Monthly
Review: numbers, quality, fit and risk
Quarterly
Team size and skills for the next quarter

Illustrative Timings are typical. We fix them for each project in a written scope. Ask for samples

What we measure

6 measures of progress, reviewed every month.

These show whether the extra engineers pay off: speed, promises kept, quality and engineers who stay.

  • Engineers in weeks

    Engineers work in your code within weeks, without months spent hiring.

    2–4 weekstypical start, with a first code change targeted for day 5

    See the first 30 days

  • Quality you can see

    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

    See the sample report

  • Scale up or down

    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

    Compare the 4 options

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.

  1. 01

    Time to first code change

    From an engineer’s first day to their first change, reviewed, approved and added to your code.

    ≤ 5working days

    Lower is better

  2. 02

    Planned work done

    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

  3. 03

    Bugs in live use

    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

  4. 04

    Time from change to live

    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

  5. 05

    Engineers who stay on your project

    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

  6. 06

    Releases that fail

    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

Engineers, teams and tech leaders who join your team in weeks.

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.

Categories
04
Offers
15
Plans
03
Not sure what you need? Tell us the problem

How to buy

  1. 01Pick offers. Ask about one, or add several to one enquiry.
  2. 02Choose a plan. A small job, a fixed project or ongoing help.
  3. 03Send your enquiry. We reply within one working day.

Browse by category

Timelines are typical. We write the scope before we quote.

01Dedicated teams

3 offers
Typical timeline: Start in 2–4 weeks

Dedicated product team

A lead, engineers, testers and a designer who own a goal in your product and work to your schedule.

What’s included

  • A team shaped to your goal
  • A lead and agreed goals
  • Works in your tools and meetings
  • Monthly progress review
  • All roles
  • Agreed goal
  • Your schedule

Best forCompanies with a clear product goal and no free team to build it.

Typical timeline: Start in 3–5 weeks

AI & data team

AI and data engineers who build and run AI features, such as document search, AI assistants and model testing.

What’s included

  • AI app and model engineers
  • Data work and running models
  • AI tests from day 1
  • Teaching your team to run it
  • AI models
  • Data
  • Running AI

Best forTeams with AI plans and no specialists in-house.

Typical timeline: Start in 2–4 weeks

Software testing team

Testers and engineers who build reliable automatic tests, so releases stop waiting on manual checks.

What’s included

  • A test plan
  • Screen and server tests
  • Tests on every change
  • Release quality reports
  • Automatic tests
  • Re-testing
  • Checks
  • Playwright

Best forTeams where releases wait on manual testing.

02Engineers by role

6 offers
Typical timeline: Start in 2–3 weeks

Frontend engineers

Engineers who build fast screens that everyone can use, in React, Next.js, Angular or Vue.

What’s included

  • Tested by senior engineers
  • Fast pages everyone can use
  • Code review and tests as standard
  • First code change in week 1
  • React
  • Angular
  • Vue
  • Vue.js

Best forProduct teams with more screen work than people.

Typical timeline: Start in 2–3 weeks

Backend engineers

Engineers for server code, data and tool links in Node.js, Python, PHP, Java, Go or .NET.

What’s included

  • Tested by senior engineers
  • Experience connecting systems and data
  • Security and testing as standard
  • First code change in week 1
  • Node.js
  • Python
  • Java · Go · .NET

Best forTeams with more server work than people.

Typical timeline: Start in 2–4 weeks

Mobile engineers

Engineers for iOS and Android apps, in Swift, Kotlin, Flutter or React Native.

What’s included

  • Apps for iOS, Android or both
  • Store release experience
  • Crash and speed checks
  • First code change in week 1
  • iOS
  • Android
  • Flutter · React Native
  • React Native

Best forCompanies growing a mobile app or starting a new one.

Typical timeline: Start in 2–4 weeks

Cloud engineers

Engineers who set up your cloud servers, automatic releases and Kubernetes, and keep live systems healthy.

What’s included

  • AWS, Azure or Google Cloud experience
  • Automatic set-up and releases
  • Monitoring and on-call support
  • Written how-to guides
  • Cloud
  • Kubernetes
  • Servers
  • AWS

Best forTeams whose developers lose too much time on servers.

Typical timeline: Start in 3–5 weeks

Data & AI engineers

Data engineers, AI engineers and data scientists: the roles that are hardest to hire.

What’s included

  • Tested on practical AI tasks
  • Experience with data, models and tests
  • Written notes, repeatable work
  • Teaching your team to run it
  • Data engineering
  • Models
  • AI apps
  • dbt

Best forCompanies building data systems or AI features without their own specialists.

Typical timeline: Start in 2–4 weeks

Product, design & testing roles

Product managers, designers and testers to complete a team that has engineers but lacks these roles.

What’s included

  • Finding and ranking what to build
  • Screen design in your style kit
  • Manual and automated testing
  • Works in your tools and meetings
  • Product
  • Design
  • Testing
  • Playwright

Best forEngineering teams missing product, design or testing roles.

03Tech leaders

3 offers
Typical timeline: Ongoing, set days each month

Part-time CTO

A senior technology leader for set days each month. They set direction, make system design decisions, guide hiring and update your board and investors.

What’s included

  • Tech strategy and plan
  • System and supplier decisions
  • Hiring plan and interviews
  • Board and investor technical updates
  • Part-time
  • Strategy
  • Board reporting

Best forStart-ups and growing companies not ready for a full-time CTO.

Typical timeline: Start in 3–5 weeks

Tech lead or architect

A senior engineer who guides your team day to day: setting standards, reviewing code, making design decisions and removing blockers.

What’s included

  • System decisions, written down
  • Code review rules
  • Mentoring for your engineers
  • Planning with your product team
  • Tech lead
  • Architecture
  • Mentoring

Best forTeams without a senior tech leader.

Typical timeline: Start in 2–3 weeks

Project management

A project manager who runs planning and reports, tracks risks and keeps everyone informed.

What’s included

  • Planning and team meetings
  • Tracking risks and blockers
  • Progress and speed reports
  • Regular updates
  • Planning
  • Risk
  • Reporting

Best forProjects with several teams or suppliers to coordinate.

04Flexible teams

3 offers
Typical timeline: Start in 2–4 weeks

Extra help for launches

Extra engineers for a launch, a system move or a busy time. Then we shrink the team as planned, with notes so knowledge stays.

What’s included

  • Team plan tied to your deadline
  • Fast onboarding
  • Written notes and handover
  • Planned reduction
  • Flexible team size
  • Handover

Best forTeams facing a fixed deadline with too few people.

Typical timeline: Start in 2–4 weeks

Try, then hire

Work with an engineer in your team first. Then hire them permanently, on terms set in the contract from the start.

What’s included

  • Hiring terms agreed up front
  • Trial period on your own work
  • Monthly fit review
  • A planned move to your payroll
  • Try before you hire
  • Permanent hire

Best forCompanies that want to hire permanently with less risk.

Typical timeline: 12–36 months, by agreement

Build-operate-transfer

We build and run a team for you. Then we hand its people, ways of working and knowledge to you on an agreed timeline.

What’s included

  • Team design and hiring
  • Run phase with a project manager
  • Ways of working, written down
  • Transfer plan for people and knowledge
  • Build
  • Your own team
  • Transfer

Best forCompanies building their own long-term engineering team in India.

Your enquiry

Tick “Add to enquiry” on any offer, choose a plan, then continue. Or enquire about one offer.

How we work with you

Ways to start, from a question to a quote.

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 call

What are you sending?

  1. 01

    About 2 minutes3 short answers

    For a first chat, a press request or anything not ready to plan yet.

    You get A reply from a named lead

  2. 02Recommended

    About 8 minutes5 short steps

    Goals, who it is for, budget and timing, so our first reply can outline the work.

    You get Options and prices after one call

  3. 03

    About 15 minutesYour documents attached

    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.

  • Typical length
    Ongoing · 3-month minimum
    Pricing
    Paid by time used
  • Typical length
    Ongoing · 6-month minimum
    Pricing
    Monthly fee
  • Typical length
    6–18 months
    Pricing
    Priced per written scope
Compare what each plan includes
What each plan includes and who it suits
PlanWhat you getBest for
SquadOur specialists join your team and work in your tools.
  • Named specialists matched to your plan
  • Works in your own tools and meetings
  • Grow or shrink the team each month
  • We teach your team from week one
Teams with a clear plan that need senior people fast
RetainerA monthly team that runs and improves what we built.
  • Team time set aside for you every month
  • Agreed response times for requests and fixes
  • A monthly review and a to-do list
  • Planned improvements, not only fixes
Monthly social media and ads, or care for live sites and apps
EnterpriseA large, long project with its own team and agreed response times.
  • A project director and a decision group
  • A team for each part of the work
  • Response times, reports and a list of risks
  • Security, legal and purchasing checks in the plan
Large companies making changes across markets, brands or business units

Questions

8 questions to ask before you sign.

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

  1. Q-01 Starting

    How fast can an engineer start?

    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

  2. Q-02 Starting

    Can we interview candidates ourselves and say no?

    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

  3. Q-03 Managing

    Who manages the engineers day to day?

    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

  4. Q-04 Managing

    Which time zones do you cover?

    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

  5. Q-05 Quality

    How is this different from a recruitment agency?

    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

  6. Q-06 Quality

    What happens if someone is not the right fit?

    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

  7. Q-07 Security

    Who owns the work, and how is it kept safe?

    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

  8. Q-08 Contracts

    Can we hire the engineers permanently?

    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

Ask us for the evidence

We can send any of these before you sign, so you see what the work looks like first.

  • A sample progress reportAn example of what you receive
  • A sample test scorecardShowing what we test
  • Our answers to your security questionnaireReturned within 5 working days
  • A call with a leadWith the lead who would run your team

Still have a question?

Send the roles, tools and start date. We reply in writing.

Start a project Try the team builder

Tell us what you need built.

You will talk to the lead who would run your work.

Book a call

Three ways to start

We always agree a written scope and price before work begins.

Choose one of the three ways above