Prologue

Rebuilding our own site meant facing the trap we sell partners out of.

The record of building BUBI’s own site: the decisions, the delays and the work you can inspect for yourself.

The build, on one card

What this was, in short

Everything here is restated from the story below; nothing on this card is new.

  • Built by The two of us, no agency and no developer in the room
  • On Webflow, with custom code for the interactive parts
  • After Years on a generic site we knew was wrong
  • To a date Our own, and kept, with a few things rushed to hold it
  • Kept in full Every partner review, not a chosen six
  • Claims Our writing, structure and demonstrations, available to inspect

The delay

Years afraid of our own advice

For years the old site said 'unleash your creativity' and meant nothing. We knew it was wrong. We did not fix it, because the proper way to fix it looked like the exact trap we sell partners out of. Hand it to developers. Lose the weeks to briefing and chasing. Watch the voice thin out in the handover. Become the person who has to approve everything, again. We had written that trap on the page we did not yet have. About the page itself, we were living in it.

We talked to several people who build sites. Each conversation ended in the same place: a management and delay rabbit hole we had neither the time nor the appetite for, and a quiet fear of getting lost in code until the voice was gone.

So we waited until two things were true at once. That the idea was too large to hand over without losing it. And that we could carry it ourselves without disappearing into work we do not do for a living. When both held, we built it.

On purpose

What we decided, and why

Compression, because the first version drowned

The first design held everything we wanted to say and was unusable, ours included. We needed to keep most of the information and lose some of the shape we were attached to. The need was practical before it was philosophical, and then it became the argument: attention is the scarce thing, so say the short version first and keep the long one underneath for whoever wants to check.

You keep the identity, we do the verbs

You own the voice, the standard, the brand. We read, write, run, record, hold. We do not write 'our creative vision' over your work anywhere, because it is not ours. Your identity gives that work its direction.

Make the distinction concrete

Several pages use a contrast to explain a decision: what a task appears to require, and what the work revealed. It helps when the distinction is real. When the same turn repeats without adding anything, it needs cutting.

The site performing its own service

This was the most deliberate decision of all. What we sell is taking a person's accumulated judgement, compressing it, keeping the character, and making it usable by others. So the site is that, done to ourselves: a compressed recommendation on top, the obsessive record underneath.

Arriving mid-process

The image on every main page is a timecode, something being worked on: we sell continuous production, so the picture should say 'in progress'.

Keeping all of it

We keep the full public review record accessible, including ratings below five stars. Individual case pages select the reviews relevant to that work and link back to the wider record.

Restraint in the machinery

No marketing tags. Optional analytics follow the visitor’s choice, with accept and reject offered equally. These choices are part of how the site handles its audience.

Bespoke effort only where judgement lives

Webflow for the boring, reliable parts. Custom work saved for the few places it changes what you understand, a demonstration you can feel rather than a decoration that announces itself. It is the same rule we use at the bench: do not rebuild the boring infrastructure, spend the attention where taste decides something.

Unplanned

What emerged, and happened to fit

Some of the site's meaning emerged while we built it. The risk was the same as in the work we sell: keeping enough detail to be useful without asking the reader to carry all of it at once.

Some readings of the site we find plausible but will not claim as intent. The old-world imagery, the chess, the meanings people read into them. Some of it is deliberate. Some of it is just margins. We would rather say which is which than let every twelve-pixel gap sound like philosophy.

The limit

What we cut, rushed, and will not claim

The first design cost us pages we liked. Compression was the right trade and it still stings a little.

The partner area is not here: one screen where everything we keep about a partner, the reports, the deliverables, the status, sits in one place. It is the ambition we want most and have not built, because it is roughly the whole site again. Postponed, not abandoned.

There were too many pieces to find our way around. One day we could not find a thing we were sure we had written, or half-written between us, and if the author cannot navigate it the reader has no chance. Guides are the correction: ordered routes through the pieces, which stay where they are. By our own eye they are not finished.

Some of this shipped rushed, because we set a launch date and we keep launch dates, including the ones we give ourselves. A few ideas were judged impractical and dropped. A few will arrive after launch. A few turned into other things on the way.

This site shows how we write, organise ideas and make production choices visible. We took what we think and made it stand up. What that approach can do for your channel is something to test together.

Source notes

The shoot, and what a stranger can name

The strategy image is a single frozen chess position, Fischer against Tal. A line long attributed to Tal names the place he took opponents: a deep dark forest, where two and two make five and the way out is wide enough for one. That is the strategy of the site, should you accept it: go in and it complicates, pleasantly, until you find your own way out. We take no side. A position holds both the player who set out to be champion and the player remembered only by the move, and both are in a person, and in the two of us. The idea came from agadmator's chess channel, which we like and have no relation to.

The rest is inspectable from the outside. It is a Webflow site, served from Webflow's own files. The heroes are one repeating component, a timecode, on purpose. A few case studies carry small interactive pieces built to make an analytical point perceptible, a microphone out of phase, a timeline, a chord, rather than to show that someone owns an animation library. Services, insights and casework each run through one shape, one set of fields, many pages: define the standard once, feed different material through it. The same doctrine as the bench.

This is our own record of the build, with no partner's data in it, so nothing is withheld. The few facts it rests on, the reviews we kept, the tools we used, the day it went live, sit elsewhere on the site with their dates. To check any of it, open the page it describes and look.

What you would get

Bring us something real

Read the site as a stranger would, then send us something real. The first conversation is free, and if we are the wrong fit we will say so. Request yours.

The figures

Every figure on this page, sourced

The figures in this case are sourced in the text above.