Skip to content

Experiment 2: Email-first hero CTA - #3

Open
slowe89 wants to merge 2 commits into
mainfrom
cursor/email-first-cta-bf89
Open

slowe89 wants to merge 2 commits into
mainfrom
cursor/email-first-cta-bf89

Conversation

@slowe89

@slowe89 slowe89 commented Sep 12, 2026

Copy link
Copy Markdown
Owner

Implements Experiment 2 — Email-First CTA on the EvalCase waitlist page. PR only — do not merge or deploy without Spencer OK.

Hypothesis: Cold visitors bounce on the scorecard + multi-field Priestley interview; an email-only above-the-fold capture should raise top-of-funnel.

What changed

  • Hero primary CTA is now an inline Work email field + Send me the scorecard button.
  • Posts via the existing FormSubmit AJAX helper to https://formsubmit.co/ajax/thespencerlowe@gmail.com.
  • Hidden fields: _subject=EvalCase email-first CTA, _template=table, _captcha=false, _honey, source=evalcase-email-first, cta=hero-email-only.
  • Email is the only required field (no budget, Q1–Q5, or maturity radios).
  • Success copy: “Got it — we’ll reply from thespencerlowe@gmail.com with the scorecard link.”
  • Secondary: “Or take the Eval Maturity Score first” → #scorecard (data-source=evalcase-scorecard).
  • Tertiary: “Tell us more about your setup” → #waitlist (data-source=evalcase-waitlist).
  • Scorecard (10 yes/no) and full Priestley waitlist form stay below / as secondary paths.
  • Soft pricing table unchanged (Starter $4,997–$9,997 · Domain $12,000–$25,000 · Refresh $1,497–$3,997/mo · demand-test caveat · no payment here).

Proof

Hero desktop — email-only CTA visible without scrolling:

Hero desktop with work-email field and Send me the scorecard button above the fold

Hero mobile (375×667) — field stacked above button, both above the fold:

Hero mobile 375 width with stacked email field and submit button above the fold

Mocked submit success (no live lead sent):

Hero success state after mocked FormSubmit showing scorecard-link reply copy

Soft pricing honesty unchanged:

Early pricing table with estimated ranges and no-payment caveat

Repo copies: docs/experiment-2/hero-desktop.png, hero-mobile.png, hero-desktop-success.png, pricing-desktop.png.

Local verification

  • Vite preview at 1280×800, 375×667, and 390×844: email field + button fully in the first viewport; scorecard starts ~1698px down on desktop.
  • Mocked FormSubmit: hero POST goes to https://formsubmit.co/ajax/thespencerlowe@gmail.com with source=evalcase-email-first. No live inbox probe from this run.
  • Scorecard still scores (70/100 fixture). Full Priestley form still succeeds independently.
  • Production build succeeds. No SOLVD strings. No Vercel deploy from this run.

Acceptance

  • Branch from default; PR open (not merged)
  • Hero email-only FormSubmit → thespencerlowe@gmail.com
  • source=evalcase-email-first on that submit
  • Scorecard + Priestley retained below / secondary
  • Soft pricing honesty preserved
  • Screenshots in PR (hero desktop + mobile)
  • No SOLVD; no ads; no deploy from this agent run

Orchestrator next (Spencer-gated)

Review → merge → Vercel Hobby auto/redeploy → probe FormSubmit tagged source=evalcase-email-first → log in week1 distribution file.

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

cursoragent and others added 2 commits September 12, 2026 17:54
Replace the above-fold scorecard/waitlist button pair with a work-email
FormSubmit capture (source=evalcase-email-first). Keep the maturity
scorecard and full Priestley form as secondary paths, and leave soft
pricing ranges and caveats unchanged.

Co-authored-by: slowe89 <slowe89@users.noreply.github.com>
Keep the email input at control height on stacked mobile layout, and
attach desktop/mobile proof that the email-only CTA sits above the fold.

Co-authored-by: slowe89 <slowe89@users.noreply.github.com>
@slowe89
slowe89 marked this pull request as ready for review September 12, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants