It may look odd for a company that builds sites to write this. But a site built too early tends to sit there having consumed money and time while teaching you nothing, and the lesson people take away is the wrong one: “websites did not work for us”. Changing the order avoids both outcomes.
What a website actually solves
A website is not a general-purpose answer; it is a tool specialised for a few problems. It lets people find you through search, saves you repeating the same explanation to every newcomer, assembles your evidence of credibility in one place, and gives enquiries somewhere to land.
Put the other way round: if what you sell is not settled yet, or nobody has confirmed they want it, a website will not answer that question for you. A site with no visitors produces no data either.
When validating first is the better move
The stage that matters most is never having quoted a price. Price is not decided on a website; it is learned in conversation. A price you write after quoting it a few times and living with the reaction is a completely different number from one you imagined.
In the right-hand column a site pays off immediately. Repeating the same explanation means that explanation can be moved into written once, used many times form — which is the thing websites are best at.
Validating without a site
The one-sentence offer states whose problem you solve, which problem, and at what price. If that sentence will not come, there is nothing to put on a home page anyway.
Saying it to people means putting the sentence in front of real humans: prospects you already know, a relevant community, an offline gathering. What you are listening for is not “that sounds good” but willingness to pay.
Recording reactions means writing down what you heard, verbatim. The reasons for refusal are the valuable part. Too expensive, not needed, or not right now are three completely different signals and lead to three different next steps.
The point is that none of this needs a website. It needs one sentence and some conversations — and the phrasing that survives becomes your copy later.
So when do you build?
The signals are usually unambiguous. The same question asked three or more times, enquiries arriving from somewhere other than referrals, or a partner or institution asking for company details — any one of those and a site starts working from day one.
By then the raw material is already gathered. Questions from validation become the FAQ, the explanation you kept repeating becomes the service page, and the reasons for refusal become the “not included” list. Keeping the order makes building the site much faster too.
When that point arrives, the launching on your own series walks from domain to launch checklist in order, and the reasoning behind those calls sits in the Servers & infrastructure archive. If you would rather hand the build over, read the scope and conditions of our optimization program first — including who it is not a fit for.