The process starts by assessing your needs and establishing a high-level design for your web application. Once the software development phase begins changing direction can be costly both in time and money, so in the design phase we will pin down as much as possible to minimize risk and uncertainty. A functional specification will be drawn up, and a stylistic design will be sourced from a third-party graphic designer. These two documents will form the acceptance criteria for the project, giving us clear goals to aim for.

The application source code will be made available to you whether through a package such as a .zip or .tar.gz file, or via a source control system such as github.

For open source and third-party works licenses will be provided. For newly-created closed source works the copyrights may be assigned.

Usage and maintenance instructions will be provided. Technical information on the inner workings of the application may be requested as an extension.

Infrastructure such as web servers, firewalls, and content delivery networks will be provisioned according to the functional specification. This will be done with your accounts taking the 'owner' role in the team, thereby any recurring costs will be billed to you directly by the service providers, and you will have full control over the service and your team.

The initial production deployment of the web application will be performed, including the setup of any software dependencies, such as databases, firewalls, and data backup systems.

Administrator-level access to the infrastructure and the application will be protected by credentials such as passwords and tokens. These will be provided separately from the software source code as a matter of information security best-practice.

Web applications typically require periodic maintenance such as security updates, performance monitoring, and resource scaling. A retainer for such work may be negotiated upon request.