Readiness score
Twelve questions, weighted by how much each one actually moves the outcome. It is built to be able to tell you no. About a third of the people who answer it honestly get told to wait, which is the same third we turn away when they apply.
Answer every line. A half-filled score flatters you, which is the opposite of what this is for.
The nine queries
The diagnostic we run at the start of every build, and there is no reason you cannot run it yourself in ten minutes. Type your name and the nine links below become live Google searches. Open each in a private window and write down what you see.
Query one is the only one that decides whether you have a panel. The other eight tell you why. If your name returns somebody else, that is a namesake problem. If it returns you but thinly, that is a corroboration problem. If it returns nothing recognisable, that is a build, and it starts at ninety days.
Why this can say no
A panel will not trigger and will not stick on an empty entity home and blank schema. There is no configuration of effort that makes Google confident about somebody the public web has nothing to say about.
That is not a character judgement, it is a sequence problem. The evidence has to exist before it can be organised. If you score low here, the honest next step is six months of real-world work — publish something, speak somewhere, get written about by somebody independent — and then come back and run this again.
Selling a build at that stage would just be selling you a twelve-month refund with extra steps.
| 75–100 | Claim job. Weeks, not months. |
| 45–74 | The normal starting point. Six to twelve months. |
| 20–44 | Foundation first. Come back in six months. |
| 0–19 | No. And nobody honest will take it on. |