When your work outgrows your website
Decide what to keep, what to change, and where a more considered design or build would make a difference.

Your work has changed. The website still introduces the version of you that launched it. A portfolio hides the projects you now want to be hired for. A service page takes several emails to explain. Your team copies each inquiry into another tool. Each problem gives the redesign a different job.
Start by naming the gap. You may need a sharper edit, a new visual direction, or a different way for people to act. The platform decision follows from that work.
Look for friction in a real task
Choose a task that matters to the project and follow it from beginning to end on a phone. Use a real service description, a published piece of work, or an actual product. Keep a list of every point where someone has to guess, repeat information, or switch channels.
- Can a new visitor understand the offer without knowing your industry vocabulary?
- Can they compare the options that affect their decision?
- Does the form ask for information your team will actually use?
- What happens after submission, including when something fails?
- Can the team responsible for the next step find the right information?
This exercise separates a visual preference from an operational requirement. Both can matter, but each needs a different kind of response.
Keep what is already doing its job
A hosted platform can be a sensible long-term choice when its content tools and workflows fit the business. A considered design, good photography and specific copy can do a great deal within an existing system.
Before replacing it, investigate whether a content rewrite, a simpler navigation or a targeted integration would solve the problem. Include the time your team spends maintaining the current setup when you compare options.
Give the visual direction a reason to change
A visual refresh can be worthwhile when the presentation no longer suits the work. An independent practice may want to show a different kind of project. A growing company may need its pages to feel like one organization. Collect examples of the mismatch and describe the impression you want to leave.
Keep recognisable details that still feel right. A distinctive type treatment, a useful content structure, or a strong set of photographs can give the new site continuity. The scope can be precise even when the result feels substantially different.
Know what a custom build needs to earn
A custom approach becomes useful when the requirements are specific: a multi-step customer workflow, a product interface, complex content relationships, or connections to systems the business already uses. Its value is the ability to shape those details deliberately.
Custom code does not automatically make a site fast, accessible or easy to maintain. Those qualities need design decisions, implementation work and verification. Ask to see how the proposed approach will be tested and who will own it after delivery.
Compare the whole engagement
Ask each studio to describe the scope, the review process, the content responsibilities and the handoff. Be explicit about existing URLs and content that must remain available. An estimate is more useful when you can see what decisions it includes.
The right result is a site your customers can use and your team can operate. A new visual direction can be part of that result. The brief should also explain what will work better when the new site is live.
Have a project in mind?
Share the idea, the brief, or the part you want help figuring out. We work with individuals, businesses, and creative teams.
Discuss your project