Instead of publishing one fixed price list, we choose a practical engagement model based on scope, materials, existing systems, and deliverables.
Engagement
We do not need to publish one fixed price to make the first step clear. We first align the type of engagement that fits the need.
Short advisory work for technical direction, implementation choices, or existing project review.
Typical deliverables
Factors that affect a quote
A one to four week effort to validate a game idea, workflow, screen, or data flow.
Typical deliverables
Factors that affect a quote
Design and implement a clearly separated feature for a new or existing project.
Typical deliverables
Factors that affect a quote
Ongoing technical support, maintenance, improvement, and investigation over a defined period.
Typical deliverables
Factors that affect a quote
Budget
The first discussion can start by clarifying limits, priorities, and staged delivery instead of forcing an exact fee too early.
We separate what can be judged through a short consultation or small discovery scope.
We sort must-have work, deferred work, and risks inside the available budget range.
Discovery, prototype, feature development, and maintenance can be split into separate steps.
We check whether ongoing review, improvement, or maintenance makes sense based on frequency and scope.
Quote
The first discussion is used to align both fee assumptions and the scope that should be included this time.
Target features, number of screens, integrations, and the amount of code or workflow to review.
Specifications, existing code, accounts, test environment, and tools currently in use.
Meeting frequency, review builds, review cycles, and expected correction speed.
Documentation, operation notes, handoff requirements, and assumptions for future support.
Examples
Even when the request is still rough, these examples make it easier to choose a first step.
Review achievements, leaderboards, localization, build steps, and common release preparation gaps.
Likely modelSpot technical consultation / small discovery
Build the smallest scope needed to judge feel and the game loop, not a near-final product.
Likely modelSmall prototype
Clarify work frequency, input files, review points, and start with a small improvement.
Likely modelFree consultation -> scope outline -> small improvement
Confirm existing code, responsibility boundary, review method, and handoff conditions.
Likely modelFeature-based development / monthly support
Limited Offer
To make the first conversation easier, we define what is included before a detailed quote or paid engagement begins.
Contact us about development needs, technical challenges, or collaboration opportunities.
