A build is worth showing when the brief was specific enough to produce real decisions. For each of these, what matters is not the visual — it is what the site had to do and what we changed to make it do that. Screenshots of attractive pages are easy to collect and tell you very little; a portfolio is only useful if it explains the reasoning, including the constraints that made the obvious answer impossible. That is what we have tried to write up here.
What the business needed the site to produce — booked consultations, cleared checkouts, quote requests — and how we knew whether it was working.
Most of these had one: an advertising code, a payment processor, a catalogue that had to stay editable, or a launch date that was not moving.
The choice that did the heavy lifting — usually about information architecture or where the primary action sits, rarely about colour.
Every build teaches something. We would rather show you the revision we would make than pretend the first version was perfect.
Because a portfolio of forty thumbnails is a filter you have to apply yourself. We would rather show fewer builds and explain the decisions inside each one, which is the part that actually tells you whether we would be useful on your project.
For most, yes — ask on the call and we will arrange an introduction where the client is happy to take it. Some clinic and supplement clients prefer not to be named publicly, which we respect and would extend to you too.
If it is one of our three specialisms, yes. If it sits outside them we will say so rather than stretch a loosely related project to look relevant — you can judge the thinking from the write-ups instead.
Thirty minutes, your time zone. We will tell you honestly whether a rebuild is the right spend or whether fixing three things on the current site would do more.