One accountable scope
The team works from the same approved deliverables, responsibilities, assumptions, and exclusions.
How we work
Clear decisionsbefore busy delivery.
Good work needs more than activity. Our process creates shared understanding, clear review points, and a practical route from the first conversation to launch and support.
Start with discoveryThe delivery path
Eight stages. Adapted to the engagement.
A small brand project and a custom software platform do not need identical ceremonies. The stages remain useful, while their depth and duration change with the work.
Discovery
We clarify the organization, audience, problem, current approach, constraints, stakeholders, and intended outcome.
Typical outputShared understanding and the questions the project must answer.
Scope & proposal
We translate the need into deliverables, exclusions, responsibilities, milestones, commercial terms, and support expectations.
Typical outputA proposal that makes the shape and boundaries of the engagement clear.
Strategy & planning
We develop the content, brand, experience, system, campaign, or implementation plan required before production starts.
Typical outputAn approved direction and a practical delivery plan.
Design or technical architecture
We turn the plan into interfaces, creative direction, journeys, prototypes, workflows, or system architecture for review.
Typical outputA tangible solution direction that can be evaluated before full build.
Build & implementation
The team executes the approved scope in manageable stages, with visible progress and documented decisions.
Typical outputWorking deliverables developed against the agreed direction.
Review & quality assurance
We review content, behaviour, responsiveness, permissions, integrations, and agreed acceptance requirements.
Typical outputIssues resolved and launch readiness understood by both teams.
Launch & handover
We deploy or deliver the approved work, complete agreed training, document ownership, and confirm the support route.
Typical outputA controlled release with clear operational responsibility.
Support & improvement
Where included, we monitor, maintain, report, refine, and plan additional work through a defined support arrangement.
Typical outputContinuity after launch and an informed path for future improvements.
From ambiguity to action
Make the work visible before production accelerates.
What clients can expect
Enough structure to keep the work understandable.
Clear delivery does not mean unnecessary meetings. It means everyone knows what is being decided, who owns the next action, and what completion looks like.
Visible review points
Feedback is collected at planned moments when decisions can still be made efficiently.
Documented decisions
Important changes and approvals are recorded so the engagement does not depend on memory.
A defined handover
Ownership, access, training, documentation, and support expectations are clarified before closeout.
Before delivery starts
A useful proposal makes the important boundaries visible.
The exact format depends on the engagement, but these points should not be left to assumption.
- 01Objective and intended outcome
- 02Deliverables and acceptance criteria
- 03What is explicitly excluded
- 04Client and UBC responsibilities
- 05Milestones and review points
- 06Commercial terms and payment stages
- 07Assumptions and dependencies
- 08Launch, handover, and support model
When the scope changes
Change is normal. Invisible change is expensive.
New information, priorities, and constraints can change the work. When that happens, we make the impact on scope, timing, responsibility, and cost visible before proceeding.
Engagement models
The commercial structure should fit the work.
01
Defined outcome
Focused project
Best when the challenge and expected deliverables can be scoped as one clear engagement.
02
Connected change
Phased programme
Best when several capabilities or releases need to work toward one wider organizational objective.
03
Ongoing need
Support retainer
Best when the organization needs agreed technical, creative, marketing, or advisory capacity over time.
The first stage
Start by making the problem and outcome clear.
A discovery session helps determine whether there is a useful project to scope and what should happen next.