How the Process Works
1. Initial Brief Submission
The process starts when you submit your enquiry and complete the attached briefing form. This gives us the information we need to understand your requirements, business context, priorities, and the type of solution or service you are looking for.
Once we receive your brief, we review it carefully and begin preparing for the next step.
2. Discovery Follow-Up Meeting
After reviewing your brief, we schedule a follow-up discussion with you. This can take place in person, by video conference, or by phone - whichever you prefer.
This session is typically one hour or longer, depending on the complexity of the requirement. By this stage, we have already spent time reviewing your brief, doing preliminary thinking and research, and preparing an initial direction and plan for discussion with you.
3. Discovery Summary and Direction
After discovery, we provide a clear summary of priorities, opportunities, constraints, and a recommended direction. This helps ensure both sides are aligned before formal implementation planning begins.
The focus at this stage is clarity: what problem is being solved, what success looks like, and what should happen first.
4. Scope, Specifications, and Implementation Plan
Once there is mutual agreement to proceed, we prepare a detailed specification and implementation plan.
This stage is used to define the project properly and may include:
- project scope
- key deliverables
- functional requirements
- assumptions and exclusions
- implementation approach
- indicative timeline
- dependencies and delivery checkpoints
Our goal is to make sure both parties have a clear, shared understanding of what is being built or delivered before development work begins.
5. Final Scope Approval and Project Kickoff
Once scope and specifications are agreed, the project moves into execution.
At kickoff, we align on:
- delivery phases and milestones
- reporting cadence and review points
- stakeholder communication flow
- acceptance criteria for each stage
This keeps execution structured and transparent across the full lifecycle.
6. Timelines
Estimated timelines are based on agreed scope and delivery dependencies.
Where requirements evolve, timelines are reviewed collaboratively to maintain quality and delivery confidence.
Why We Structure the Process This Way
Our projects typically involve substantial upfront thinking before development begins. Reviewing your brief, researching your requirements, preparing an initial plan, and conducting the discovery discussion all require time and expertise.
This process helps ensure that:
- your requirements are properly understood
- the project is scoped realistically
- delivery risk is reduced early
- delivery expectations are clear from the start
It also allows us to begin engagements in a structured, professional way that protects both parties and improves the likelihood of a successful outcome.