We turned “quality” from a claim into an argument
How we translated Pinegard's quality, custom design and project model into content architecture, CTAs and a website built to work with performance campaigns.
Strategy, copy and content architecture that turned a generic quality claim into concrete reasons to choose Pinegard — while supporting conversion paths and performance traffic.
We did not need more words. We needed better logic.
There was already plenty of material on the Pinegard website, but repeating words such as “quality”, “custom” and “premium” does not create differentiation. Our task was to determine **what specifically proves those promises**, in what order a visitor should see the proof and where the next step should appear.
We developed the copy, H1/H2 hierarchy, section structure, offer entry paths, CTAs and implementation documentation. We did not perform the development — we designed the content and page behaviour for the implementation team to translate into the website.
From an empty claim to a page that can defend it
We unpacked the word “quality”
Instead of leaving it as a slogan, we broke it down into things Pinegard can show: material, experience, design process, execution and aftercare.
We built a proof layer
We organised arguments around material origin, experience with the material since 1985, finishing and execution standards so they supported the brand promise rather than forming a loose feature list.
We translated customisation into a process
The lack of a catalogue stopped being an absence. It became proof of the design model: start with the home, garden and intended use, then create the specific structure.
We added three ways to enter a project
“Tailor-made”, “Straight from the portfolio” and “Wherever you want” answer three different client situations: a personal vision, inspiration from an existing project, or a project in a specific location.
We connected decisions to the interface
The “Request a quote” CTA appears next to the design argument, while “Inspire” sits next to the inspiration section. The portfolio stops being a gallery attached at the end and becomes part of the next step.
We packaged it for implementation
The documentation identified specific headings, paragraphs, sections, CTAs and visual issues to correct, reducing the need for the implementation team to reinterpret the strategy.
“Exceptional quality” sounds good. The problem is that anyone can say it.
That is why the new H1 does not try to shout louder about quality. **“It is all in the approach”** moves the conversation from declaration to method. From that point on, the page has to prove the promise.
The first layer covers material and Pinegard's experience. The next explains design without catalogue-driven compromise. Another extends quality to service and responsibility for delivery. The sections no longer repeat the same message — each answers a different client question.
We turned the lack of a catalogue into a sales argument
In a premium product, personalisation often ends with a generic “made to measure”. We showed the **mechanism** behind the phrase. The project starts with the client's space, how they use the garden and the desired outcome. Only then are materials, screens, lighting, heating and other components selected.
This changes how the offer is perceived: the client is not buying a variant from an option list, but a process that leads to a solution. That is why the “We design without compromise” section was structured as four consecutive steps — from understanding needs to making the finished structure match the approved design.
Not every client arrives with a finished project in mind
After explaining the design approach, we created three parallel paths. **“Tailor-made”** is for someone with a personal vision. **“Straight from the portfolio”** allows a client to start from an existing project and adapt it. **“Wherever you want”** addresses the concern around project location.
These are not three variations of the same paragraph. Each block removes a different barrier to entry and creates a different reason to continue.
The CTA appears where the visitor has just received a reason to act
We did not treat the button as a mandatory footer element. “Request a quote” sits next to the design argument, while “Inspire” appears where the page moves into inspiration and portfolio. The next step follows naturally from the content the visitor has just read.
After the click, the ad cannot suddenly change the subject
The website changes were designed in the wider context of Pinegard's performance activity. Campaigns were separated by product and directed to corresponding destinations on the website. A page therefore has to take over a visitor who may know nothing about the homepage narrative, quickly provide the right arguments and present a clear CTA.
In this project, the website layer was not a separate “website task”. It was part of the **post-click experience**: ad message, page content and conversion point had to form one path. Campaign performance is covered in a separate Meta Ads case study — here we show how we prepared the website to work with that system.
Instead of a page “about quality”, we created an architecture of reasons to choose
The final material was more than rewritten copy. It included a new communication hierarchy, specific headings and paragraphs, a four-principle design section, three offer entry paths, “Request a quote” and “Inspire” CTAs, a portfolio block and notes on visual issues to correct.
The most important change happened earlier: **each section received its own function**. One proves material quality, another explains the design model, another reduces service risk, the next helps choose how to start a project, and the CTAs turn interest into the next step.
A website should make an argument, not only look good
We connect positioning, copy, information architecture and campaign context so every section has a specific job to do.
Visit the website
Visit Pinegard to see the current presentation of its timber architecture offer.