Claude Code Claude CodeGetting started

Claude Code: install and your first agent run

Claude Code is an agentic tool that runs in your terminal, your editor, a desktop app, or the web, and does multi-step work against your real files and tools. To start: install it with npm (npm install -g @anthropic-ai/claude-code), run claude, sign in with your Claude subscription or an API key, and give it a real task. Make your first run something you actually do, like turning a company URL into an account brief, not a toy.

Overview

I avoided Claude Code for months, and the reason is embarrassing: the word 'Code' is in the name, and I run demand generation, not engineering. I assumed it was a tool for people who are not me. That assumption cost me a quarter of doing by hand what it now does while I get coffee.

The reframe that unstuck me: Claude Code is not a coding tool, it is a do-things-on-my-machine tool that happens to be very good at code. Anything that can be described as files and commands is fair game, and a shocking amount of GTM work is exactly that.

So this is the fifteen-minute path from nothing to a first useful run, written for the operator I was, the one who almost skipped it. Do not make my mistake.

What Claude Code actually is

What Claude Code actually is

Claude Code is Claude running as an agent. You give it a goal, and it reads what it needs, decides the next action, takes it with a tool (read a file, run a command, call an API), checks the result, and keeps going until the job is done. It is the agentic loop from the concepts, turned into a tool you run.

The shift from the chat box is the whole thing. In the app you ask for text and paste it somewhere. In Claude Code you hand off a task and review the outcome. One is an assistant that talks; the other is one that does.

The agentic loop
01Observeread the current state and the goal
02Decidepick the single next action
03Acttake it with a tool, read or write
04Read resultthen loop back to 01
It runs this loop over and over until the goal is met or a stop fires: a step limit, a required approval, or an error.
💡

TipIf you already use the chat app, the mental jump is small: same Claude, but now it can act on your files and tools instead of just describing what you should do.

Install and sign in

Install and sign in

Getting running is quick, and none of it requires you to be technical.

  • Install with npm: run npm install -g @anthropic-ai/claude-code
  • Start it: run claude in whatever folder you want it to work in
  • Sign in: your Claude Pro or Max subscription, or an Anthropic API key
  • It works in the directory you launch it from, so start in a folder that holds the files for your task
💡

TipOn a fresh machine, the only prerequisite is Node (which gives you npm). If npm is unfamiliar, that is the one thing to install first; everything after is one command.

Make your first run a real task

Make your first run a real task

Skip hello-world. Give it something from your actual week. A strong first run for a GTM operator: drop a company URL in and ask for a first-call account brief, or hand it a CSV and ask it to enrich and score the rows. You will learn more from one real task than from ten tutorials, because you will immediately see whether the output is worth your time.

Watch how it works as it goes. It narrates its plan, takes steps, and shows you the result, and that transparency is how you build the trust to hand it bigger jobs later. The first time it does in ninety seconds a thing that used to cost you an hour, the tool sells itself.

💡

TipPick a first task you already know the right answer to. Then you can judge the output instantly, and you learn to trust it (or not) fast.

It asks before it acts

It asks before it acts

By default Claude Code asks permission before it does anything that changes your files or runs a command, so a first run cannot quietly wreck something. You watch, you approve, you learn its habits. As you get comfortable, you widen what it can do without prompting, but that is a choice you make on purpose, not a default you inherit.

This is the same guardrail principle from the agent concepts, built into the tool: start cautious, loosen deliberately. It is much easier to grant more freedom to a tool you trust than to recover from one you trusted too soon.

Why a non-engineer should bother

Why a non-engineer should bother

Here is the reframe again, because it is the whole point for operators and I want it to stick: Claude Code is a do-things-on-my-machine tool. I am not a software engineer, I run demand gen, and it is one of the most-used tools in my stack. I use it to build and maintain the scripts and automations that move my GTM data around, and I could not tell you the last time I wrote one of them by hand.

Anything that can be expressed as files and commands is in scope, and once you look, an enormous amount of GTM work is exactly that: pulling a list, cleaning it, scoring it, drafting from it, updating a system with the result. You do not need to code. You need to describe the job and read the result.

💡

TipWhen you catch yourself doing the same manual data chore for the third time, that is a Claude Code task. Describe it once, and stop doing it by hand.

Where first-timers go wrong

Where first-timers go wrong

