Accounts in your name
The code repository, the cloud hosting account, the domain and the app store accounts are opened by your company, with the admin role held by you. Our engineers are added as members at the level the work needs. You receive: the admin credentials and an access list you can edit.
Assignment in the contract
The contract assigns the code, designs and documentation produced for you to your company, in a writing both sides sign. A list of third-party libraries and their licenses goes with it, so you know what is yours and what is borrowed. You receive: the signed assignment clause and the license list.
A written scope
The first milestone is described in a document: what is in it, what waits, and the fixed price for the milestone. Changes are written up and priced before work on them starts. You receive: the scope and each approved change.
Work in your tools
We take access to the repository, the issue tracker and the chat workspace you already run, and work in them. There is no second backlog to reconcile. You set the permissions and can change them. You receive: a shared channel and a board that show the work as it happens.
Review in your repository
Code arrives as pull requests in your repository. If you set merge rules, such as required approvals, the work follows them. Your engineers, or an adviser you hire, can read and comment on any change. You receive: the pull request history and test builds you can install.
A live window
We are on calls and in Slack from 8 a.m. to 1 p.m. ET on business days. Anything raised outside the window is picked up in the next one, and the work is documented in the repository and the tracker. You receive: the window in writing, in the scope.