Work that fits the project you already own
- Features: add gameplay or extend an existing system.
- Customisation: adapt mechanics, interfaces or game content to new requirements.
- Completion: identify unfinished work and define a realistic next version.
- Bugs: investigate reproducible problems and their underlying causes.
- Performance: review reported issues on the affected devices and situations.
- Updates: scope new content and ongoing development as separate agreed work.
Understand the condition before confirming the scope
An inherited game may contain undocumented decisions, dependencies or partially completed systems. A public description cannot establish code quality or the cause of a performance issue. We first clarify the current state, the expected behaviour and the access needed for an agreed investigation. Detailed technical investigation is quoted according to the work required.
Make the first conversation useful
- Share a public game link if one exists.
- List the most important changes separately from nice-to-have ideas.
- For bugs, describe the steps, expected result and actual result.
- Tell us about existing players, saved data and important integrations.
- Confirm who owns the code and assets, and who can authorise access.
Protect what already works
Discuss a safe working copy, backups, test data and release responsibilities before changes begin. Existing player data and live systems require particular care. We will define a review and release approach suited to the project; we cannot guarantee every inherited project can be repaired within a particular budget.