The work
The build at a glance
Scope, stack and outcome for Cashew.
High-converting landing pages built in Webflow, no code required. Strong UX foundation, responsive layouts and smooth interactions, designed so the client can keep changing them.
No code
landing pages the marketing team can rewrite on a Tuesday without opening a ticket
Cashew: a component system, CMS and page set built to be edited by non-technical teams.
Traditional landing page development is time-consuming, dependent on developers, and hostile to iteration. The first version ships fine. The problem starts when the marketing team wants to test a different headline and discovers that a two-word change requires a ticket, a sprint and a deploy.
That dependency quietly kills performance marketing. Pages stop being iterated because iterating is expensive, and a page that cannot be tested cannot be improved.
A landing page that needs a developer to change is a landing page that stops changing.
So the goal was pages that are fast to launch, easy to manage, and deliver a seamless experience across every device, with the client's own team holding the keys.
Reusable classes and components that maintain consistency across pages, so adding a new page means assembling known parts rather than designing from scratch.
Blogs, case studies and landing pages modelled as dynamic content, so the client updates them without touching layout or needing technical help.
Non-technical teams can update copy, images and sections without breaking the design. The components hold the rules so the editor does not have to know them.
Dynamic content for blogs, case studies and landing pages that the client can update without technical help, and without a developer in the loop.
Reusable classes and components that keep consistency across pages as the site grows, covering buttons, pricing tiers, panelist cards, FAQs and content blocks.
Meta tags, alt text and page structure controllable directly, so search visibility is something the team can improve rather than something they have to request.
Non-technical teams can update copy, images and whole sections without breaking the design, which is the point of the entire exercise.
The work
Scope, stack and outcome for Cashew.
Four weeks, one designer, and a site the client runs themselves. That is usually a better outcome than a bigger build.
Start a project →