Honest signup success + concrete pricing CTA

[manazoid4]

Problem

Two small but high-impact copy issues that erode trust at the exact moment a user is about to pay:

1. SignupPage success screen told users "Gold leads for your trade and patch start coming through from day one." That directly contradicted the careful "results may be sparse or empty" language on every other page. A user who just read the honest caveats on /pricing would feel misled the moment checkout completed — and would likely churn inside the first month.
2. PricingPage hero CTA said START £39/MO → but the plan card underneath said START AFTER COVERAGE CHECK →. Ambiguity at the payment step is one of the highest-cost UX failures on a pricing page: users don't know if clicking will charge them or queue something.
3. The /pricing hero H1 was a word-for-word duplicate of the homepage H1 — a wasted moment on the page that actually decides the sale.
4. Post-signup CTA said BROWSE LIVE LEADS → — wrong frame for a public-tender product.

User impact

Small UK contractor (5–25 person firm) evaluating public works. After these changes:

• The signup success screen tells them the truth: they'll run firm-aware qualification against current Find a Tender notices, and coverage depends on what buyers have published — no fake promise of "gold leads from day one."
• The pricing page shows one consistent, concrete offer everywhere: START £39/MO — 30-DAY MONEY-BACK →. No ambiguity about what clicking does.
• The pricing hero opens with a fear-proof-control line specific to contractors: "Every wrong bid costs you a day. Know which public works fit before you prep a quote."
• The post-signup CTA reads SCAN CURRENT TENDERS →, matching the product they signed up for.

Scope

Changed:

• src/pages/SignupPage.tsx — rewrote the confirmation-email panel copy and CTA to match the public-tender product reality.
• src/pages/PricingPage.tsx — new hero H1 + supporting paragraph, aligned plan-card CTA with hero, added money-back reassurance line, standardised free CTA to SCAN FREE — NO CARD NEEDED →.

Deliberately left out:

• The "leads / jobs" vocabulary across FindJobsPage was flagged as a UX issue too, but it ripples across dozens of pages, existing components, and the tenders-vs-leads storefront narrative. That's a scoped rewrite of its own, not a copy tweak — deferring to a dedicated PR.
• No component, layout, or design-system changes. Copy only.

Verification

• npm run lint — npx tsc --noEmit clean.
• npm run build — clean Next.js production build, no route errors.
• Relevant regression checks — no runtime paths touched, only static copy strings.

Remaining risk

None operational. Both changed pages are static (aside from Supabase signup submission on SignupPage, which was not touched). If a real UK tradesman lands on /pricing or completes signup right now, nothing breaks and nothing confuses them.

---

Generated by Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
job-filter-v1	Ready	Preview	Aug 18, 2026 12:50pm

[supabase]

This pull request has been ignored for the connected project nfjwuwsuaapufmkppoeo because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[alwaysmeticulous]

✅ Meticulous spotted 0 visual differences across 169 screens tested: view results.

Meticulous evaluated ~4 hours of user flows against your PR.

_{Expected differences? Click here. Last updated for commit 2263e1f Update next-env.d.ts (generated by Next.js build). This comment will update as new commits are pushed.}