Map the job: define the release people need
We identify users, their key tasks and the information needed to complete them. For a website, this might be a service comparison and an enquiry journey. For an application, it could be account creation, a permission boundary or an operational action. You supply existing code, content and system access as appropriate. We record dependencies and unresolved decisions before proposing the build.
The written scope names included journeys, integrations, supported environments and acceptance checks. It separates the initial release from ideas for later work. We agree who supplies content, who approves screens and who owns infrastructure decisions. Your code, files and accounts belong to you; third-party software, services and licences are identified separately so ownership does not obscure an external dependency.
Design the system: connect screens and architecture
We prototype the important interactions while planning the data and application structure. Roles, validation, empty states and error recovery receive attention alongside the main path. A checkout, marketplace or mobile release may depend on outside providers and their rules. We check those dependencies during scoping and name any provider approval or account setup that must happen before launch.
Technology choices follow the product and your team’s operating needs. We consider existing systems, hosting constraints, content editing and how future work will be maintained. The tool list below is a vocabulary for the discussion, not a required stack for every project. The agreed architecture records the chosen tools, data boundaries, deployment approach and the reasons for those choices.
Build in the open: review working software
Regular demos take place on a live URL so you can review actual behaviour as the product develops. We show the journeys that are ready, identify what remains incomplete and collect one consolidated response. A working preview helps reveal content and integration issues before release. Preview access and data are scoped; sensitive production records are not needed simply to demonstrate a screen.
Checks follow the risks of the product. We test important user actions, permission boundaries and integration failures where they are in scope. Website checks cover the agreed screen sizes, keyboard use, loading and metadata requirements. We document unresolved issues and their release implications. A successful local build is one checkpoint; deployment and provider acceptance still require checks in the agreed target environment.
Release with care: leave an operable product
Release preparation covers configuration, secrets, deployment instructions and the recovery approach appropriate to the system. Infrastructure and external service accounts are held by the client under the agreed arrangement. We review the core journeys after deployment and record acceptance against the written scope. A mobile app scope distinguishes a working build from store submission and any external review process.
Handover includes the source code, documentation and a walkthrough of the tasks your team will perform. Maintenance is a separate, explicit decision: what is monitored, which updates are covered and how changes are requested. We identify remaining priorities without presenting them as unfinished promises. If your internal engineers take over, the documentation explains how to build, configure, deploy and extend the product.