BuyWhere
← Back to documentation

BUY-3977-ux-audit-signup-cta-flow

BUY-3977 UX Audit: /developers to Signup CTA Flow

Date: 2026-04-24 Owner: Form Scope: /developers -> /docs / /quickstart -> /api-keys

Summary

The current developer conversion path leaks mostly through inconsistency, not lack of content. The site already has enough pages to convert, but the onboarding story changes too often:

  • /developers reads like the entry point
  • /docs also reads like the entry point
  • /quickstart is written like the canonical path
  • copy still mixes signup and api-keys
  • documentation navigation includes dead destinations
  • the post-key state behaves like account management before the user has activated

Friction Points

  1. Multiple "start here" stories
  • /developers, /docs, and /quickstart all compete as the first click for new developers.
  • CTA labels shift between Get API key, Get API Key, View quickstart, and older signup language.
  1. Dead-end docs navigation
  • The docs sidebar and docs feature cards point to routes such as /docs/search, /docs/products, /docs/compare, /docs/sdk, and /docs/mcp.
  • Those pages do not exist in the repo today.
  1. Copy drift in the activation flow
  • FirstCallBlock still references "the signup step" even though the live flow uses /api-keys.
  • Docs and quickstart materials still imply different API conventions, which weakens confidence before first use.
  1. Weak post-signup handoff
  • After a key is created, the page drops the user into a dashboard-style state.
  • That helps later, but the first-session job is activation: copy key, run request, continue setup.

CTA Hierarchy Issues

  1. /developers
  • Good visual hierarchy, but no explicit "preferred path" statement.
  • Resource cards compete with the core onboarding sequence instead of reinforcing it.
  1. /docs
  • The page mixes onboarding and reference behaviors.
  • New users do not get a strong signal that quickstart is the safer first move than full docs browsing.
  1. /api-keys
  • The form is clear.
  • The success state is not activation-oriented enough.

Mobile-Specific Concerns

  1. Docs navigation adds friction on first visit
  • The floating menu button and drawer are workable, but they create another decision layer before activation.
  1. Path clarity matters more above the fold
  • On mobile, the first visible CTA pair should explain the sequence without requiring interpretation.
  1. Dashboard content dominates too early
  • On /api-keys, metrics cards visually outrank the next action for a first-time user.

Highest-Impact Fixes

  1. Standardize one named onboarding path
  • Treat /quickstart as the canonical sequence.
  • Treat /api-keys as the provisioning step inside that sequence.
  1. Replace dead docs links with working destinations
  • Favor live paths that keep users moving: /quickstart, /integrate, /docs/QUICKSTART, /docs/API_DOCUMENTATION, /docs/API_EXAMPLES.
  1. Convert the success state into an activation checklist
  • After key creation, emphasize:
  • copy key
  • run first request
  • open quickstart
  • connect MCP

Recommended Follow-up

  • Align endpoint/auth examples across marketing pages, quickstart, and markdown docs in a dedicated content pass.
  • Instrument hero CTA clicks, key creation success, quickstart click-through after signup, and first successful request.