Skip to main content
Back to docs
Getting Started

Our Project Delivery Process

How a typical project flows from discovery through to production deployment and handover.

Overview

Every project follows the same structured delivery process. Predictability is a feature — you always know where the project is and what comes next.

Discovery and architecture

Before writing code, we validate the technical approach. For most projects this is a half-day or full-day discovery session where we work through user flows, data models, and integration requirements. The output is a technical specification that confirms or refines the proposal scope.

Development sprints

We work in two-week sprints. At the end of each sprint, you see working software — not a status report. Feedback at this stage is expected and built into the timeline. We use a shared project board (Notion or Linear) so you always have visibility into what is in progress and what is next.

Staging environment

All development goes to a staging environment that mirrors production. You can test and review on staging at any point during development. We never deploy directly to production without your sign-off.

Testing and QA

Every feature is tested against the acceptance criteria defined in the proposal. We write automated tests for business-critical logic and perform manual QA against the agreed user flows before marking any milestone as complete.

Production deployment

We handle the full production deployment — server setup, DNS configuration, SSL certificates, CI/CD pipeline, and monitoring. You receive access to all infrastructure with full documentation.

Handover

At the end of the project, we run a handover session with your team. We walk through the codebase, explain the architecture, cover the deployment process, and answer any technical questions. You receive:

  • Full source code in a private Git repository
  • Technical documentation (architecture, API reference, deployment guide)
  • Infrastructure access (server, database, DNS)
  • A 30-day post-launch support window

Post-launch support

The 30-day post-launch window covers bug fixes for issues that arise in production. It does not cover new features or scope changes — those are handled via a new proposal or a retainer engagement.

Still have questions?

Our team is happy to walk you through anything — just send us a message.