Current state
Review the existing brand assets and touchpoints, available evidence, ownership and the practical constraint the work must address.
Services / Rebranding solutions
Rebranding solutions.
Review the current brand, identify what should stay and build a clearer direction for the next stage of the business.
The job this service must do
A rebrand should preserve useful recognition while resolving a clear business problem. The transition is planned across the places customers and staff will actually encounter it.
A useful first scope
What we define
and deliver.
- Current-brand and touchpoint review
- Positioning and transition direction
- A phased identity and website rollout plan
Trademark searches, legal clearance, packaging production and large-scale rollout management require separate specialists or scope.
Service coverage
What the work can include.
The final combination follows the project brief. Every included page, feature, integration and review point is named in the written scope before implementation.
Brand audit
Define the brand audit required for the agreed first scope and record what remains outside it.
Transition direction
Develop the transition direction through reviewable decisions and a defined list of outputs.
Rollout plan
Prepare the rollout plan and the files, checks or operating notes needed for handover.
Working process
From brief to a testable release.
The proposal names the review milestones. Timing depends on the number of pages and features, content readiness and third-party access.
Define the problem
Agree the audience, business goal, available brand assets and touchpoints and the decision this project needs to improve.
Set the boundary
Name the change boundary, required inputs, review points, exclusions and acceptance criteria.
Create and review
Work through a small number of reasoned directions, record feedback together and keep changes tied to the approved brief.
Prepare the handover
Check the agreed outputs, organise source files and document the next implementation or operating step.
Custom scope / USD
Custom quote
Custom Development. Final quote after scope.
A tailored website feature, application capability or internal tool. The first release is defined before quoting.
User accounts and business state move into application scope. Third-party licences extra.
Read all pricing boundaries ↗Scope decisions
Questions to settle before build.
The proposal records confirmed requirements and lists any unknowns that need a separate, bounded review.
What is already approved?
Existing research, brand material, content, platform choices and account access should be separated from assumptions that still need a decision.
Who owns approval?
One named decision-maker and consolidated feedback prevent contradictory revision cycles and unclear acceptance.
What happens next?
The proposal identifies whether the work ends with a defined deliverable or continues into a separately scoped implementation.
Case study references
Reference studies
and interface details.
Each study identifies its public source, material status and the interface details being reviewed.
Explore working examples ↗Do we need to replace everything?
Not automatically. The review identifies recognisable assets worth keeping and the parts that actively limit clarity or consistency.
Frequently asked questions
Before you send the brief.
Can this be combined with website work?
Yes. When both are needed, the proposal sequences shared decisions and states which deliverables belong to each part of the project.
How many revisions are included?
The written proposal names the review stages and included revision rounds. Additional directions or production work are quoted before scope expands.
What do you need before starting?
A concise brief, the available brand assets and touchpoints, the intended audience, one approval owner and any fixed platform, timing or compliance constraints.
Your next website
Have a website in mind?
Let’s talk about what it needs to do.
Share your brief. We’ll review the scope and reply in writing.