How projects work
A structured process, from enquiry to launch
Every project moves through the same ten stages — adjusted in depth depending on scope, but never skipped.
The process
Ten stages, from first enquiry to handover
- 01
Submit Project Requirement
- You provide
- An initial project enquiry with goals, project type, and any early requirements.
- We review
- The enquiry is reviewed to understand the type of project and its likely scope.
- What gets confirmed
- Whether the project is a good technical and commercial fit, and next steps for discovery.
- Why it matters
- This sets the direction for every stage that follows.
- 02
Discovery & Goal Review
- You provide
- Business goals, target users, and context about the organisation.
- We review
- How the stated goals translate into technical and design requirements.
- What gets confirmed
- A shared understanding of what the project needs to achieve.
- Why it matters
- Without clear goals, technical decisions have nothing to be measured against.
- 03
Scope & Feature Mapping
- You provide
- Feature requirements, must-haves, and nice-to-haves.
- We review
- Feasibility, priority, and how features relate to the overall goal.
- What gets confirmed
- A prioritised feature list and initial project scope.
- Why it matters
- Clear scope prevents wasted effort and unclear expectations later.
- 04
UX/UI Direction
- You provide
- Brand assets, content, design preferences, and reference material.
- We review
- User journeys, information architecture, and interface direction.
- What gets confirmed
- Wireframes or design direction for key screens and flows.
- Why it matters
- Design decisions made early are far cheaper to change than decisions made during build.
- 05
Technical Architecture
- You provide
- Details of any existing systems, hosting, or technical constraints.
- We review
- The technical approach, integrations, and recommended technology.
- What gets confirmed
- The technical architecture and stack for the project.
- Why it matters
- Architecture decisions shape everything that is built on top of them.
- 06
Development
- You provide
- Timely feedback and any outstanding content or assets.
- We review
- Progress against the agreed scope and technical plan.
- What gets confirmed
- Milestones and any scope adjustments, agreed as they arise.
- Why it matters
- Development is where the technical plan becomes a working product.
- 07
Integrations
- You provide
- Access credentials or accounts for required third-party services.
- We review
- How each integration connects to the wider system.
- What gets confirmed
- Integration scope, testing approach, and any third-party constraints.
- Why it matters
- Integrations often involve services outside our direct control, so clarity here matters.
- 08
Testing & Review
- You provide
- Feedback from testing the build against real use cases.
- We review
- Functionality, responsiveness, accessibility, and performance.
- What gets confirmed
- Any final fixes or adjustments before launch preparation.
- Why it matters
- Structured testing reduces the risk of issues appearing after launch.
- 09
Launch Preparation
- You provide
- Final content, approvals, and hosting/domain access where relevant.
- We review
- Launch checklist items specific to the project.
- What gets confirmed
- Go-live date and any final pre-launch requirements.
- Why it matters
- A structured launch reduces avoidable last-minute issues.
- 10
Handover & Improvement Planning
- You provide
- Any questions about using or maintaining the system.
- We review
- Handover documentation and ownership requirements.
- What gets confirmed
- Support, maintenance, and future improvement plans, based on agreed terms.
- Why it matters
- A considered handover sets the project up for a longer, healthier life.
Transparency
Straight answers about scope, timelines, and ownership
These are the questions clients ask most often before starting a project.
How is project scope defined?
Project scope is confirmed individually for each enquiry, based on discovery, feature mapping, and agreed requirements.
What deliverables are included?
Final deliverables are confirmed per project and depend on the agreed scope, features, and integrations.
How are timelines set?
Delivery timelines depend on project scope, content, integrations, approvals, testing, and third-party services.
How do approvals work?
Approval points are agreed at key stages so feedback is captured before development moves forward.
What about third-party services?
Third-party platforms, APIs, hosting, payment providers, CRM tools, analytics tools, and software services may have separate terms, costs, limits, and availability.
How are integrations handled?
Integration requirements, access, and testing are scoped and agreed as part of the technical architecture stage.
What about hosting?
Hosting requirements and technical structure are agreed per project, based on the technology used and the client’s preferences.
How is testing carried out?
Testing requirements are agreed per project and reviewed before launch preparation begins.
Are revisions included?
Revisions are scoped per project — unlimited revisions are not assumed unless specifically agreed in writing.
Who owns the final product?
Ownership terms are confirmed individually for each project as part of the agreed scope.
What support and maintenance is available?
Support and maintenance terms, where applicable, are confirmed per project — no ongoing SLA is assumed unless specifically scoped.
Are commercial outcomes guaranteed?
No ranking, traffic, revenue, app-store approval, commercial result, or third-party platform approval is guaranteed.
Project scope, deliverables, timelines, integrations, third-party platforms, revisions, hosting, support, maintenance, ownership terms, and final development requirements are confirmed individually for each enquiry.
No ranking, traffic, revenue, app-store approval, commercial result, or third-party platform approval is guaranteed. SEO, performance, conversion, and commercial outcomes depend on content, competition, hosting, user behaviour, ongoing activity, technical implementation, and external factors.
Project enquiries
Ready to start at stage one?
Submit a project requirement and we will begin the discovery and goal review stage.