FAQ

Yes we do, we work with teams at all sizes and all stages of development.

Yes. We are based in Australia but work online with local, national, and international clients.

Co-development means we work along side you to understand your problem, find the right solution, and include you in the development process. Not just agreeing on terms and deliverables and vanishing.

Absolutely, we love to work iteratively on designs with stakeholder feedback and refinement. When the project is early or open, we can assist with UX, design, and prototyping.

We'll make time to determine how we can help you with your projects. How quickly we can get started on the project itself will vary with our current workload and nature of your project. Our typical 'lead time' ranges from 2 to 6 weeks.

The details will depend on what service you're after. But to start conversations we only need an email to set up a call. After that we usually exchange NDAs or Software Developer Agreements before determining the manner and scope of our engagement.

Absolutely! We choose to work in an agile structure when we can, so we can start where ever you like and with no obligation to continue.

You can check out our team page to see some of our staff. But this will depend on current project load, and skill sets of our team members.

We choose to work in a 2 week interval in a scrum style when possible. So you set the direction, the current goals/tasks and get progress at least once every 2 weeks to redirect us. But we're flexible if you want that more frequently we can do it.

We endeavour to respond within 2-4 hours. This will often be faster depending on your preferred communication platform (e.g. Discord, Slack, etc.)

It depends on project structure, but we can typically manage these within or between sprints. If we're engaged in an agile/scrum style project this is expected and encouraged at the end of every interval. Even in more milestone based projects we'll account for variability and iteration in the milestone deliverables.

Absolutely. Whether your project has been on the shelf, or your team just needs help breaking past blockers, we can help get things moving

We perfer to estimate and bill on time and materials needed for the project, capped within an interval period. Most commonly a 2 week sprint.

We do. This may depend on your preferences, budget, procurement requirements, or the nature of your project.

Our estimates will include a breakdown of all costs by source, including where we anticipate our time will be spent. We may need to charge fees or pass on costs for additional items such as travel, cloud hosting, or special hardware if a project requires it. We will confirm these with you ahead of time, so there won't be any hidden costs or surprises. Support beyond the end of a project is quoted on a time and materials rate, and only ever occurs at your request.

Absolutely. This is the most common way that we work with our clients, adopting and embedding into their existing processes, tools, and infrastructure.

We primarily let the project goals drive technology. Beyond that we factor in the familiarity of the project team with the tech, harmony with existing tech choices, and client preferences.

We'll work through that with you during our initial engagement, scoping and requirements phase.

Yes we can. It is more common than not that we sign mutual NDA, and Software Developer Agreement.

You do. It's your project, we're just helping you make it. It's your code, your assets, your ideas. We give all rights to what we make for you, to you. We don't want to be your competitor, we're your partner in this.

Yes, you can find some in the Projects section of this website. We can provide more specific references on request.

We will always try to resolve or rectify issues if you aren't happy. If you decide to cease working with us, we'll do our best to make that handover as easy as possible.

We don't want to make you work with us if we're not a good fit. We'll try to help you find other developers that might be a better match.

This will depend on the nature of our engagement with you, and the project itself. Typically, on milestone projects we will categorise bugs and verify with you which categories are covered under a quality guarantee and which aren't, along with establishing a defined support period post-delivery. Agile projects are determine by your capacity and priorities.

Everything. For most projects that's a live build, support documentation, demonstration videos, and the project repositories and working files.

Absolutely. We have experience working on various platforms, including PS5, PSVR2, Meta Quest, Pico, Steam (Windows, Mac, Linux, Steam Deck), Xbox, and Nintendo Switch.

Absolutely. We can identify the causes of poor performance and work with you to resolve them or ameliorate.

Absolutely. We often recommend this approach if you haven't already reached that phase in developing or validating your project/concept. This is an important phase for gaining feedback or validating an idea, and may serve as a 'go/no-go' check before proceeding with full-scale development.

If the main need is understanding risk or deciding what to do, start with Insight Reports. If you have a team and a defined technical challenge, Co-Development may fit. If you need a broader delivery partner, explore Full Development or Full Game Development.

Yes. A focused assessment, technical challenge, or milestone can be a useful first step. We shape the engagement around the problem rather than requiring a large commitment upfront.

Yes. Co-development is designed to integrate with an existing team, codebase, process, and ownership model. We can also support existing products through full development engagements.

We listen to the project context, ask focused questions, and help identify the clearest next step. You do not need a finished brief before starting the conversation.

No. We work alongside your team, agree responsibilities together, and contribute directly to the shared outcome.

Yes. The engagement is shaped around your codebase, engine or platform, workflow, review practices, and communication needs.

Feature development, architecture, performance, multiplayer or third-party integration, code quality, technical debt, and other defined delivery challenges are all suitable starting points.

It can be sized around a focused task, milestone, or longer period of senior capacity. We agree the right shape after understanding the challenge.

Yes. Discovery can begin with a concept, opportunity, or product challenge. We help turn it into a clearer problem, plan, and first valuable release.

The service can cover web, mobile, and desktop applications, together with the APIs, data, identity, payments, analytics, and other platforms they need.

We can support release, monitoring, issue resolution, operational readiness, and ongoing technical improvement after the first version reaches users.

Yes. We can join an existing product to improve architecture, deliver features, strengthen quality, or help create a more reliable path to release.

Yes. We can begin with concept refinement, game mechanics, player experience, technical feasibility, and a plan for proving the idea through prototypes or early milestones.

Yes. We can join an existing project to add development capacity, improve performance, strengthen systems, address technical debt, or help prepare for release.

The service can cover design, engine development, gameplay, production, visuals, audio, networking and multiplayer, saves, analytics, platforms, testing, and release management.

We use clear goals, playable milestones, visible priorities, technical planning, and regular decisions about scope and risk so the team always knows what to prove or deliver next.

No. A focused concern, stalled decision, or delivery risk is enough to begin framing the review. We help narrow the question before investigation starts.

Yes. Findings are connected to impact and prioritised so the team can distinguish urgent action from longer-term improvement.

Yes. The review can cover an existing codebase, architecture, build, performance profile, test approach, or development workflow, depending on the question.

You can use the recommendations with your existing team, or talk to us about focused co-development or implementation support where that is the best next step.