I stopped asking people to take my word for it. That is how Page Zero began

The problem was not writing a better quote

I have written plenty of quotes. Some were concise; others broke down every last item. They explained pages, functions, timings, costs and responsibilities. That was necessary, but one limitation remained: they described a result that did not yet exist.

For someone reviewing an offer — particularly someone who does not work in digital — terms such as architecture, content hierarchy, accessibility and performance are difficult to turn into something tangible. Comparing the price and counting the pages is easier. The heart of the project, how a website should make sense of a business, is left to the imagination.

A portfolio only solves part of the problem. It proves that I can design and develop, but it records decisions made for different organisations with different goals, content and constraints. A prospective client may appreciate those projects and still reasonably wonder: what has he understood about us?

So I stopped looking for another way to say, “trust me, I will do good work”. A more useful question was this: which part of my method can I make visible before someone has to choose?

A quote can define the scope clearly. It cannot replace proof that I understand what deserves space, order and priority on a homepage.

I did not want to give away a mock-up; I wanted to take on part of the risk

At first, the idea could sound like a free preview. That was not enough. An attractive screen, perhaps put together quickly, would simply add another object to judge without making the method any clearer.

I wanted to show more than an aesthetic. I wanted to take the existing website, understand its public message, choose a different hierarchy and show how those decisions behave in a real, private, navigable page.

That means investing time before a paid commission, knowing the relationship may go no further. It is a real risk, but not a random one. If I ask a business to entrust me with an important project, I can take on some of the uncertainty first instead of transferring all of it to the other side.

Being free is not the value in itself. The value is reaching the conversation with one more fact and one less promise.

Consent comes before any homepage

There is a boundary here that matters to me. I do not pick a business, secretly rebuild its homepage with its logo, images and copy, then turn up with work it never requested. That would be intrusive and would turn a demonstration into sales pressure.

A first contact may begin with two visible, verifiable issues on the public website. I explain Page Zero and invite the owner to request an assessment. Only after an interested response and authorisation to use the materials do I decide whether the case is suitable and, if it is, begin designing.

That sequence is not red tape. It protects the owner, who knows what I am proposing in advance, and it protects my work from becoming a production line of unsolicited mock-ups.

A demonstration needs clear boundaries

When something is free, misunderstandings come easily. A “free homepage” can sound like a small website being given away, a creative contest, or the start of open-ended unpaid work. It is none of those things.

Page Zero is deliberately limited. It does not replace a full website analysis, cover an entire project or provide production material to hand to anyone else. It is there to test a possible direction and how we might work together.

The dedicated page sets out timings, availability, required materials and terms. What matters here is why those boundaries exist: to show enough for a decision without pretending a project can be created without discussion, content and shared responsibility.

What a homepage really needs to demonstrate

The first response to a homepage is often aesthetic: people either like it or they do not. That is inevitable, but for me the demonstration begins one step earlier. The important questions are whether the visitor understands who the business is, what it offers, who it serves and what action makes sense next.

A homepage can be beautiful and still hide the main service. It can look current while using the same interchangeable language as a hundred competitors. It can load quickly and send visitors towards an unclear enquiry. The technical result matters, but it must support a design decision people can understand.

That is why a disagreement about the demonstration can still be useful. Discussing a visible hierarchy is more precise than approving abstract claims in a quote. It reveals whether the issue is a visual choice, missing content or a different understanding of the business itself.

Trust can start with evidence

Showing a homepage before the quote does not remove the risk from a decision. A complete project still requires agreements, content, responsibilities, time and trust. It does mean the relationship does not have to begin entirely with claims that cannot yet be checked.

• whether I understood the business beyond its surface;
• which priorities I assign to the content;
• how I turn a line of reasoning into a real page;
• how clearly I define the scope and its boundaries;
• whether the conversation can become a working relationship.

For me, it means accepting that the method is judged before the commission, not merely described. It is a more exposed position, but it matches the way I want to work: fewer generic promises and more observable decisions.

I cannot know which conversation will become a project. I do know why Page Zero exists and which problem it needs to solve.

In a market crowded with similar offers, I did not want to find a louder way to say that I am different. I wanted to make a difference visible.