Code Wizards' CEO publishes five rules for external development partnerships

Code Wizards' CEO published five rules for external development partnerships. The rules draw on 24 years of backend engineering and live-ops co-development work. Trust, flexibility, communication, declared weaknesses and team culture anchor the framework. Early-stage production stays invisible to clients, with no timesheet able to prove the work.

Trust functions as the only metric in early production
Early-stage production work is largely invisible, compared to a house's unseen foundation.
No timesheet can show the real effort behind early-stage engineering, the CEO says.
A hesitant client signed within 15 minutes of checking Code Wizards' reputation with a past partner.
"The more you build up trust with the client, the more it's likely that any feedback given to them will be listened to" - Code Wizards CEO

A two-week pause reshaped a flagship mechanic
A renowned studio paused production two weeks to fix a flawed wall-running mechanic.
The pause disrupted Code Wizards' schedules but the fix lifted the game's Metacritic score.
Neither team regretted the change despite the rescheduling nightmare it caused, the CEO notes.
"Games evolve over time, and everybody on the team needs to be willing to bend and flex with them" - Code Wizards CEO

Reporting cadence differs by partnership maturity
A new driving-game partnership receives fortnightly project-health reports on milestones, morale and blockers.
A long-standing partner gets exception-only updates, with silence implied as on-track.
Communication turns more formal as a project accelerates toward launch, the CEO says.
"Communication style will change as the game goes on" - Code Wizards CEO

Where the framework leaves technical governance undefined
Code Wizards declined optimization work for an existing client and referred them to another partner.
Strengths and weaknesses stay self-declared, with no externally verified scorecard mentioned in the framework.
None of the five rules names a formal milestone-verification or audit checkpoint for co-development work.
Risk control instead rests on reputation checks and a client's early concern-flagging.
What this means
For Publishers & Developers: Write independent milestone-verification checkpoints into co-dev contracts before the first engineering sprint.
For Service Vendors: Pitch third-party code-audit and delivery-verification services to studios that vet partners through referrals.
For Investors & VC: Add external-partner audit rights to diligence on studios outsourcing backend or live-ops work.