Process

How we deliver a project

Ten phases from first conversation to long-term support. Each has defined activities and named deliverables, so you can tell when a phase is genuinely complete.

Phase 1: Discovery
We establish what the business is trying to achieve, who it serves, and which constraints are fixed before proposing any solution.
Activities
- Interviews with decision-makers and the people doing the daily work
- Review of current systems, tools and manual workarounds
- Identification of commercial, technical and regulatory constraints
- Agreement on what success would look like in measurable terms
Deliverables
- Discovery summary
- Constraints and assumptions log
- Agreed success criteria
Phase 2: Requirements Analysis
Vague requests are turned into specific, testable requirements, including the exceptions that usually surface late.
Activities
- Documenting current processes end to end, including the exceptions
- Defining roles, permissions and the rules that govern each record
- Separating what is genuinely required from what is preferred
- Flagging requirements that carry disproportionate cost
Deliverables
- Requirements specification
- Process maps
- Prioritised scope with exclusions stated
Phase 3: Planning
Scope is sequenced into phases where each release is independently useful, with estimates that state their assumptions.
Activities
- Breaking scope into releases ordered by business value
- Estimating effort with the assumptions behind each figure recorded
- Identifying dependencies on your team and third parties
- Agreeing the review points and how changes will be handled
Deliverables
- Phased delivery plan
- Estimate with assumptions
- Change-handling procedure
Phase 4: UX & Architecture
Structure is decided before appearance: information architecture, user flows, data model and system design.
Activities
- Information architecture and navigation structure
- User flows including error and empty states
- Data model, entities and relationships
- Technical architecture, integrations and environment plan
Deliverables
- Wireframes
- Flow diagrams
- Data model
- Architecture document
Phase 5: Visual Design
Interface design applied across both text directions, with every component state specified so nothing is improvised in code.
Activities
- Design tokens for colour, type, spacing, radius and elevation
- Screens designed at mobile, tablet and desktop widths
- Independent right-to-left layouts, not mirrored copies
- Contrast verification and interaction states for every component
Deliverables
- Design system
- Interactive prototype
- Exported assets
Phase 6: Development
Implementation in reviewable increments, with working software available throughout rather than at the end.
Activities
- Version-controlled development with peer review before merge
- Separate development, staging and production environments
- Regular demonstrations of working software to stakeholders
- Automated checks running on every change
Deliverables
- Source code in your repository
- Staging environment
- Release notes per increment
Phase 7: Testing
Functional, cross-device, accessibility, performance and security checks, covering both languages independently.
Activities
- Functional testing against the agreed requirements
- Real-device testing across the supported screen range
- Keyboard navigation, screen-reader and contrast checks
- Performance measurement and input validation review
- Arabic and English tested separately, not assumed equivalent
Deliverables
- Test results
- Defect log with severity
- Accessibility and performance findings
Phase 8: Deployment
A rehearsed release with monitoring, backups and a rollback path established before anything goes live.
Activities
- Production environment provisioning and hardening
- Data migration with verification passes
- Monitoring, alerting and backup configuration
- Redirects, analytics and search console setup where applicable
Deliverables
- Live environment
- Deployment runbook
- Verified backup and restore procedure
Phase 9: Training & Handover
Your team is trained on the system and receives the documentation, credentials and access needed to operate independently.
Activities
- Role-specific training for administrators and daily users
- Handover of documentation, credentials and repository access
- Walkthrough of routine operations and common problems
- Agreement on the support arrangement going forward
Deliverables
- Training sessions
- Operations documentation
- Complete credential handover
Phase 10: Support & Continuous Improvement
Defined response times, scheduled maintenance, and a planned pipeline of improvements after the first release.
Activities
- Incident response within the agreed times
- Security patching and dependency updates on a cycle
- Periodic restore tests and performance review
- Prioritised enhancements based on real usage
Deliverables
- Support agreement
- Maintenance reports
- Improvement roadmap

Adapted to the engagement

Not every project runs all ten phases at full depth. A focused website does not need the same requirements analysis as a business system. What stays constant is that each phase has an agreed outcome before the next one starts.

Ready to start with discovery?

The first conversation costs nothing and usually clarifies more than a written brief.

Book a conversation Request a quote

Process

How we deliver a project

Ten phases from first conversation to long-term support. Each has defined activities and named deliverables, so you can tell when a phase is genuinely complete.

