LeveredDocs

Quick Start

One prompt in your coding agent. It finds where your product loses conversions, builds the versions in your app, and launches them on Levered.

Your coding agent does the work and you approve each step. It works in Claude Code, Cursor, or any agent that can fetch a URL.

1. Paste the prompt

Prompt for your coding agent
Take a first look at my product with Levered: https://levered.dev/start.md

No account and no install for this step: the agent only reads your code.

Already know what you want to improve? Ask for it directly instead, for example "Using Levered, get more sign-ups on my pricing page".

2. Pick a goal and see the ideas

The agent asks what you want more of (sign-ups, downloads, purchases), with its recommendation first. Then it shows where visitors drop off before that goal and what it would try instead, how many versions that makes, and roughly how long the model needs to learn which one works best at your traffic.

From there you choose: build the versions, sharpen the ideas first with your analytics or some quick research on your market, or pick which ideas to build.

3. Click through the versions

The agent builds every version in your app on a new branch, with your main branch left untouched, and opens the page with a small Levered switcher so you can try each one. Ask for changes until you're happy.

Along the way it installs the Levered plugin, so later sessions start with it.

Prefer to install the plugin yourself? (Claude Code only)

Type these two commands in Claude Code, then paste the prompt above:

Claude Code
/plugin marketplace add levered-hq/claude-plugin
/plugin install levered@levered

4. Go live

When you say so, the agent connects it to Levered:

  • signs you in, or opens a free sign-up, in your browser;
  • turns on the Managed Warehouse, so there's nothing to connect;
  • creates the metric for your goal and the optimization with your versions;
  • writes the API key straight into your gitignored env file, so it never shows up in the chat;
  • sends a test visit and a test conversion to confirm tracking works;
  • asks once before going live.

Your part: merge the branch, add the environment variables it names to your hosting, and deploy. Visitors see the versions once it's deployed, and part of your traffic keeps today's page so you can measure the gain.

5. See how it's doing

Ask your agent "how is my optimization doing?" at any time, or open it in the dashboard.

Next steps

Quick Start