Fourteen Words: Writing a Homepage Definition

Under the hero on our homepage there are four sentences. Fourteen words in total. They took longer than anything else on the page.

This is a short piece about why they are short.

The hero does not tell you what we sell

Our opening is a line drawing of a journey with a conversation building beside it. It is deliberately oblique. It has a mood and a sequence and no product name in a sentence anywhere.

That is a real cost and we accepted it knowingly: a stranger who reaches the bottom of the hero still cannot say what Duvi is. Something got built, someone was travelling, there was blue.

So the thing immediately after has exactly one job, and it is not to continue the mood.

Four lines, and the first word of each is the actor

The block is four sentences and nothing else. No illustration inside it, no supporting paragraph, no three-column breakdown of benefits.

Each line begins with whoever is doing the thing. Those opening words take the transcript's colouring, and the colouring is the argument: the agent is the accent, you are not. Three blue words run down the left edge and one that isn't.

You act once. It acts three times.

Nobody has to be told that. It is carried by which words are blue and where they sit, and it arrives before the sentences are finished being read.

Why it stays compact

The obvious treatment is one sentence per screen, each beside a screenshot, scrolling. Every marketing site does this and it is not stupid: it gives each idea room and it fills a page that needs filling.

It would have destroyed this particular block, because fourteen words only work if they are read as a set. The relationship between the four lines is the content. Separate them by a screen each and you have four unremarkable claims instead of one shape.

So it stays in one compact block, at a size you take in at once, and the page moves on.

Proof goes after, not inside

Below the definition is a screenshot of the builder being asked for an agent and writing the configuration next to the conversation.

It sits in the same band rather than getting a section of its own, because it is the definition's evidence and not a second topic. It carries no caption, because the four sentences above are its caption. That is the whole reason the definition can stay abstract: it does not need to describe the software when the software is directly underneath.

Everything above that point is drawn, borrowed, or typographic. Nothing on the page had yet proved the product existed. The builder is the shot to lead with, because describing an agent into existence is the uncommon thing, and because the hero has spent five stations drawing that exact conversation. The screenshot is the evidence it was not a fantasy.

It also needs a frame. A plain rectangle of screenshot reads as pasted. Ours takes the shell radius and a gradient across the bottom fading into the page ground, which is what stops it looking dropped in.

What we deleted

Three destination links used to follow the hero. They are gone. They duplicated the navigation and the footer, which both still carry the documentation, the blog, and Studio. Nothing became unreachable and the page got quieter.

There is no call to action in the hero at all. The navigation has one. A visitor who wants Studio can find it in the place people look for it.

The cost of writing this way

Compression like this is expensive in a way that does not show up in the artifact. Fourteen words cost more per word than fourteen hundred, and there is no way to tell by looking that they did.

It also has to stay true. The nice thing about four short sentences is that there is nowhere for a hedge to hide. You cannot qualify your way out of a fourteen-word claim. If the product stops doing one of those four things, the sentence is simply wrong, and anyone can see it.

That is the point of writing it this way. The constraint is not aesthetic. It is that a claim short enough to check is a claim you have to keep.