Phase 1: Discovery
We establish what the business is trying to achieve, who it serves, and which constraints are fixed before proposing any solution.
Activities
- Interviews with decision-makers and the people doing the daily work
- Review of current systems, tools and manual workarounds
- Identification of commercial, technical and regulatory constraints
- Agreement on what success would look like in measurable terms
Deliverables
- Discovery summary
- Constraints and assumptions log
- Agreed success criteria
Phase 2: Requirements Analysis
Vague requests are turned into specific, testable requirements, including the exceptions that usually surface late.
Activities
- Documenting current processes end to end, including the exceptions
- Defining roles, permissions and the rules that govern each record
- Separating what is genuinely required from what is preferred
- Flagging requirements that carry disproportionate cost
Deliverables
- Requirements specification
- Process maps
- Prioritised scope with exclusions stated
Phase 3: Planning
Scope is sequenced into phases where each release is independently useful, with estimates that state their assumptions.
Activities
- Breaking scope into releases ordered by business value
- Estimating effort with the assumptions behind each figure recorded
- Identifying dependencies on your team and third parties
- Agreeing the review points and how changes will be handled
Deliverables
- Phased delivery plan
- Estimate with assumptions
- Change-handling procedure
Phase 4: UX & Architecture
Structure is decided before appearance: information architecture, user flows, data model and system design.
Activities
- Information architecture and navigation structure
- User flows including error and empty states
- Data model, entities and relationships
- Technical architecture, integrations and environment plan
Deliverables
- Wireframes
- Flow diagrams
- Data model
- Architecture document
Phase 5: Visual Design
Interface design applied across both text directions, with every component state specified so nothing is improvised in code.
Activities
- Design tokens for colour, type, spacing, radius and elevation
- Screens designed at mobile, tablet and desktop widths
- Independent right-to-left layouts, not mirrored copies
- Contrast verification and interaction states for every component
Deliverables
- Design system
- Interactive prototype
- Exported assets
Phase 6: Development
Implementation in reviewable increments, with working software available throughout rather than at the end.
Activities
- Version-controlled development with peer review before merge
- Separate development, staging and production environments
- Regular demonstrations of working software to stakeholders
- Automated checks running on every change
Deliverables
- Source code in your repository
- Staging environment
- Release notes per increment
Phase 7: Testing
Functional, cross-device, accessibility, performance and security checks, covering both languages independently.
Activities
- Functional testing against the agreed requirements
- Real-device testing across the supported screen range
- Keyboard navigation, screen-reader and contrast checks
- Performance measurement and input validation review
- Arabic and English tested separately, not assumed equivalent
Deliverables
- Test results
- Defect log with severity
- Accessibility and performance findings
Phase 8: Deployment
A rehearsed release with monitoring, backups and a rollback path established before anything goes live.
Activities
- Production environment provisioning and hardening
- Data migration with verification passes
- Monitoring, alerting and backup configuration
- Redirects, analytics and search console setup where applicable
Deliverables
- Live environment
- Deployment runbook
- Verified backup and restore procedure
Phase 9: Training & Handover
Your team is trained on the system and receives the documentation, credentials and access needed to operate independently.
Activities
- Role-specific training for administrators and daily users
- Handover of documentation, credentials and repository access
- Walkthrough of routine operations and common problems
- Agreement on the support arrangement going forward
Deliverables
- Training sessions
- Operations documentation
- Complete credential handover
Phase 10: Support & Continuous Improvement
Defined response times, scheduled maintenance, and a planned pipeline of improvements after the first release.
Activities
- Incident response within the agreed times
- Security patching and dependency updates on a cycle
- Periodic restore tests and performance review
- Prioritised enhancements based on real usage
Deliverables
- Support agreement
- Maintenance reports
- Improvement roadmap

Adapted to the engagement

Ready to start with discovery?

The first conversation costs nothing and usually clarifies more than a written brief.

Book a conversation Request a quote

How we deliver a project | GO RICH

How we deliver a project

Phase 1: Discovery

Activities

Deliverables

Phase 2: Requirements Analysis

Activities

Deliverables

Phase 3: Planning

Activities

Deliverables

Phase 4: UX & Architecture

Activities

Deliverables

Phase 5: Visual Design

Activities

Deliverables

Phase 6: Development

Activities

Deliverables

Phase 7: Testing

Activities

Deliverables

Phase 8: Deployment

Activities

Deliverables

Phase 9: Training & Handover

Activities

Deliverables

Phase 10: Support & Continuous Improvement

Activities

Deliverables

Ready to start with discovery?

How we deliver a project

Phase 1: Discovery

Activities

Deliverables

Phase 2: Requirements Analysis

Activities

Deliverables

Phase 3: Planning

Activities

Deliverables

Phase 4: UX & Architecture

Activities

Deliverables

Phase 5: Visual Design

Activities

Deliverables

Phase 6: Development

Activities

Deliverables

Phase 7: Testing

Activities

Deliverables

Phase 8: Deployment

Activities

Deliverables

Phase 9: Training & Handover

Activities

Deliverables

Phase 10: Support & Continuous Improvement

Activities

Deliverables

Ready to start with discovery?