Sample Report — Market-Sentiment Review Desk

Sample report. The product reviewed below is fictional. This report is published only to show buyers what the deliverable looks like.

Classification: Public sample Tier illustrated: Standard Review ($497) Reviewer: S. Mitchell, Market-Sentiment Review Desk Review date (illustrative): 2026-04-22 Subject (fictional): Cadenza — a B2B team-rituals SaaS Public URL reviewed (fictional): https://cadenza.example/

Decision-support only. Not legal, financial, regulatory, medical, or professional advice. No outcome, revenue, fundraising, or conversion result is asserted, implied, or promised.

0. About this document

This is a published sample. Cadenza is not a real product, and none of the screenshots, quotes, or pricing details below describe a real company. We publish this so prospective buyers can see what they actually receive when they commission a Standard Review.

A real Standard Review of your launch page is delivered as a similar document — typically 6 to 10 pages — within five business days of intake. We send one PDF, one Markdown copy, and a single follow-up email three weeks later asking whether anything changed.

1. Executive summary

Cadenza's public launch page leads with a feature list before establishing who the product is for. Cold visitors arriving from Show HN or a Substack share are likely to bounce inside the first screen because the hero promise ("rituals, reimagined for modern teams") is abstract, and the three feature tiles immediately beneath it do not name a job-to-be-done. The trust block — three generic stock photos and a "trusted by ambitious teams" line — sits below the fold and contains no named customers, no logos, and no quotes. Pricing is visible but the cheapest tier is gated behind a 9-field "request demo" form that asks for company size, role, budget range, and use case before showing the actual price for that tier.

Three of these gaps are cheap to fix this week. One is a positioning question that will take a real founder decision. None of the gaps are evidence of a bad product — they are evidence of a launch page that was written by people who already know what Cadenza does, for visitors who don't.

The rest of this report names each gap, points at the specific block on the public page that produced it, and proposes the lightest fix that would close it.

2. Scope and method

What we reviewed:

The public URL above as rendered on a 1440-wide laptop, on a 390-wide mobile viewport, and as a LinkedIn / X share card.
The pricing page and the demo-request form.
The footer (legal, contact, postal address).
The first three pages of indexed content (sitemap-visible).

What we did NOT review:

Account-gated content, the in-product experience, or anything behind the demo-request form.
Pricing fairness vs. competitors. (We do not estimate revenue lift, conversion lift, or fundraising outcomes.)
Marketing-channel attribution, ad creative, or paid funnel.
Anything that would require an NDA, internal data, or access to the product itself.

Method: one reviewer, one focused read, one written deliverable. No models. No agents. No predictions. We name the gap and the lightest fix; the founder decides whether to act.

3. Findings

3.1 Hero promise does not name a job-to-be-done

Observation: The current hero reads "Cadenza — rituals, reimagined for modern teams." The sub-hero adds "Cadenza makes team rituals effortless." Neither line names what a "team ritual" is, who on the team owns it, what changes after Cadenza is installed, or what specifically gets easier.

Why this matters for a cold visitor: A Show HN visitor reaches the page with roughly 8 seconds of patience. If those 8 seconds do not produce a concrete sentence the visitor can repeat to a co-worker, the visitor bounces. "Rituals, reimagined" is a thesis, not a sentence the visitor can repeat.

