Build something useful before chasing traffic.

Give the visit a purpose

A studio website can publish fifty pages and still give a prospective client very little to use. Descriptions of services explain the offer. They do not necessarily help someone understand their own problem.

Our view is that a small tool should earn its place by answering one specific question. How far is a review rating from a target? Which business facts belong in a schema graph? What would have to be true for a search budget to pay back? Those questions create a useful interaction before a sales conversation.

The formula is part of the product

A polished result with hidden assumptions is weak evidence. If a calculator says a campaign could generate £10,000, the visitor should be able to trace that number back to traffic, conversion, customer value and cost.

We would rather show a modest result that can be challenged than a large result designed to collect an email address. The visitor should be able to change the inputs, see an impossible case and take away the workings. This is also how a tool demonstrates technical judgement.

Keep the first version narrow

A review calculator does not need a login, CRM or connection to every Google profile. Manual inputs can make the first version fast, private and easy to verify. Connections become useful when repeat use creates a clear need for them.

That boundary matters. Every stored input introduces questions about access, retention, consent and deletion. A tool that can do its job in the browser has a simpler operating model. We add persistence when it benefits the user, then explain exactly what is stored.

Measure usefulness before volume

Tool use can be a helpful signal. It is not proof of purchase intent, and downloads are not revenue. We would assess the quality of the resulting decisions before using traffic growth as the headline.

• Can a first-time visitor explain the result?
• Does changing an assumption change the result as expected?
• Can they export or use the output without speaking to sales?
• Does a later enquiry contain a better-defined problem?

Sometimes a guide is the better product

Not every problem is arithmetic. A guide is better when someone needs judgement, a sequence of checks or an explanation of a trade-off. The test is the same: does the page remove a real obstacle?

Start with the obstacle, then choose the format. A tool, a documented example and a short checklist can all be more useful than a large content calendar with no clear reader task.