Grizzle is a London-based organic growth agency focused on content, SEO, and digital PR for B2B and SaaS. Originally built in a more scrappy, in-house way, the brand had been outgrown and no longer reflected the level of work they were delivering. They came to our agency for a full rebrand and website overhaul, aiming for something more distinctive, while still grounded in performance. Our team led the full brand sprint, followed by a complete web design sprint covering wireframing, UI, and dev handoff, with the site ultimately built in Webflow. The result is a site that feels more confident and opinionated, while still aligned with their core focus on driving measurable growth.
Industry
UX / UI Design, Design System, Dev Handoff & QC
Scope
End-to-end UI design
Output
Design + Dev handoff
Tools
Figma, Adobe Suite
Recognition
Award submission
The web design sprint started with high-fidelity wireframes in Figma, running this in parallel with the final branding phase to stay on schedule. We designed desktop and mobile for the homepage and key service pages in weekly batches (3–4 pages per week, alongside other client work), with most pages approved in the first round.
For more complex interactions, I used lightweight prototypes and paired each delivery with a Loom walkthrough to explain user flows and key decisions. All wireframes were built with auto layout to ensure they scaled cleanly into development. We started building out components at this stage as well to make the transition to UI design more seamless.
Moving from high-fidelity wireframes into UI, we kept the structure and flow intact but didn’t treat the wireframes as fixed. They set the foundation, but the UI phase is where the brand needed to come through properly.
We allowed for flexibility in layout, spacing, and visual treatment so the design could align with the branding work, rather than forcing everything to match the wireframes exactly. The examples below show how the core structure is carried through, but the final UI evolves where it needs to.
“I wanted something out there from a B2B perspective. Something a little cooky, but still professional, taking inspiration from the B2C world. And boy, did they deliver. Whenever I shared early versions of the new website with friends and peers, I would get one of two responses: ‘Wow, that’s really f’ing cool.’ or, ‘Huh…. that’s f’ing weird.’ But never ‘that’s boring.’ Which was the opposite of what we were going for.”
— Tom Whately, CEO, Grizzle
The scope didn’t allow for a full design system, so we built a focused UI kit within the Figma file instead. It covered the essentials: typography, colour and extended palettes, grids and spacing, core components with states, and basics like favicon and open graph. Everything was structured and linked so it could be used directly in build. This worked well for the scale of the site — it was quick to roll out, updated continuously during the sprint, and handed over as a single source of truth for development.
“My first exposure to your website was last night. I thought it was really well done.”
— Leonard Doherty (LinkedIn Feedback)
Handoff was straightforward because the full UI was completed before development started. We stayed on timeline, so there was no need to design and build in parallel. That meant all UI refinements were resolved upfront, and we avoided rework later. We built the site in Webflow and stayed in close contact throughout. I worked directly with the developer via huddles, Looms, and calls to walk through interactions and flag anything complex early. Where something wasn’t immediately feasible, we worked through it together and adjusted either the design or the implementation. In most cases, we were able to stay true to the approved UI.
More broadly, I treat development as collaborative, not handoff-only. Every developer works differently, and I try to adapt to that. The goal isn’t pixel perfection at the cost of function, but getting as close as possible while respecting how things actually behave in build. Keeping communication open makes a big difference. We also ran multiple rounds of dev QA. I see that as part of the design responsibility — making sure what was built matched the intent. Feedback was a mix of live calls for quick fixes, plus markup and side-by-side comparisons in Figma for more detailed checks. The developer later mentioned this was one of the smoothest projects he’d worked on, which came down to alignment early and consistent communication throughout.
“Weirdly cool, for sure 😎”
— Celia Vox (LinkedIn Feedback)
We submitted the project for award consideration following launch. It felt like a strong candidate given the clarity of the process, the quality of the outcome, and how smoothly design and development came together.
Sprint: 4–5 weeks
