First impression
What a new visitor is likely to notice and understand first.
Optional private feedback
See your project through fresh eyes.
A Fresh Eyes Report shows you how your project reads to a new visitor. You get private, practical notes on what is clear, what is confusing, and what I would change first. A person checks every report before delivery.
The free submission is saved before checkout. Buying private feedback does not affect Project Note selection or wording.
What is included
Clarity and messaging
Notes on the main promise, primary call to action, and language that needs more context.
Trust cues
Which details build confidence and which ones raise questions.
What to change next
A short list of specific improvements and why each one may matter.
Complete sample report
Fresh eyes on Project Radar
We wrote this sample about our own site using its public copy on September 4, 2026. It is an editorial example, not a customer report or proof of user testing. The linked pages may have changed since then.
Copy snapshot:
Project snapshot
Project Radar helps readers find indie software. Selected projects get a public profile and a longer Project Note. Makers can submit for free, then choose whether to buy private feedback.
Intended reader. Readers looking for a useful tool and makers deciding whether to submit a project.
Source pages: Homepage, All Projects and its profile pages, Submit, How Project Notes Work, and this offer page.
First impression
The homepage clearly says that payment does not influence editorial coverage. Readers get a search box, while makers get a submission link. I would keep those paths separate. The opening copy spends more time on editorial independence than on what readers can find in the directory.
- Homepage
- Somewhat clear
The purpose is visible, but the page could say more clearly what readers will find.
- Messaging
- Somewhat clear
The difference between a profile and a Project Note needs a clearer explanation.
- Calls to action
- Clear
Search, browse, and submit each tell the reader what happens next.
- Trust signals
- Clear
The pages state the editorial policy. This sample does not verify how every decision is made.
- Pricing
- Clear
The copy separates free submission from the optional $19 one-time report.
- Mobile experience
- Not reviewed
This sample does not include a device or layout test.
- Onboarding
- Not reviewed
No submission, email delivery, owner login, or purchase was completed for this sample.
What felt clear
- The homepage separates the reader and maker paths. A maker can go straight to submission without opening the directory first.
- The submission page says coverage is a possibility and describes the public page a selected project may receive. It does not promise customers or traffic.
- The Fresh Eyes offer states the price, describes the private report, and says payment does not affect public Project Notes. Keep that statement beside the purchase path.
What needs more context
- The homepage repeats its rule about paid editorial influence in the introduction and editorial panel. Readers must scroll farther to see what kinds of apps, websites, and tools are in the directory.
- The directory says a profile contains the full ProjectRadar note. Profiles have a short version and a separate Project Note link, so that promise needs more precise wording.
- The submission page lists what a published project may receive, but it does not show an example profile there. A new maker has to leave the form and find one.
Calls to action and messaging
Keep Browse projects beside search so readers can explore without knowing a product name. For makers, keep free submission explicit and explain the optional report after the submission is saved. A new visitor should not have to understand the paid offer before submitting.
Trust and confidence
The process page explains that automation may help with drafting, an editor makes the final decision, and readers can request corrections. This sample reviews that wording only. It does not prove that every published note followed the process.
Changes I would make first
1. Give readers one concrete reason to browse
The homepage introduction and side panel both explain that sponsorship does not affect editorial selection. That policy matters, but visitors also need to know what they can find in the directory.
Keep the independence statement and use the supporting paragraph to explain the catalog: "Find indie apps, websites, and tools, with a short explanation of who each project may help and a link to try it."
Homepage introduction and editorial panel2. Explain the profile and the full note at the directory entrance
The directory promises the full note on the profile, while the profile links to the longer Project Note separately. Readers should know which page they will open and what each page contains.
Use: "Open a profile for a short overview and the official project link. Follow its Project Note link for the longer write-up." Use the same distinction wherever these two pages are introduced.
All Projects introduction and linked profiles3. Show a published example beside the submission explanation
The "What you may get if published" section lists a profile, Project Note, official link, and discovery opportunities without linking to an example there. An example lets makers judge the result before completing the form.
Add one existing profile and its Project Note with the label "See an example of a published project." Keep the surrounding statement that coverage is not guaranteed.
Submission page, What you may get if published
Biggest opportunity
Show the result at each entrance. Readers need an example of what they can find. Makers need an example of the page their project might receive. Existing profiles and notes can do both jobs.
Final takeaway
I would start with the homepage copy, then explain the difference between a profile and a note and add a submission example. These changes aim to make the site easier to understand. Measure their effect on visits, submissions, and sales after release.
How it works
- 1.Send a free project submission.
- 2.Use the private upgrade link shown after the submission is saved.
- 3.Complete secure Stripe checkout.
- 4.A human checks the draft before the private report is delivered.
The report is delivered through a private link after a human check. If it is still undelivered 7 business days after payment, you can request a full refund. You can also request a full refund any time before delivery.
What it is not
A Fresh Eyes Report is private first-impression feedback. It is not a formal UX, technical, or security audit. It is also not growth consulting, investment advice, market sizing, or paid public placement.
Public Project Notes are curated separately. The report does not buy favorable language or a better editorial position.
Start with the free path