Four steps, always in this order.

A project moves through four steps, always in this order. Prepare: we explore your needs and set the scope; you receive a scope document, an estimate, and a risk list; we need access to the people who do the work, sample data, and a decision on where data lives. Depart: staged releases tested by your team from the start; you receive a first working version on the agreed date; we need regular reviews and quick decisions. Resupply: maintenance, updates, and monitoring; you receive periodic reports and security updates; we need one technical contact and a maintenance window. Return: final documentation, handover, and training; you receive full access to code, data, and infrastructure; we need a receiving team and time for training. No step is skipped, and maintenance after handover is a separate agreement.

This table compares the roles of your organization and sixseven.camp, whose access can be revoked. Accounts and access: accounts are in your organization’s name and you appoint who is responsible for access; we work with the access you grant, which is logged and revocable. Data: stored where you decide; we use it within the agreed scope. Code and documentation: code, data structure, and documentation are handed over to you; we prepare them and hand them over. Day-to-day operations: you decide on changes; we maintain the system only under an agreement. Everything is set out for each project.