The project was inherited
Ownership changed, documentation is incomplete, and the real dependency map is unclear.
Unity project review & repairs
Problems with your Unity project? Find out what needs fixing.
Taken over a Unity project, lost your previous developer or found that the game or app no longer works? I check the source code, how to run the project and the affected devices, then explain what needs fixing. You can use the report with your team or agree the repairs with me.
20–40hTypical first assessment
Build firstEvidence before promises
NDABefore confidential access
Hands-onRemediation available
When to start here
The project exists. Confidence does not.
A review helps when you need to decide what to fix or develop next but do not yet have a reliable picture of the project’s condition.
The build is fragile
It works on one machine, fails in CI, or depends on undocumented local setup and manual steps.
Performance is blocking release
Frame time, memory, loading, crashes or device-specific behavior need evidence-led diagnosis.
Integrations keep breaking
Connections to server services, third-party tools, phone features, Steam or VR devices keep causing problems when you prepare an update.
Changes have unpredictable effects
Tightly coupled systems make small fixes expensive and regression-prone.
The roadmap is based on guesses
The team needs a defensible finish, refactor or rebuild decision before scaling effort.
Concrete deliverables
Know what works. Decide what to fix.
The assessment is structured around what the product owner needs to decide and what the engineering team needs to execute next.
- 01
What works and what prevents the project from running
Build status, environment notes and clearly recorded blockers.
- 02
Architecture map
Core systems, dependencies, ownership boundaries and critical coupling.
- 03
Prioritized risk register
Findings ranked by impact, likelihood and delivery urgency.
- 04
Performance & integration findings
Measured evidence from the relevant platform, device or headset.
- 05
Technical direction
A reasoned finish, refactor or rebuild recommendation—not a reflexive rewrite.
- 06
A repair plan divided into clear stages
Milestones, acceptance criteria, dependencies and useful next decisions.
The review focuses on the most important questions we agree. A 20–40-hour review cannot find every bug in a large existing project, so the report also explains what was checked and what remains uncertain.
How the assessment works
Understand the work before investing in repairs.
- 01
Brief & access
Clarify the product, target platform, current blocker and success criteria. Arrange an NDA before repository access when needed.
- 02
Check whether the project runs
Run the project, reproduce the issue and document the actual build path before making delivery promises.
- 03
Inspect & measure
Trace architecture, dependencies, data flow, integrations and performance on the relevant target.
- 04
Decide & sequence
Recommend what to fix first, explain the options and suggest a manageable first piece of work based on the findings.
The core decision
Finish, refactor or rebuild?
The answer should follow product constraints and evidence—not taste, panic or sunk cost.
Finish01
Preserve the working core.
When the architecture is serviceable, focus effort on blockers, validation and release-critical gaps.
Refactor02
Improve the parts causing problems.
When specific modules create risk, isolate and repair them without destabilizing the whole product.
Rebuild03
Use only when evidence supports it.
A rewrite becomes defensible only when the current structure cannot meet the product’s required outcome.
Relevant proof
Delivery experience behind the assessment.
Architecture decisions are grounded in hands-on product delivery across shipped PCVR, production mobile software and systems-heavy games.
Shipped Steam PCVR
Reach The Beat
Sole Unity engineer and technical owner across architecture, gameplay and XR systems, tooling, builds, hardware validation and release.
View Steam proofProduction Android / iOS
Confidential mobile product
Sole Unity client engineer and mobile architect for complex UI, backend-dependent flows, device validation and native integrations.
Product identity withheld · NDA-safe
Systems-heavy games
Interconnected product systems
Architecture and implementation across progression, saves, localization, analytics and data-driven content systems.
5+ years commercial Unity · 5.0 public Upwork rating
Questions before access
Clear first steps.
01Can you take over an existing or abandoned Unity project?
Yes. I first check whether the project runs, review its code and identify what can be repaired or reused. I recommend a first step before estimating a larger piece of development.
02What access do you need?
For the assessment itself: usually the repository, Unity version, a representative build, available documentation and access to the target platform or hardware context. Start with a high-level outline. We can agree an NDA before you share sensitive details or grant repository access.
03Will the assessment tell us whether to finish, refactor or rebuild?
That is one of its main purposes. The recommendation is tied to evidence, product constraints, delivery risk and the definition of success—not a blanket preference for rewrites.
04Can you implement the roadmap after the audit?
Yes. Your team can use the report, or we can separately agree work on fixes, selected code improvements, performance, service connections or release preparation. The review does not commit you to further work.
05How large is the first engagement?
We start with a paid review. For an inherited project or one with unclear problems, 20–40 hours may be appropriate. We agree the hours, fee, main questions and report before starting. You receive a record of what works or prevents the project from running, the most important risks and a proposed first repair stage. Development is estimated separately.
Start with the blocker
Tell me what keeps breaking.
Have a limited budget? Tell me your priority and the range you’re comfortable with. I’ll be clear about a realistic first step.
Confidential from the first conversation
I count contact interactions in aggregate, without visitor IDs or message contents.
Need a different kind of help?
All servicesBuild a game
Game Development
Build a non-game app
App Development
Keep a product moving
Part-time Unity Technical Lead
Revive & retest a product
Updates & Support for Older Unity Projects
Connect AI to a real workflow
AI Integrations & Private AI Trials
Bring the right skills together
Development with Creative & Testing Specialists
Check quality before the next step