Let’s talk

Our process

From first spark to launch day — and beyond.

Eight clear phases, two-week sprints and a working build in your hands every cycle. No black boxes, no surprises — just steady, visible progress.

See the journey
  1. Phase 01 1–2 weeks

    Discover

    Every great product starts with understanding. We run collaborative workshops to define the problem, the audience, the business model and what success looks like.

    What we do

    • Stakeholder workshops
    • Audience & competitor research
    • Feature prioritisation
    • Risk assessment

    What you get

    • Product brief
    • Prioritised feature list
    • High-level estimate
  2. Phase 02 1 week

    Strategy & plan

    We define the technical architecture, choose the right platforms and engine, and break the project into milestones with transparent cost and timing.

    What we do

    • Technical architecture
    • Platform & engine selection
    • Milestone planning
    • Team allocation

    What you get

    • Product roadmap
    • Architecture document
    • Fixed milestone plan
  3. Phase 03 2–4 weeks

    Design

    Our designers map user flows and craft the interface. For games, we define the core loop, game design document and art direction.

    What we do

    • User flows & wireframes
    • UI & visual design
    • Game design document
    • Art direction & style frames

    What you get

    • Interactive prototype
    • Design system
    • GDD & art bible (games)
  4. Phase 04 1–3 weeks

    Prototype

    Before full production we build a clickable prototype or a playable vertical slice, test it with real users and refine until it clicks — or the fun is found.

    What we do

    • Clickable prototypes
    • Playable greybox / vertical slice
    • User & playtesting
    • Iteration on feedback

    What you get

    • Validated prototype
    • Playtest report
    • Refined scope
  5. Phase 05 6–20 weeks

    Build

    Development happens in agile sprints with a working demo at the end of each one. Code is reviewed, tested and integrated continuously so quality is built in, not bolted on.

    What we do

    • Agile two-week sprints
    • Code reviews & CI/CD
    • Backend & integrations
    • Sprint demos

    What you get

    • Working builds every sprint
    • Source code repository
    • Technical documentation
  6. Phase 06 2–4 weeks

    Test & polish

    Our QA team tests across a matrix of real devices and OS versions. We profile performance, fix edge cases and run beta programmes via TestFlight and Google Play testing tracks.

    What we do

    • Real-device QA matrix
    • Performance profiling
    • Accessibility checks
    • Closed beta testing

    What you get

    • QA report
    • Performance benchmarks
    • Release candidate
  7. Phase 07 1 week

    Launch

    We prepare store listings, screenshots and metadata, manage review submissions and coordinate a smooth, staged release — with monitoring in place from minute one.

    What we do

    • Store listing & ASO
    • Review submission
    • Staged rollout
    • Launch monitoring

    What you get

    • Live app or game
    • Store assets
    • Launch dashboard
  8. Phase 08 Ongoing

    Grow & LiveOps

    Launch is the beginning. We analyse behaviour, run experiments, roll out new features and LiveOps events, and keep everything updated for new OS releases.

    What we do

    • Analytics & experimentation
    • Feature updates
    • LiveOps events & content
    • Maintenance & OS updates

    What you get

    • Monthly insights report
    • Regular releases
    • Growth roadmap

How we collaborate

You’re never in the dark.

We work in the open, with the same tools and rituals as the best product teams.

Direct communication

A shared Slack or Teams channel with the people building your product — no middlemen.

Full visibility

Live task boards in Jira, Linear or ClickUp, so progress is always visible.

Demo every sprint

A working build to try on your own device every two weeks.

Your repository

Code lives in your GitHub, GitLab or Bitbucket from day one.

Typical timelines

How long will it take?

Every project is different, but these ranges are typical for our engagements. After discovery you get a detailed, milestone-based plan.

  • Hyper-casual game 4–8 weeks
  • App MVP 8–12 weeks
  • Casual game 3–6 months
  • Full-featured app 4–6 months
  • Mid-core game 6–12+ months

FAQ

Process questions.

Can’t find what you are looking for? Reach out and a real person will get back to you.

Ask us anything
How involved do I need to be?

As much as you like. Most clients join a weekly call and the sprint demo; we handle everything else and reach out whenever a decision is needed.

What if requirements change mid-project?

Change is expected. Because we work in sprints, we can re-prioritise the backlog at any sprint boundary and show you the impact on time and budget upfront.

How do you ensure quality?

Code reviews on every change, automated tests, continuous integration and a dedicated QA phase on real devices before each release.

Ready when you are

Let’s start with a free discovery call.

Tell us about your app or game. We’ll reply within one business day with next steps — no obligations, no jargon.

Start your project [email protected]