Game concept & planning
Define the player, objective, rules and winning conditions. A focused brief makes it easier to decide what belongs in the first playable version and what can wait.
Turn your game concept into an interactive experience. MayaWeb brings gameplay, design and development together to help you create a game shaped around your audience, your budget and your vision.
Game development turns an idea into rules, visuals, interaction and code that people can play. It is for founders validating a concept, brands creating an interactive experience, and teams developing a focused game. MayaWeb’s published packages cover small 2D projects on one target platform.
Define the player, objective, rules and winning conditions. A focused brief makes it easier to decide what belongs in the first playable version and what can wait.
Explore a small version of the core mechanic before adding a complete game around it. Use the prototype to review controls, challenge and the feel of play.
Connect gameplay logic, scenes and interactions into a playable build. Choose a package around the number of levels and the systems your game needs.
Make starting, pausing, restarting and understanding the game feel clear. Menu and scoring systems are included in the Standard package; other interfaces are scoped with your brief.
Give players a way to move through the game and return to their progress. Progression and save systems are included in Premium, with their exact behaviour agreed before development.
Review the agreed gameplay on the target platform, record issues and refine the build. The package includes testing and delivery; launch services are discussed separately.
Three Game Development packages. Starting prices in USD, quoted per project. Final scope and payment milestones are confirmed in your proposal.
For founders testing a small game idea.
For a compact game with several levels.
For a larger 2D experience with progression.
One target platform. Multiplayer, paid assets, online backends and store publishing are quoted separately.
A playable version makes feedback more useful. You can review how the game feels before committing to more levels, art or features.
Let people interact with a challenge instead of only reading a message. A game can support entertainment, learning or a branded experience when designed around the right audience.
A defined core mechanic and level count help keep the initial project manageable. New ideas can be prioritised against the approved scope.
Testing gives you a practical starting point for refinement. Player feedback can guide later decisions about difficulty, onboarding and additional content.
Start with your idea, audience and budget. Agree the platform, deliverables and boundaries so everyone works toward the same version of the game.
Plan review points around playable milestones. Share feedback on the experience while changes can still be discussed and prioritised.
Know what your package includes. Additional levels, assets, online features and publishing are discussed before they become extra commitments.
Confirm the build format, included files and delivery requirements in your proposal. Discuss any future support separately so responsibilities remain clear.
A game needs a satisfying interaction at its centre. Our starting point is the player’s action, the response it creates and the reason to try again.
Levels, menus and rewards should support the experience. We connect the agreed systems around the core mechanic instead of allowing the feature list to define the game.
MayaWeb brings a broader design and digital development perspective to the project. Visual choices and interface decisions are considered alongside the practical requirements of implementation.
These are directions to explore in your brief, not examples of completed client projects. Your chosen mechanic and content determine what fits a package.
Short play sessions, clear goals and a mechanic that is easy to understand. Discuss score chasing, timing or a simple obstacle challenge.
Create a challenge around patterns, sequencing or problem solving. Define difficulty and feedback so each level feels intentional.
Explore movement, obstacles and discovery in a 2D setting. Level count, character interactions and artwork determine the project scope.
Build an interaction around a lesson, product or campaign. Start with what the player should understand and keep the game’s purpose clear.
Share your reference games, intended audience, target device and budget. Agree the first release and the features outside it.
Work through the core action and basic rules. Review an early playable direction before expanding the experience.
Develop the approved levels and systems. Review interface, gameplay feedback and content at agreed milestones.
Check the main player journeys and agreed device requirements. Prioritise issues, retest changes and prepare the final build.
Receive the agreed build and handover. Scope publishing, future features or ongoing support if your project needs them.
Discuss a game people can access through a website. Define the supported browsers, input methods and loading requirements.
Define Android or iOS requirements, touch controls and the device range. Store accounts and submission are separate from the published packages.
Plan keyboard or controller input and the intended operating system. Agree how the build will be installed, tested and delivered.
Each published package includes one agreed target platform. Engine selection follows the brief and technical assessment. Console releases, cross-platform ports, 3D, AR/VR and specialist engine requirements need a separate feasibility review and quote.
An existing project may need a specific feature, a new level or a production handover. Share your current build, documentation and technical requirements so we can assess the work before committing.
Discuss a custom project ↗Multiplayer, online accounts, backends, paid artwork, audio licensing and store publishing are outside the listed packages. Ongoing updates, analytics, in-game purchases, porting and live operations also require an agreed scope.
Costs depend on the game’s complexity, assets, platforms and delivery requirements. No download, revenue or player-retention result is guaranteed.
MayaWeb’s Basic package starts at $999 USD, Standard at $1,999 USD and Premium at $3,999 USD per project. These are small 2D game packages for one target platform. Your final proposal confirms scope, cost and payment milestones.
Yes. Basic covers a small 2D prototype with one core gameplay mechanic, one playable level, testing and build delivery. It provides a focused way to explore your concept.
The timeline depends on the mechanic, level count, asset readiness and review process. We confirm the schedule after reviewing your brief; the package price does not imply a fixed delivery time.
The engine is selected after reviewing the platform, gameplay and technical requirements. If you have an existing Unity, Unreal, Godot or web-based project, include that requirement in your enquiry so suitability can be assessed.
Paid assets and store publishing are quoted separately. The proposal should state which artwork, audio, files and platform services are included. Store fees and approval requirements must also be accounted for.
These are custom requirements rather than included package features. Share the player count, online systems or support needs so we can review feasibility and provide a separate scope.
Share a short concept, reference games, target platform, desired features, available artwork, budget and intended launch window. If you already have a game, describe its current state and the help you need.
Tell us what you want to build. Let’s define a playable starting point.
Plan my game ↗