The first trap is using it like the chat app, one question at a time, and never handing it a whole task. That works, but it wastes what makes Claude Code different, which is delegation. Give it the end goal, not a stream of tiny asks.

The second is starting too broad. 'Rebuild my entire lead-scoring system' on run one is how you get overwhelmed and quit. Start with one scoped task, get it working, and grow from there. The confidence to hand off big jobs comes from watching it nail small ones.

💡

TipScope your first three runs small and self-contained. Momentum comes from three quick wins, not one ambitious project that stalls.

Why this is the tool under everything

Why this is the tool under everything

Claude Code is the engine beneath the automations on this site: the account briefs, the enrich-and-route flows, the weekly ad analysis. Learning it is learning the thing that runs all of them, which is why it is the first Claude Code piece to read and the one that pays back fastest.

Start with one task you repeat, get it working once, and you have the seed of a system. The rest of this pillar, context, plan mode, skills, hooks, is how you grow that seed into something safe, repeatable, and worth trusting.

So what is the one manual chore you did this week that is really just files and commands? Start there.

💡

TipYour best first project is the boring recurring task you resent most. Automate the thing you hate, and the habit forms itself.

How to set it up

How to set it up

Install it and sign in

Claude Code installs with one npm command and then runs as `claude` in any folder. Install it, launch it, and sign in with your Claude account the first time it asks.

zsh
$# install once, globally
$npm install -g @anthropic-ai/claude-code
$# launch it inside any folder
$claude
Welcome to Claude Code. Signed in as vikash@getwickedgrowth.com
$
💡

TipOn Max you can run long sessions without watching the meter. If you are only trying it out, Pro is fine to start.

Point it at a folder with real GTM files

Claude Code works against the files in the folder you launch it from, so start it somewhere that has something real: a CSV of target accounts, last quarter's closed-won notes, your positioning doc. Do not make a toy folder to be safe, the whole point is that it touches your actual work.

Give it a real first task, not a hello-world

Type the job in plain English. The first run that convinces you is one you would have done by hand for an hour:

claude
$For each row in accounts.csv, visit the company's website, write a one-line reason we are relevant to them, and save it to a new column called angle.
Read 42 rows. Fetching sites, drafting angles, writing accounts_enriched.csv ...
$

Approve as it goes

It proposes each change and waits for you before it writes anything or runs a command. Read the diff, approve the ones you want, and stop it if it heads the wrong way. You stay the editor, it does the typing.

💡

TipFor the first week, keep it asking before every action. Widen its permissions only once you trust the pattern of work you are handing it.

FAQ

Frequently asked questions

What is Claude Code?

An agentic tool that runs Claude against your real files and systems: it plans, takes actions with tools, and checks its work, across the terminal, your editor, a desktop app, or the web. It does the task rather than just describing it.

How do I install Claude Code?

Install it with npm (npm install -g @anthropic-ai/claude-code), then run claude in the folder you want it to work in and sign in with your Claude subscription or an API key. Setup takes about 15 minutes.

Do I need to be a developer to use Claude Code?

No. It is a do-things-on-my-machine tool that happens to be great at code. Plenty of GTM work, briefs, enrichment, list cleanup, analysis, is just files and commands, and needs no traditional programming.

Is Claude Code safe to run on my machine?

By default it asks permission before actions that change files or run commands, so a first run cannot surprise you. You widen its permissions deliberately as you build trust; start cautious.

What should my first Claude Code task be?

A real one you already know the answer to, so you can judge the output fast: turn a company URL into an account brief, or enrich and score a CSV of leads. A real task teaches more than a tutorial.

What do I need installed first?

Node, which gives you npm to install Claude Code. If npm is unfamiliar, install Node first; after that it is a single install command and you are running.

How is Claude Code different from the Claude chat app?

The app answers; Claude Code acts. In the app you ask for text and move it yourself. In Claude Code you hand off a whole task and it reads files, runs commands, and checks its own work until it is done.

Why should a GTM operator learn Claude Code?

It is the engine under real GTM automations, account briefs, enrichment and routing, weekly analysis. Learn it once and you can build the systems that do your repetitive work, starting with a single task you repeat.

Sources

Sources & further reading

Claude ships fast. This page was last reviewed Aug 22, 2026; verify time-sensitive details against the official docs above before relying on them.

Get the AI-for-GTM playbook in your inbox

New Claude guides, use cases, and prompts every couple of weeks.

Subscribe →