Eight Stages From
First Call To LiveOps
The same route runs for a hyper-casual prototype and for a mid-core title with servers. The depth of each stage changes. The order and the deliverables do not.
First Call
Twenty minutes about the concept, the audience and the numbers you need to hit. No documents required, no charge, and no sales script.
Concept & Scope
Core loop, feature list, platforms and technical requirements go into a written scope, with a fixed estimate per stage attached to it.
Prototype
A playable build that tests the loop before art production starts. If it is not fun here, no amount of polish later will fix it.
Art & Production
Style guide, asset pipeline and full production in two-week sprints, each ending with an installable build and a written summary.
QA & Devices
Manual and automated passes across a device matrix that includes the low-end hardware most of your players will actually be holding.
Soft Launch
A limited release with full event tracking, so retention, funnel and cost data arrive before the global marketing budget does.
Global Release
Store listings, creatives, ratings, privacy declarations and submission, handled by us under your accounts and your ownership.
LiveOps
Event calendar, seasonal content, balance passes and crash response under an agreed reaction window after the launch week.
You Always Know Where
The Build Stands
If a decision was not written down, it was not made. Everything that affects scope, schedule or budget goes into writing, so it can still be reviewed a year later when nobody remembers the call.
One Point Of Contact
A project lead who knows the build, attends every review and answers inside the working day. No account manager relaying messages to a team you never meet.
Written Sprint Summaries
Every sprint ends with an installable build and a short written note: what changed, what is next, and what needs a decision from you before work continues.
An Open Board
The task board is shared from day one. Backlog, current sprint and blockers are visible without asking anyone for a status update.
What Every Build Passes Before You See It
40+
Device Test Matrix
Builds are verified on current and older iOS and Android hardware, including low-memory devices and the screen sizes that break layouts first.
24h
Crash Response
Under a support agreement, crashes affecting a meaningful share of sessions are acknowledged and triaged inside the agreed window.
100%
Documented Handover
Architecture notes, environment setup, build instructions and third-party credentials handed over in writing, so another team could continue without us.
Pick The Shape Of
The Collaboration
The model is agreed during scoping and can change between phases. Most teams start with a fixed scope release and continue on a LiveOps retainer.
Fixed Scope Build
A defined product, a written scope, a fixed price per stage. Best for prototypes, first releases and applications where the destination is already agreed.
- Written scope and stage plan
- Fixed price per stage
- Installable build every sprint
Dedicated Team
Designers, artists, engineers and QA assigned to your product monthly. Best for live titles and roadmaps that will change more than once.
- One unit, one roadmap
- Monthly capacity, quarterly planning
- Direct access to the people building it
LiveOps Retainer
For products already earning. Content calendar, balancing, store compliance and an agreed crash response window every month.
- Agreed crash response window
- Scheduled events and content drops
- Monthly cohort and revenue reporting