← Outcome Pack

Landing Page Conversion

Get Superdense

npm i -g @nimrobo/superdense

How to start

Make a folder, start your agent in it, and say: "/outcome-setup set up a Landing Page Conversion outcome pack for my signup page."

One-time setup

Connectors

  • Analytics — pick one: GA4, PostHog, Mixpanel, or any tool that can track page views, funnel steps, and conversion events.
  • Payment — optional: Stripe or equivalent, to qualify signups by confirming downstream paid conversion.

Before your first run

  • ☐Confirm your analytics tool is installed and receiving page_view events from the landing page.
  • ☐Instrument your signup completion action as a conversion event (e.g. 'signup_completed', a thank-you page view, or equivalent in your tool).
  • ☐Check what funnel steps you can track — native form tracking may not cover SPA or multi-step flows; add custom events where needed.
  • ☐Build a funnel from landing page to signup completion and record the current baseline drop-off % at each step.
  • ☐Record baseline page load performance (Lighthouse, PageSpeed Insights, or equivalent) before making changes.

goal.md

  • North star: % of unique landing-page visitors who complete the signup action, measured in your analytics tool over a consistent window (7 days is a common starting point — adjust to match your traffic volume).
  • Primary metric: signup completions / unique page visitors. Track qualified signups separately if your product distinguishes them — a spike in low-quality signups may not be real progress even if the rate rises.
  • Guardrails to watch: check bounce rate and page load time after any change; a faster conversion rate that degrades lead quality or page performance may not be a net win. Set your own thresholds based on your baseline.

run.md lever map

  • hero clarity: rewrite the headline and primary CTA to better match the visitor's intent; diagnostics include CTA click rate, scroll depth, and bounce rate. What 'clear' means depends on your audience — test and observe.
  • signup friction: reduce steps, fields, or decisions between landing and completion; diagnostics include per-step dropoff in a funnel. Note: tracking this well may require custom events if your signup flow is a SPA or doesn't use native form submits.
  • social proof: add credible proof (numbers, named customers, before/after results) near the CTA; diagnostics include time-on-page, scroll depth to proof section, and signup rate. Specificity tends to outperform generic claims.
  • traffic-message match: create variants that mirror the language of your ad copy or referral source; diagnostics include conversion rate and CTA click rate by source/medium. Useful when you have meaningful traffic from multiple distinct sources.

gate.md

Requires change committed and deployed to a reachable URL, funnel baseline recorded before the change, analytics event names listed in work.md, and measurement window started. Warning if page load performance was not checked after deploy.