Suggested experiment (lightest fix): Replace the hero pair with a concrete outcome line plus a one-line proof. Example direction (not prescriptive — the founder should pick the verb that's true):

"Cut your team's weekly standup from 25 minutes to 10 — without changing tools." "Used by engineering teams of 8 to 60 to run async standups, retros, and pulse checks."

This is one test. We are not predicting a lift; we are predicting that more visitors will be able to repeat the sentence after reading it.

3.2 Three feature tiles do not name a buyer

Observation: Below the hero, three tiles say "Standups", "Retros", "Pulse". Each tile has a 12-word description and a small animation. No tile names a buyer role (e.g., engineering manager, head of people, founder).

Why it matters: Visitors do not buy "standups" — buyers buy relief from a specific painful Monday. Without a buyer named, the page is asking the visitor to do the translation work.

Suggested experiment: Reword each tile so the first word names the buyer's pain. Example direction:

"Your engineering manager spends 35 minutes a day in standup. Cut it to 10."

Keep the tile animations. Replace the tile copy.

3.3 Trust block uses stock imagery and an unverifiable claim

Observation: A horizontal strip near the middle of the page shows three stock photos of laptops, with the caption "Trusted by ambitious teams." No named customer, no logo, no quote. A reverse image search returns the three photos as stock library images, which is verifiable from the public page alone.

Why it matters: "Trusted by ambitious teams" is an unverifiable claim. A cold visitor who notices the stock imagery will discount everything else on the page, because the page has just shown the visitor that it is willing to imply something it cannot prove.

Suggested experiment: Either replace the strip with one named customer (logo + a one-sentence quote signed with a real name and role), or delete the strip entirely. Deleting it is better than keeping a claim the visitor will discount.

This is the single highest-priority change in this report. The gap costs more than the rest combined because it casts shadow on every other claim above and below it.

3.4 Pricing-page friction: 9-field gate in front of the cheap tier

Observation: The pricing page shows three tiers — Team ($12/seat/month), Business (price gated), Enterprise (price gated). The Team tier's "Start" button does not start anything; it opens a 9-field "Request Demo" form (name, company name, company size, role, team size, current tooling, budget range, use case, message).

Why it matters: The Team tier is the on-ramp; gating it behind a 9-field form means cold visitors who would have started free or self-served will never reach the product. The form length also signals to the visitor that Cadenza expects a sales motion, which conflicts with the $12 price point.

Suggested experiment: Make the Team tier self-serve. Reduce the form to three fields (email, role, team size). Keep the 9-field form on Business and Enterprise tiers, where a sales motion is appropriate to the price.

3.5 Above-the-fold CTA repeated six times, no secondary path

Observation: "Get started" appears six times above the fold (hero, sub-hero, top nav, first feature tile, sticky header, mobile bottom bar). No secondary, lower-commitment path appears anywhere above the fold.

Why it matters: Cold visitors are not ready to "get started." They are ready to look. Pushing the same high-commitment CTA six times in one screen reads as pressure, even though pressure is not the intent.

Suggested experiment: Keep one prominent "Get started." Add one quieter secondary CTA next to it: "See a 90-second tour" (no email required). Drop the count from six to two above the fold.

3.6 Footer missing two items the visitor expects

Observation: The footer contains the legal entity name, a contact email, and three nav links. It does not contain a postal address, a published privacy policy link, or a published terms link.

Why it matters: The missing postal address is a credibility problem for buyers in regulated industries (the page lists healthcare and fintech in its target list). It is also required in most jurisdictions once Cadenza begins any cold outreach. A B2B buyer who clicks the footer and finds no address has just learned that the company is not yet ready for them.

Suggested experiment: Add the registered postal address, a link to the privacy policy, and a link to the terms. This is a 10-minute fix, but it shifts the trust band by more than the time spent.

3.7 Share card (LinkedIn / X) describes a different product

Observation: Pasting the URL into LinkedIn's post inspector returns a card titled "Cadenza — the AI rhythm engine for product teams." The current public page does not use the word "AI" once, and "rhythm engine" appears nowhere. The share card metadata appears to be from an earlier draft of the page.

Why it matters: A B2B buyer who sees one pitch on LinkedIn, clicks, and reads a different pitch on the page assumes a disorganized team. Some buyers stop there.

Suggested experiment: Update the per-route Open Graph and Twitter meta to match the current hero copy. This is a one-line fix per tag.

4. Things working well

A balanced read names what is working so the founder does not delete it during the rewrite.

The pricing page itself is clean — three tiers, no anchoring tricks, no false scarcity. The friction is the gate in front of Team, not the pricing layout.
The product screenshots (further down the page) are the strongest asset on the entire site. They show a real product, with real text, doing a real thing. Move at least one above the fold.
The blog has three posts that read like they were written by an engineer who has actually run a standup. They are buried under /resources. Surface them in the footer at minimum.
The mobile layout reflows cleanly. No horizontal scroll, no cropped CTAs. This is rarer than it should be.

5. Visitor objection map

The four objections most likely to fire in the first 30 seconds:

"Who is this actually for?" Hero and tiles do not name a buyer role or company size.
"Is this real, or is it a deck?" Stock imagery in the trust block triggers this.
"Why should I switch from what I already use?" The page names no incumbents and offers no comparison.
"Can I just try it?" The Team tier's gated form answers no.

Each of these is fixable with one of the experiments above. None of them require a product change.

6. Suggested next 14 days

This is a dependency-ordered list, not a roadmap. The founder chooses what to do.

Day 1. Decide whether to keep the stock-photo trust block. If keeping it, replace with one named customer. If not, delete.
Day 1–2. Rewrite hero pair (3.1) and tile copy (3.2).
Day 3. Reduce the Team-tier form to three fields (3.4).
Day 3. Add a "See a 90-second tour" secondary CTA (3.5).
Day 4. Update share-card meta (3.7) and footer (3.6).
Day 5–14. Watch what changes. We do not predict what will change; we are predicting that the visitor will be able to repeat the sentence.

7. What this report does NOT promise

Any conversion rate, click-through rate, signup rate, revenue number, or fundraising outcome.
That the changes proposed are the right changes. They are the changes a single experienced outside reader would suggest after one focused read. The founder is the decision-maker.
That the product is good or bad. We reviewed a public page, not a product.
Any legal, regulatory, financial, fundraising, or medical advice of any kind.

If a different reviewer ran the same review, they would name some of the same gaps and miss others. That is the nature of a one-reviewer outside read. It is a teaser, not an audit.

8. About the reviewer

S. Mitchell has reviewed launch pages for fictional companies for the purpose of this published sample. In a real engagement, you would receive the name and short bio of the actual reviewer assigned to your page before the review begins. We assign one reviewer per engagement. We do not pool, batch, or rotate.

9. Closing

Reviewer: S. Mitchell, Market-Sentiment Review Desk (fictional reviewer, fictional product, published sample)
Contact: [email protected]
Public-facing brand: Market-Sentiment Review Desk
Legal entity: ChristCoin Capital LLC

This sample is fictional. The product reviewed (Cadenza) does not exist. None of the people quoted exist. The pricing, claims, and screenshots described are inventions for the purpose of showing buyers what a real deliverable looks like.

Decision-support only. Not legal, financial, regulatory, medical, or professional advice. No outcome, revenue, fundraising, or conversion result is asserted, implied, or promised.