Quick overview
PC and consoles first, and I also work with mobile, VR/AR, and web builds when it supports the product.
Snapshot: built a playable demo scene where one level lets you try jumping, sliding, double jumps, swimming, gliding, and moving platforms.
Scope: Single location with a clear route, showcase challenges for each mechanic, polished controls for gamepad and keyboard.
Outcome: Quickly validate feel and difficulty on PC and consoles; highlights what to expand next.
Timeline: 1-2 weeks
Download demoSnapshot: demonstrated the skeleton of an RPG - movement, inventory, simple abilities, dialogues, and combat inside a sandbox level.
Scope: Quest route, baseline missions, inventory and upgrade UI, controller-friendly input.
Outcome: Shows the explore -> fight -> reward loop and gives a foundation for extending content and balancing.
Timeline: 2-3 weeks
Snapshot: compact linear scene with atmosphere and a couple of scripted scares (lighting, audio, chase).
Scope: Readable landmarks, audio and lighting polish, lightweight puzzles, safe zones, and tension peaks.
Outcome: Validates tone and pacing: when the player feels pressure versus relief, and where to add content or increase tempo.
Timeline: 1-2 weeks
For you: clear milestones, reliable schedule and budget forecasts, regular demos.
For you: clear game rules and predictable scope of work.
For you: choose the right model (co-op, sessions, matchmaking), implement server logic, guard against obvious exploits.
For you: readable locations, tuned pacing and encounter scenarios, consistent visual language.
For you: clear first-time experience, fewer early drop-offs, better retention.
For you: stable frame rate, fast startup, fewer bugs in the release branch.
For you: fair economy and transparent revenue levers without hurting gameplay.
For you: fast answers, outside perspective, actionable next steps.
I am a Unity developer with game and level design experience. I enjoy projects where tight controls, readable levels, and solid performance matter. The process stays transparent: short calls, regular builds, and clear reports.
I fit into existing pipelines: task boards, code reviews, builds, releases. If needed, I set up the process from scratch—task tracking, prioritisation, branching, build cadence. You get not just results but a tidy project that is easy to support and extend.
goals, platforms, timeline, risks.
lock scope, milestones, and budget.
you see progress and share feedback.
source files, documentation, final tweaks.
bug fixes, improvements, or the next sprint as needed.
audit/prototype of one key feature
2-5 days
playable slice with a level and interface
1-3 weeks
content, multiplayer/porting, optimisation
3-6 weeks
Milestone-based payments with a 40-50% advance. Final quote after a short brief.
If your audience is on PC, we start there while factoring in console requirements (controls, performance). Mobile joins when it helps the product.
Yes. We build a small playable slice with a clear testing goal and success metrics.
Yes. From co-op to dedicated servers—we will align on the model, budget, and expected load.
We set FPS and load-time targets, test on target hardware, and track improvements.
Source files, documentation on adding content, known limitations, a final call, and optional post-launch support.
Tell me a bit about the project—platform, genre, rough timeline. I will reply with suggested next steps and a ballpark budget.
