What we find goes to you first.
Run one of the startups we follow? The walkthrough and the problems we find reach you before anything is public. A problem shows on your page only in a line Connor writes, marked open or fixed with its dates. This page is the whole path, in five stops.
75 startups followed, read every day from their own public pages; when we review one, from our own account, as any customer would.
From the work we do first to a call with Connor
- 01
The work first
Before you hear from us, we do something for you: a bug on the money path found, a teardown, an introduction. Sent privately, by Connor.
- 02
Your page
Why we follow you, what you are hiring for, the work log, and once Connor has used your product, what we found.
- 03
Claim it
Sign in with your work address and tell us your role. Connor checks it is you, usually the same day. A request, never an automatic key.
- 04
The portal
What is waiting on you, the walkthrough, every finding we sent you with its state, and what is public set beside what only you see.
- 05
Talk to Connor
Thirty minutes, any weekday afternoon, UK time. Bring what we found, or bring what you need. No pitch.
Public on your page, and yours only
The left column is on your page for anyone to read, each line with the moment it goes live. The right column never leaves the portal.
Public on your page
goes live- Why we track you, in one lineyour first day on the roster
- The work log: fixes, pull requests, visitors sentonce Connor publishes it, dated
- A problem we found, in Connor’s wordsonce he writes its line
- “Fixed” beside a problemafter Connor re-checks it
- The review and its walkthroughonce Connor publishes it
- Your asks, and how many are filledwhen you post one
- Your replies, marked from the companyonce Connor publishes them
Only you see
in the portal- Finding titles and detail, and where we saw eachalways
- Your replies on each findinguntil Connor publishes one
- The walkthrough, unlisteduntil a public cut is cleared
- A head-to-head table, before it is publicfor its seven days
- Security problems, sent to your security contactnever on any page
See what a crawler, an AI agent and a first-time visitor find on your public pages
Whether it renders without JavaScript, your link preview, llms.txt, sitemap, status page, changelog and job listings. No sign-up.
These are the same checks we run every day on the startups we follow. The result is yours alone; it never touches your page.
- 01We read at most nine public pages: your homepage, robots.txt, llms.txt, your sitemap, and the status, changelog and careers pages your homepage links to.
- 02We follow your robots.txt, and if your site answers “too many requests” we stop at once.
- 03We never sign up, log in, fill in a form or test for security holes.
- 04The result is shown only to you. We keep it for ten minutes so repeat checks don’t hit your site again, then it is gone. We don’t ask for your name or email.
A review is not for sale.
No one pays for a review, a better mark, a faster one or a kinder line. Any money between us and a company is declared at the top of its review. Money and relationships
Security problems never appear anywhere, claimed or not.
They go to your security contact, on their own, by email. They are in no count, no chapter and no line on any page, and claiming your page changes none of that.
What we find goes to you first. The practice starts by doing the work, and if you want a hand with something, get in touch.