1.05 Setting Up Claude Max
If you're going through Forge, you'll be running Claude on a Max plan paid for with a company card rather than on Liatrio's Enterprise API access. This page walks you through getting that set up on day one. Budget about 15 minutes.
Complete this page first. Section 1.1 Environment Setup assumes you already have a Claude subscription to log in with.
Before You Start
You'll need a personal email address (not your Liatrio one) and a phone number in a country Anthropic supports for verification. That's an Anthropic requirement, not a Liatrio hoop.
Step 1: Request a Ramp Card
Message @smith in Slack and ask for a Ramp card for a Claude Max subscription.
Do this first. Virtual cards often come back right away, but request yours before you reach checkout rather than mid-flow. You can work through steps 2 and 3 while you wait.
The card is issued for 45 days, which leaves buffer past the length of Forge.
Step 2: Create or Log Into Your claude.ai Account
Go to claude.ai and sign in, or create an account if you don't have one. Use your personal email address. You'll verify with a phone number as part of signup.
If you already have a Free or Pro account from before you joined, just log into that one — you'll upgrade it in the next step.
Claude may appear to let you upgrade a free account registered to your Liatrio email. Don't. Forge Max subscriptions go on a personal account — see A Note on the Personal Account below for why.
Step 3: Upgrade to Max
New account: the upgrade is offered right in the signup flow.
Existing account: go to Settings → Billing → Upgrade to Max.
Pick the Max 20x tier ($200/mo). That's the tier we standardize on for Forge, so go straight to it.
Step 4: Pay With the Ramp Card
Enter the card details, and for the billing address use the address registered to that Ramp card — not your home address, unless they happen to be the same.
If the address doesn't match, Anthropic will make you cancel and wait out the old subscription before the new one takes effect, which costs you a day or more.
Confirm the subscription. It auto-renews by default, which is what we want for the duration of Forge.
Forward the receipt from your personal email to your work email and Ramp will pick it up. You don't need to file a separate expense report for this.
Step 5: Confirm You're on the Personal Account
Before moving on, double-check that the account you're now working in is the personal one with Max active — not a leftover Liatrio login. In claude.ai, open Settings and confirm the email shown is your personal address and the plan reads Max.
If you see your Liatrio email, log out and log back in with the personal account.
Step 6: Check That Training on Your Data Is Off
Go to Settings → Privacy and confirm the option allowing your conversations to be used to improve Claude is switched off.
It's off by default, so this is a verification step rather than a change — but check it rather than assume it.
Step 7: Point Claude Code at Your New Login
Log Claude Code in with the same claude.ai credentials you just used. Section 1.1 Environment Setup covers the install and the /login flow.
ANTHROPIC_API_KEY overrides your Max loginIf ANTHROPIC_API_KEY is set in your shell environment, Claude Code will quietly ignore your Max login and keep billing the old way. Check for it and unset it first:
echo $ANTHROPIC_API_KEY # should print nothing
unset ANTHROPIC_API_KEY # if it printed something
Also check your shell profile (~/.zshrc, ~/.bashrc, or similar) so it doesn't come back in your next session.
settings.jsonClaude Code also reads credentials from its settings files, and those win over your Max login the same way the shell variable does. The Vercel CLI is a known case: it can write an Anthropic token into ~/.claude/settings.json, so Claude Code keeps billing the old way even though Max shows as active on claude.ai.
Check for it:
grep -nE 'ANTHROPIC_|apiKeyHelper' ~/.claude/settings.json .claude/settings*.json 2>/dev/null # should print nothing
If it prints anything, remove those entries (ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, or ANTHROPIC_BASE_URL in the env block, or a top-level apiKeyHelper), save, and restart Claude Code. Then run /status in Claude Code and confirm it shows your personal claude.ai account, not an API key.
When Forge Wraps
Cancel the subscription in Settings → Billing as soon as Forge is done. Don't wait for the Ramp card to lapse — the 45 days are buffer, not a deadline.
Set yourself a reminder for around day 40 as a backstop. IT tracks the active subscriptions through Ramp and will follow up, but the fastest path is you cancelling it the week Forge ends.
A Note on the Personal Account
Because this sits on a personal email, it isn't tied to your Liatrio identity — it's outside Google SSO, and it won't be caught by the usual offboarding cleanup. That's why cancelling at the end matters.
Questions
Ask in #liatrio-forge.
Next Steps
With a Max subscription active, continue to Section 1.1 Environment Setup to install Claude Code and sign in.