What the project includes
User journeys
Clarify audiences, goals and information requirements.
Structure and wireframes
Organise content and test the flow before applying the visual system.
Visual design
Develop reusable components and responsive templates with real text.
Development handoff
Prepare organised design files and explain key behaviours.
When it fits and what to consider
Your goals guide the choice.
Who it suits
- New websites
Create a coherent interface before development starts.
- Confusing journeys
Review structure and content hierarchy around actual tasks.
- Reusable systems
Keep future pages consistent through shared components.
What to consider
- Research scope
Interview or usability-study work must be separately specified.
- Design versus code
A design file is not a deployed website.
- Real content
Placeholder copy cannot validate every layout condition.
Scope and deliverables
What we do and what you receive.
User journeys
Clarify audiences, goals and information requirements. Map the actions and questions that the interface must support.
Scope of work
- Agreed scope: user journeys
- Joint review before handover
What you receive
You receive this stage’s deliverables and the documented decisions needed to move forward.

Loading examples…
Structure and wireframes
Organise content and test the flow before applying the visual system. Include empty, error and success states where relevant.
Scope of work
- Agreed scope: structure and wireframes
- Joint review before handover
What you receive
You receive this stage’s deliverables and the documented decisions needed to move forward.

Loading examples…
Visual design
Develop reusable components and responsive templates with real text. Align type, spacing and interaction states within one system.
Scope of work
- Agreed scope: visual design
- Joint review before handover
- Brand identity
- Web development
- Custom web development
What you receive
You receive this stage’s deliverables and the documented decisions needed to move forward.

Loading examples…
Development handoff
Prepare organised design files and explain key behaviours. Review implementation questions against the agreed layouts and content.
Scope of work
- Agreed scope: development handoff
- Joint review before handover
What you receive
You receive this stage’s deliverables and the documented decisions needed to move forward.
Cost and timeline
We estimate the work from its scope, available materials, integrations and review rounds. Milestones are agreed before work begins; licences, subscriptions, ad spend and third-party services are listed separately where applicable.
Clear responsibilities
We establish who approves materials, owns the accounts and handles ongoing maintenance. Scope changes are assessed before implementation.

Loading examples…
Choose your starting point
Choose the next step for your project.
Your goal
User journeys
Clarify audiences, goals and information requirements. Map the actions and questions that the interface must support.
- Goal
- Scope
- Delivery
Understand
Review goals, materials, access and market requirements. Identify what must be checked before work starts.
Plan
Agree scope, deliverables and responsibilities. Present decisions for approval before implementation.
Implement
Complete the agreed work and check relevant scenarios. Assess new requirements separately.
Handover
Share deliverables and recommendations. Establish who handles ongoing operation and improvements.
Questions about web and ux/ui design
Scope, preparation and handover.
Do you provide development too?
Development can be scoped separately or as part of a complete website project. The design handoff identifies templates, components and behaviours to implement.
Will we receive the editable files?
File ownership, access and asset licences are agreed before work starts. The handoff scope explains what your team can reuse.
Do you include mobile design?
Responsive states are part of the agreed template scope. We consider real text lengths and interaction states, not only one desktop artboard.
How do you estimate cost and timing?
First we review the scope of web and ux/ui design, available materials and dependencies. The proposal separates deliverables, revisions and external costs. Different project requirements need different estimates.
What should we prepare to get started?
Share your goals, target market and existing materials. We identify missing inputs and request only the access needed. Do not send passwords through public forms.
Are ongoing maintenance and improvements included?
The initial scope and ongoing support are agreed separately. At handover we clarify who maintains the project, which accounts your team owns and how changes are requested.
Let’s discuss web and ux/ui design
Website UX/UI design from user flows and wireframes to responsive interfaces. Get organised Figma templates and reusable components ready for development.




