One accountable scope
Both teams work from the same approved deliverables, responsibilities, assumptions, and exclusions.
How we work
Agree on the workbefore the work begins.
We make sure everyone understands the problem, the plan, the review points, and the next step from the first meeting onward.
Start with discoveryThe delivery path
Eight stages, adjusted to fit the project.
A small brand project does not need the same process as a large software system. We use only the depth and time the work needs.
Discovery
We learn about your business, users, current process, constraints, and goals.
Typical outputA shared understanding of the problem and the questions we need to answer.
Scope & proposal
We set out the work, exclusions, responsibilities, milestones, price, and support terms.
Typical outputA proposal that shows exactly what the project includes.
Strategy & planning
We prepare the content, brand, user experience, system, campaign, or delivery plan before production starts.
Typical outputAn approved direction and delivery plan.
Design or technical architecture
We turn the plan into designs, prototypes, user journeys, workflows, or system architecture for review.
Typical outputSomething you can review and test before the full build.
Build & implementation
We build the approved work in manageable stages and keep decisions documented.
Typical outputWorking deliverables that follow the approved direction.
Review & quality assurance
We check content, behaviour, mobile layouts, access, integrations, and the agreed requirements.
Typical outputKnown issues resolved and both teams ready for launch.
Launch & handover
We launch or deliver the approved work, train your team, hand over access, and confirm how support will work.
Typical outputA controlled launch with clear ownership.
Support & improvement
If support is included, we monitor, maintain, report, improve, and plan future work with you.
Typical outputReliable support after launch and a plan for future improvements.
Plan before production
Make the important decisions before we start building.
What clients can expect
Enough structure to keep everyone on track.
We do not add meetings for the sake of it. We make sure people know what is being decided, who acts next, and what done means.
Visible review points
We ask for feedback at planned points while changes are still easy to make.
Documented decisions
We record important changes and approvals so the project does not depend on memory.
A defined handover
We agree on ownership, access, training, documents, and support before the project closes.
Before delivery starts
Your proposal should leave no important question unanswered.
The format may change, but every proposal should cover these points.
- 01Goal and expected result
- 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 happens. We agree on its impact first.
New information and priorities can change the work. Before we continue, we explain what the change means for scope, timing, responsibilities, and cost.
Ways to work with us
Choose a working model that fits the need.
01
One clear result
Focused project
Best when we can define the problem and deliverables as one project.
02
Connected change
Phased programme
Best when several services or releases need to work toward one larger goal.
03
Ongoing need
Support retainer
Best when you need technical, creative, marketing, or advisory support each month.
The first stage
Start by telling us what needs to change.
The first conversation helps us decide if there is a project to scope and what should happen next.