A clear digital project delivery process
Built with process. Delivered with care.
A clear process reduces assumptions, protects timelines and helps everyone understand what happens next. The exact stages can change by project, but the core structure remains consistent.
1. Discovery
We identify:
- Business objective
- Target users
- Current workflow
- Main problem
- Desired outcome
- Existing tools or website
- Priority market
- Timing
- Budget context
- Decision-makers
- Known dependencies
The objective is to understand the requirement before proposing a solution.
2. Scope and proposal
The proposal or statement of work should define:
- Deliverables
- Exclusions
- Milestones
- Timeline
- Client responsibilities
- Required content and access
- Review stages
- Revision allowance
- Payment schedule
- Third-party costs
- Ownership and licence terms
- Confidentiality
- Support period
Major work should not begin until the scope and commercial terms are accepted.
3. Structure and design
Depending on the project, this stage may cover:
- User journey
- Page or screen architecture
- Workflow mapping
- Wireframes
- Content hierarchy
- Visual direction
- Data and role requirements
- Integration planning
Early structure approval helps prevent expensive changes later.
4. Development and implementation
The approved design and workflow move into implementation.
This may involve:
- Frontend development
- Backend or database work
- Automation configuration
- API coordination
- Dashboard setup
- Content integration
- Analytics
- SEO foundations
- Responsive behaviour
- Security and access controls
5. Testing and review
Testing should reflect the actual scope.
Possible checks include:
- Functional flows
- Mobile and desktop behaviour
- Browser compatibility
- Forms and notifications
- Links
- Permissions
- Edge cases
- Performance
- Accessibility
- SEO files
- Analytics events
- Content accuracy
The client should review the work within the agreed feedback window and provide consolidated comments.
6. Approval and deployment
Once the agreed acceptance criteria are met, the project is prepared for launch or handover.
Deployment may require:
- Domain and DNS access
- Hosting
- Environment variables
- API credentials
- Analytics accounts
- Email configuration
- App-store or platform approvals
- Third-party subscriptions
External provider delays remain outside direct control.
7. Handover
Handover may include:
- Source files
- Deployment notes
- Admin guidance
- Credentials checklist
- Known limitations
- Third-party dependency list
- Maintenance recommendations
- Support-period details
8. Maintenance and improvement
A separate support agreement can cover:
- Bug fixes
- Content updates
- Monitoring
- Performance improvements
- Security updates
- Integration maintenance
- New features
- SEO improvements
- Automation refinement
Client responsibilities
A project moves faster when the client provides timely:
- Accurate information
- Approved content
- Brand assets
- Access credentials
- Legal approvals
- Consolidated feedback
- Decisions
- Payments
- Third-party accounts
Delays in these inputs may affect the schedule.
Change requests
A change request applies when work falls outside the accepted scope or materially changes an approved deliverable. The effect on cost and timeline should be agreed before the additional work begins.
Ready to define the first milestone?
Send the requirement, current situation and intended outcome.