Claude for Agents · The Claude Ladder

Rung 2 · Projects

I typed one sentence about a $9,000 repair request, and it already knew the listing, the seller and the six months behind them. A project is a folder that remembers.

  • Rung 2 of 6
  • 5 minutes
  • The map, not a setup guide
  • Setup: about 30 seconds
  • Part of the series
The walkthrough

Nine thousand dollars in repairs, and one sentence typed.

Buyer’s inspection came back on one of my listings, and they wanted nine thousand dollars in repairs. I had to get back to my seller with something useful — not forward her a repair list that says “let me know what you think.”

Watch what this looks like on rung one

I open a blank chat and I start typing. I’m a real estate agent in Arizona. This is a resale. Here’s what the house sold for. Here’s what we already conceded to get the deal together. Here’s what my seller is like — she does not like being handled, she wants the actual numbers.

All of that, and I haven’t even asked my question yet.

That’s the ceiling. Every conversation starts from nothing, and you’re the one hauling all the context into it.

What I actually typed

I opened the project I’d been using for this listing since before I even got it, and I typed one sentence: the inspection came back, buyer’s asking for nine thousand, here’s the list.

That’s all I typed — because of what was already in there. The listing appointment prep. The recording of the appointment itself. My analysis afterward, when I was deciding how to handle the pricing conversation. The comps. The disclosure packet. Every back-and-forth from the offer. Months of a working relationship, sitting in one folder.

So when I dropped in the full inspection report and the repair request, Claude wasn’t starting over. It was adding one more thing to a file it already knew. I had something I could send my seller in under a minute — and it sounded like me, talking to her.

A project is a folder that remembers

You work inside the folder instead of starting fresh every single time. Everything you put in it — every file, every conversation — stays there and makes the next one better.

Two things live in a project

WhatWhat it means
InstructionsPlain writing. Not code, not a prompt. You’re telling Claude what you’re working on and why it matters.
FilesWhatever Claude should be able to look at — disclosures, comps, the contract, transcripts. This is the context.

It takes about thirty seconds

You name it. That’s it. You do not need perfect instructions to start — you can change them any time, and mine get rewritten constantly.

And honestly? What made that inspection response good wasn’t my instructions. It was the six months of stuff that had piled up in that folder. Good instructions help, but the context does the heavy lifting, and you only get context by using the thing. Start it today.

One project per ongoing thing

This is where I watch agents make a mess. One project per ongoing thing — a client, a listing, a part of your business you come back to over and over.

What people do instead is create a new project every time they have a question. Then they have forty projects, nothing has accumulated in any of them, and it’s actually worse than where they started.

A project is a folder for a relationship. Not for a question.

You’re not supposed to be the memory

Rung one: ask a question, copy the answer, close the tab. Tomorrow, start over. You’re carrying the context. You’re the memory. That’s chatbot thinking — and being the memory is the software’s job, not yours.

That’s rung two. You’ve handed over one thing: remembering.

Next: rung three

But notice something about that story. Claude still needed me to bring it the inspection report. I had to go find the email, download the PDF and put it in there.

Rung 3 · Connectors

Rung three is where it stops needing you to go fetch things. It gets its own information.

Questions agents ask

Before you make your first one.

Do I need good instructions before I start?

No. Making a project takes about thirty seconds — you name it, and that’s it. You can change the instructions any time, and Kristi’s get rewritten constantly. Good instructions help, but the context is what does the heavy lifting, and you only get context by using the project.

A project for every question, or not?

Not for questions. One project per ongoing thing — a client, a listing, a part of your business you come back to over and over. What goes wrong is forty projects made one question at a time, where nothing ever accumulated. That is worse than where you started.

What should I put in the files?

Whatever Claude should be able to look at: disclosures, comps, the contract, transcripts. The inspection response that worked was carried by six months of exactly that — the listing appointment prep, the recording, the analysis afterward, every back-and-forth from the offer.

Prefer Google over your inbox?

Tell Google you want Kristi’s builds first

Add kristijencks.com as a preferred source and Google highlights new Claude for Agents builds and Take It and Run articles in your Top Stories and AI results.

Or have it built for you

Rather climb two rungs in an hour with someone sitting next to you?

A working session with Kristi or Merrill ends with a system running, not a list of notes.

Book an AI Session