Co-Dev Strike Team

Test a game co-development team in a 4-week pilot

A Lead-level strike lead and 2–⁠5 Unreal or Unity specialists work inside your Perforce and Jira for a 4-week pilot. Build security is set up before day 1.

Build my squad Book a scoping call

NDA first. Upload your Jira task list after signature.

Fig. 01Co-Dev Strike Team

  • 72hfree hold
  • 4working days to start
  • 48hshortlist
  • 9practices
In short

Real milestone tasks, inside your Perforce and Jira, with a scorecard you agree before the first commit.

Co-Dev Strike Team is a Remote Pro Ai game co-development team that starts with a 4-week pilot. A Lead-level strike lead and 2–⁠5 Unreal or Unity specialists work inside your Perforce and Jira on real milestone tasks, with build security configured before day 1 and a conversion review in week 3.

What happens in the 4-week co-dev pilot

Before week 1, you sign the NDA, upload your milestone tasks as a Jira export, and the Squad Builder maps them to roles. You review 2 candidates per role, with credits and code samples, and agree the pilot scorecard.

WeekFocusOutcome
1Onboarding and first tasksEngines compiled on your build; first task picked up by day 3
2Velocity baselineTasks closed, review times and build health measured against plan
3Conversion reviewScorecard against success criteria; proposal for a monthly team
4Milestone deliveryPilot tasks completed; convert, extend or close with a clean handover

  • Typical pilot tasks

    • A complete gameplay feature, such as combat, inventory or a quest.
    • An Arabic and English UI system.
    • A level blockout with its gameplay logic.
    • A bug-fix sprint with a target number of closed issues.
    • A performance pass on a named platform.

  • Who it is for

    • Studios facing a publisher milestone, such as a vertical slice, within 2–⁠3 months.
    • Publishers adding capacity to an external studio’s roadmap.
    • Teams short on UE5 gameplay, netcode, tools or technical art.

Game co-development team compositions

Every strike team has a Lead-level strike lead who owns delivery, code quality and the weekly producer report. Engineers are Mid, Senior or Lead, matched on engine depth and shipped credits.

Strike teamTypical compositionTypical tasks
GameplayStrike lead, 2 Senior gameplay engineers, technical artistAbilities, AI, combat, camera and feel
MultiplayerStrike lead, netcode engineer, backend engineer, QAReplication, rollback, matchmaking, dedicated servers
Tools and pipelineStrike lead, 2 tools engineersEditor tools, build automation, content validation
Unity mobileStrike lead, 2 Unity engineers, QAFeatures, performance, store-ready builds
Vertical sliceStrike lead, 3–⁠4 engineers, technical artistA publisher-ready slice on a fixed date

Perforce and Jira integration, least privilege first

Perforce
Engineers mapped to groups with access to named streams only, through your VPN.
Per-user audit
Every sync and submit logged; unusual volumes raise an alert.
Jira
Project access set by you; tasks synced to Client OS for reporting.
Reviews
Your code-review rules; your engineers approve merges to protected streams.
Builds
Your build farm and CI; broken builds counted in the weekly report.
Channels
A shared Slack, Teams or Discord channel with your producer.

Access is approved in the Client OS integration panel by your administrator, and the security plan, including managed devices and watermarking, is in place before engineers sync for the first time.

The pilot scorecard you agree on day 0

  • Milestone tasks closed against the plan agreed for each week.
  • Build breaks caused by the strike team, with a target of 0.
  • Pull-request review turnaround, measured in working hours.
  • Defects reopened after acceptance by your QA.
  • Producer satisfaction score at the end of weeks 2 and 4.

The week-3 review compares results with these criteria. If you convert, the same people continue as a monthly strike team, often with 1 added QA engineer. If you end, offboarding happens the same day: access revoked, devices wiped and an IP handover certificate issued.

Co-dev pilot pricing

Your itemised proposal states the fixed price, and we email it within 2 minutes of your request. Most pilots run in the reservation lane: an instant reservation, a quotation PDF for your purchase order, and the bench held for 7 days against a refundable deposit. If the monthly team starts within 30 days of the pilot, 50% of the pilot fee is credited.

  • What shapes your quotation

    • Engine and platform: console work needs devkit-experienced engineers.
    • Security level: cloud workstations and watermarking add to the setup.
    • Commitment after the pilot: discounts for 6 and 12 months (rates in your quote).
    • Team size and the seniority mix.
    • On-site days with your studio in Riyadh, Dubai or elsewhere.

  • Guarantee

    • Replace any engineer for any reason: a replacement starts within 4 working days; the full handover completes in under 14 days.
    • MSA, pilot SOW and code and art IP assignment signed before payment.
    • Same-day offboarding and an IP handover certificate at the end of the pilot.

Credits behind the strike teams

Strike leads come from our games practice that built Case G-01, a multiplayer launch title for a game studio in Riyadh: authoritative servers with rollback netcode, under 100 ms p95 latency in-region and first-pass platform certification. Candidate profiles show each engineer’s shipped titles, as far as NDAs allow.

Read Case G-01

Frequently asked questions

Book a scoping call

20 minutes with an Account Director. No sales script.

A co-dev strike team is a small group of external game developers who work inside a studio’s own pipeline on a defined set of milestone tasks. At Remote Pro Ai it means a Lead-level strike lead plus 2–⁠5 Unreal or Unity specialists, using your Perforce, Jira, build system and review rules from the first week.

Co-development succeeds or fails on fit with your pipeline and producers, which a CV cannot show. A 4-week pilot on real tasks gives you measured evidence: tasks closed, build health and review times. You decide at week 3 whether to convert, with no long contract signed before the team has proved itself.

Yes. You see 2 candidates per role, with shipped titles, engine depth scores and code samples, and you can book a technical interview with any of them. Candidate names and full profiles are released after the NDA. Interviews are scheduled in your time zone, typically within 2 working days.

Devkits stay under your platform-holder agreement. Engineers use kits you ship to a controlled location or remote kits inside your network, and console roles start within the same 4 working days, counted from the date your platform holder grants devkit access. The Squad Builder flags devkit requirements when it maps your tasks to roles.

You choose to convert, extend or close. Conversion keeps the same people as a monthly strike team under a short amendment with 30 days’ notice. Many studios add QA or a technical artist at this point. If you close, access is revoked the same day and you receive an IP handover certificate.

Credits follow your studio’s policy. Most studios credit external developers under the partner’s name or individually, and we ask only that the credit is accurate. If the title stays under NDA, we describe the work by genre and platform in our materials and never name the game without your consent.

All questions, by topic

Start today

4 working days

Your team can be working within 4 working days of signature.