# Feedback Sprint Report: DRE Landing Page (3-variant comparison)

**Product:** Debt Recovery Experts (DRE) — Texas commercial/consumer debt recovery
**URLs:**
- A: https://mockups.itpropartner.com/dre/institutional-trust.html
- B: https://mockups.itpropartner.com/dre/conversion-results.html
- C: https://mockups.itpropartner.com/dre/modern-platform.html
**Date:** 2026-08-21
**Reviewers:** 3 dispatched, 3 survived moderation (0 rejected)
**Model:** claude-sonnet-5 (delegation-pinned), rotated order, blind

---

## Verdict

> **Ready after 3 blocking fixes** — institutional-trust wins the identity vote
> (8/6/4 scoreboard, 2 of 3 first-place votes, 2 of 3 identity picks), but it ships
> with a legal-liability risk in the logo subtitle, visible placeholder brackets,
> and a weak CTA hierarchy. Those three are gating; a fourth item (real proof
> points) is a launch-gate, not a mockup fix.

## Scoreboard (3/2/1 by rank)

| Candidate | A | B | C | Total |
|---|---|---|---|---|
| institutional-trust.html | 2 | 3 | 3 | **8** |
| conversion-results.html | 3 | 2 | 1 | **6** |
| modern-platform.html | 1 | 1 | 2 | **4** |

**Identity pick:** institutional-trust (B + C). Reviewer A picked conversion-results.
Clear winner, not a tie.

## Blocking fixes (must fix before shipping institutional-trust)

1. **"TEXAS DEBT RECOVERY COUNSEL" logo subtitle** — implies attorney/legal
   representation. A debt collector cannot present itself as a law firm (FDCPA /
   deceptive-practice exposure). Reword to "LICENSED TEXAS RECOVERY FIRM" or drop
   "Counsel" entirely. Flagged by B (#1 fix) and A.
2. **Visible placeholder brackets** — "[Phone number]", "[Office address]",
   "[Licensing and bond information placeholder]" in the top utility bar and footer.
   Resolve with real content before launch. Flagged by A + B.
3. **CTA hierarchy** — "Submit a Claim" and "Make a Payment" carry near-equal
   visual weight (solid navy vs outline), and the header "Client Login" adds a
   third similar navy button. Make "Submit a Claim" the unambiguous primary.
   Flagged by A + C.

## Launch-gate (not a mockup fix — requires real data)

4. **Proof of results** — zero testimonials, case studies, recovery-rate stats, or
   years-in-business anywhere. Intentional (mockups were built under a
   no-fabricated-stats rule) and correct to leave blank, but a real prospect
   evaluating a recovery firm expects it. Supply real numbers before the site goes
   live. Flagged by all 3 reviewers.

## Secondary polish (non-blocking)

- **Hero is a text wall** — no visual in the hero despite a "track it in real time"
  subhead promise. Add a lightweight dashboard/portal visual. (A #1)
- **"Ready to place an account?"** — "place an account" is industry jargon; use
  "Submit a Claim" plain language. (B #3)
- **"SEC" compliance badge** — reads as Securities and Exchange Commission, not
  "Secure data handling." Relabel (lock icon / "DATA"). (C #3)
- **Compliance strip blends into header** — both dark navy; differentiate the top
  strip so it reads as a distinct trust signal. (C #1)

## Positioning check (target-user guess)

| Reviewer | Guessed target user | Match? |
|---|---|---|
| A | Texas SMB owner/bookkeeper, compliance-conscious, owed money | Yes |
| B | Risk-averse Texas business, finance/legal/ops, wary of aggressive collectors | Yes |
| C | Texas SMB, finance/legal-adjacent decision-maker, risk-averse | Yes |

**Reading:** PASS. All three independently named the same user — a Texas business
owed money, specifically a risk/compliance-conscious buyer — with no positioning
telegraph. This confirms the two-sided (creditor + debtor) structure lands, and
that debt recovery is a trust-first purchase. The institutional-trust direction
consistently pulled the "risk-averse, compliance-conscious" read that matches the
actual target; conversion-results pulled "transactional/urgent," modern-platform
pulled "tech-forward SaaS" — i.e. the winning design direction also produces the
most accurate target-user read.

## Consensus pros

- Dual CTA (Submit a Claim / Make a Payment) cleanly splits creditor vs debtor — all 3.
- Explicit FDCPA + TDCPA naming with plain-English explanations = strongest trust
  signal; institutional-trust does it best (A + B).
- "No upfront retainer required" objection handler placed at the decision point (A + C).
- Serif + navy/gold register reads as "institutional/law-adjacent," distinct from
  generic SaaS (all 3, on institutional-trust).

## Consensus cons

- Hero placeholder brackets = single most credibility-damaging element
  (conversion-results "[Recovery rate]", modern-platform "[Account name]") — all 3.
- No social proof / testimonials / recovery stats — all 3.
- "Counsel" subtitle implies law-firm relationship (liability) — A + B.
- No pricing/fee model (contingency vs flat fee) — B + C.

## Taste calls (single-reviewer)

- "without cutting corners" / "not a marketing claim" reads defensive — C only
  (note: A + B both PRAISED the "not a marketing claim" line as a trust win —
  genuine divergence, treat as a split, not a defect).
- Gold accent too subtle / near-monochrome — B + C (borderline consensus).

## Moderation notes

- Submissions rejected as slop: 0.
- All 3 verified `window.location.href` before each review (no cross-reviewer
  browser contamination on the shared session).
- Reviewer C caught and corrected a vision-model confabulation (false "orange"
  accent read on modern-platform; actual CSS is green/cyan) against curl'd CSS.

## Convergence synthesis (per skill)

Keep **institutional-trust** as the identity (serif + navy/gold + compliance-first
is the correct trust register for debt collection). Port the winning elements from
the losing directions:

- **From conversion-results:** benefit-driven headline energy ("Stop chasing...
  Get them recovered."), the "No upfront retainer required" objection handler, and
  the solid-vs-outline CTA hierarchy.
- **From modern-platform:** a single clean dashboard/portal visual in the hero
  (fixes the text-wall gap without adopting the SaaS-first framing).

## What was NOT reviewed

- Mobile navigation behavior (mockups are static, no JS — hamburger/toggle
  functionality out of scope for a static-HTML comparison).
- Backend / portal / intake flows (separate workstream).
- Real legal review of the compliance language (flagged as a required pre-launch
  step by the reviewers themselves).