Skip to content
MISSIONBuilding to $50K/year · partnership threshold — every $20 subscription reserves 10 meals in the fund. Report published monthly.SEE THE PROGRESS →
SWITCH · FROM CLAUDE

Moving from Claude.ai to LADLE.

You already love the model — Claude Sonnet powers both. The switch is administrative: cancel Claude Pro at Anthropic, subscribe to LADLE, rebuild Projects with your existing prompts. Voice and reasoning carry over exactly.

EXPORT FLOWS VERIFIED 2026-08-05
WHAT TRANSFERS

Honestly: what comes across, what doesn’t.

WHAT
TRANSFERS?
NOTE
Model behavior
Yes
Same Claude Sonnet, same voice, same context window.
Chat history
Yes (readable copy)
Via Claude's export. Keep for reference; not imported to LADLE.
Custom Instructions (Claude Style)
Yes
Paste into a LADLE Project Voice Guide — same shape, per-Project scoping.
Projects
Partial · manual
Anthropic's Projects concept maps 1:1. Recreate each with the same knowledge files and instructions.
Uploaded files
Yes
Re-upload to LADLE Projects. Same limits.
Subscription
No
Cancel Claude Pro at anthropic.com. Both companies fine with the switch.
Anthropic API keys / API usage
N/A
LADLE uses Anthropic API on your behalf. If you have direct API workflows, keep those — LADLE doesn't replace them.
STEP 1 · EXPORT FROM CLAUDE

Get your data out of Claude.

  1. 01

    Settings → Privacy → Export data

    In Claude.ai, click Settings → Privacy → Export. You'll receive an email within an hour with your archive: conversations.json, projects, uploaded files. Keep the .zip.

  2. 02

    Copy your Claude Style (Custom Instructions)

    Settings → Style. Copy the style description. This is your Voice Guide seed for LADLE.

  3. 03

    List your Claude Projects

    Note the name, description, and attached knowledge files for each Project you actually use (probably 2-5). You'll rebuild these in LADLE.

  4. 04

    Cancel Claude Pro (or hold until you're settled)

    You can either cancel Claude at anthropic.com immediately and run only LADLE, or run both for a week to make sure the switch lands. LADLE's 7-day refund covers you either way; $20 in parallel is cheaper than a bad call.

STEP 2 · REBUILD IN LADLE

Set LADLE up the way Claude was working for you.

  1. 01

    Sign up for LADLE and create your default Project

    Same setup as Claude Projects: sidebar → New Project → name it → Voice Guide + attached files. Interface differs slightly; the concept is identical.

  2. 02

    Paste your Claude Style into the Voice Guide

    Add 2-3 example paragraphs of your writing (helps LADLE hit register precisely). This takes ~20 minutes and locks in voice quality forever.

  3. 03

    Recreate your Claude Projects

    For each Claude Project: new LADLE Project → same name → attach the same knowledge files → paste the instructions. Testing with one chat immediately verifies the migration landed.

  4. 04

    Move active chats forward

    Pick your 2-3 most-active recurring Claude chats. Start fresh in LADLE by pasting the last 2-3 exchanges from each. Preserves working context without importing years of history.

FEATURE MAP

Their feature → our equivalent (or an honest “we don’t”).

IN CLAUDE
IN LADLE
Claude Style (Custom Instructions)
Voice Guide (per-Project)
Projects
Projects (same concept, same shape)
Artifacts
Not yet — LADLE renders code and text inline; standalone Artifacts view is planned
Claude Code CLI
Not available — Claude Code is a separate developer product
Anthropic Console (API playground)
Not available — LADLE is chat-only; use Anthropic Console for API dev
Team / Enterprise plans
For Business — same $20/seat, no markup
Model options (Sonnet / Haiku / Opus)
Sonnet only (opinionated single-model)
MIGRATE HONESTLY

Nothing hidden, no lock-in.

FIRST-WEEK PLAN

Seven days to feel at home.

  1. DAY 1

    Sign up, set up default Project with Voice Guide

    The muscle memory from Claude carries over. This takes 15 minutes.

  2. DAY 2

    Recreate your top Claude Project

    The one you used most yesterday. Attach files, paste instructions, test one chat.

  3. DAY 3

    Do actual work in LADLE for the day

    Same model, so no surprises on quality. Notice the UI differences (they're small).

  4. DAY 4-5

    Recreate remaining Projects

    You'll have 2-5 depending on how you work. Each Project takes ~15 minutes.

  5. DAY 6

    Cancel Claude Pro if the switch is landing

    Anthropic Settings → Subscription → Cancel. You retain access to Claude through your paid period; no rush.

  6. DAY 7

    First meals fund at month-end

    Your subscription starts funding meals immediately; the first monthly statement arrives the last day of this calendar month.

YOU GAIN
  • 10 meals/mo reserved in the LADLE meal fund per subscription (pegged at the partner's $0.80/meal; ships as real partner donations once the $50k/year threshold clears).
  • Published monthly fund reports and open metrics.
  • Same Claude Sonnet, so no learning curve on the model.
  • Straightforward, honest 7-day refund policy.
  • One less line item on your card — same price, one thing feeds two purposes.
YOU GIVE UP
  • No Artifacts standalone view (planned).
  • No Claude Code CLI (that's a separate Anthropic developer product).
  • No model choice (Sonnet only — Opus and Haiku aren't available here).
  • Smaller company than Anthropic — feature roadmap is smaller too.
SWITCH FAQ

Migration questions.

Because the meal donation is real, and the product is otherwise identical. If the meals matter to you, LADLE is the answer. If they don't, Claude Pro is a fine subscription — this whole company only makes sense for people whose AI spend is going to happen anyway.

Try LADLE for a week alongside Claude. Then decide.

7-day full refund if you don't switch. Meals fund from your first month either way.

Start with LADLEWatch it work
$20/MO · CANCEL ANYTIME · $0.80/MEAL · RECEIPTS MONTHLY
Read the ledger →
0meals fundedROLLING TOTAL · UPDATED HOURLY
SEE THE RECEIPTS →