Team composition by stage
The mix of roles changes as the product matures. Early on, a designer and a backend engineer matter most. Around launch, mobile engineers and a tester carry the load. Later, a smaller team can run releases and fixes. You receive: a role table for each stage in the written agreement.
Onboarding to your tools
We ask for access to the tools your people already use and work in them, so there is no second backlog or side channel. You decide the permission level for each person. You receive: an access list showing who holds what, which you can revise whenever you choose.
Code and accounts in your name
The repository, the cloud account, the Apple Developer account and the Google Play Console account belong to your company from the first commit. Our engineers are members of them. You receive: the admin credentials and the ability to remove our access.
IP assignment in writing
The agreement assigns the code and designs the team produces to you, in a signed writing, which is what the Copyright Act requires for a transfer. You receive: the signed assignment clause, plus a list of the third-party libraries and their licenses.
Planning and review
Work is planned from your backlog and arrives as pull requests in your repository, where your own engineers can read, comment and ask questions. Builds go to testers on TestFlight and Google Play internal testing. You approve each release before it goes to the stores. You receive: the pull request history and installable builds.
Scaling up or down
When the roadmap grows or slows, the team changes size as the written agreement sets out, and you approve the new role table before it takes effect. The change starts once you approve the new role table. You receive: an updated role table in writing.