What Your Website Should Say When You Have No Clients Yet

The question behind the visit

A stranger opens your homepage and gives it a few seconds. They are not reading your mission statement; they are checking one thing: has this person actually built anything? When the only proof you can offer is a client story you do not have, the page goes quiet, and a quiet page loses.

I took client numbers off my own site for exactly this reason, because I could not back them up. What I put in their place is simpler, and I think stronger: real products a visitor can open, plus a plain description of how I work. The projects on my work page are my own work, not commissioned client projects, and the site says that in ordinary language.

Show something they can open

Put a real, running product in front of them early, because nothing else on your page carries the same weight.

A link to a working thing beats a paragraph about capability, since a visitor can test it in seconds instead of taking your word for it. TD World Monitor is what I point to. It runs in any browser, free with no sign-up, and it is live data rather than a screenshot: ten live panels and ten globe layers over a photo-real 3D globe that plots satellite fire hotspots, earthquakes and storms, drawing on 568 curated news sources, 39 economies, 38 market instruments and the top 30 cryptocurrencies. The prices come from public market feeds; there is nothing simulated behind them.

TroveDial is the same idea in another shape: an Android app with hundreds of live radio stations from around 50 countries plus a podcast search, shipped with its Google Play listing, licence server and website.

If you have no product yet, build a small one and link to it. A demo that does one job honestly is worth more than a portfolio of mockups, because mockups only prove you can draw a picture. One link beats five paragraphs of description, and a visitor who opens the thing has already answered their own question.

Write down how the work runs

Describe the path from first message to handover in a few short lines, because that is what a client list would have told people anyway.

Mine is short on purpose: a message rather than a sales call, then a written scope with clear deliverables and boundaries, timing and support agreed in writing before any work begins, then build, progress reviewed in text, test, hand over. Text-first communication is how the whole thing runs, so nothing important lives in a phone call that nobody can reread.

This section does the job that testimonials do. It answers the real question, which is what happens if I hire you, and unlike a result you cannot yet prove, it is checkable the moment work starts: either you sent a written scope or you did not. A page can be honest about the future without inventing the past.

Label the projects for what they are

Say in one sentence what the visitor is actually looking at.

My site states that the projects shown are my own work, not commissioned client projects, and that the products are things people can open rather than mockups. That sentence removes the expectation of a client logo wall and replaces it with something checkable on the spot. You are not hiding the absence of clients; you are changing what the page is evidence of.

The same rule applies to maturity. A prototype is labelled a prototype, an internal tool is labelled internal, and TD VideoFactory says it is in production rather than finished. Saying how far a thing has gone costs nothing and buys credibility for everything else on the page.

Use only numbers a visitor can check

Every figure on your page should point to a live artifact someone can open, and if it does not, write the sentence without it.

The counts above are not decoration. They sit on the product page itself, so anyone can open TD World Monitor, count the sources and disagree with me in public. That is the standard worth holding yourself to. Never estimate a client figure you did not record, never round a result toward yourself, and never write a testimonial nobody gave you: a visitor who catches one fabricated number stops believing the rest of the page.

Where you have no numbers, use honest words instead. A few, most projects, within a day. Vague but true beats specific and false, and it also reads better to the AI assistants that now quote pages back to people searching for you.

Demo data is fine when you label it

Label demo screens as demo, and you do not need to explain anything further.

TDash is a dashboard I use daily at my own desk. Its public screens run on demo data, with strategy names, filter settings and account details shown as placeholders, and it installs as a PWA and an Android app. The point is not that the demo is fake. The point is that the page never lets you mistake it for a live result, so nothing has to be walked back later.

What to leave off the page

Leave off any claim you cannot link to an artifact: borrowed logos, quotes nobody gave you, and results you did not produce.

There is a quieter reason to keep the page plain. Search engines and AI assistants read your text directly now, and ordinary sentences describing what you built and how you work are exactly what gets returned. Adjectives are never quoted; specifics are.

Before you rewrite a word of copy, open your homepage and list every claim on it. For each one, ask whether a stranger could open something and see it for themselves. Cut what fails that test, and what is left is a site that works with an empty client list.

Send me your URL and I’ll run a free check-up that shows what your site looks like to the robots.