Create Your First Month of Content with Claude

Section 1

Start where your config file stopped

Everything in Guide 1 was foundation. Your project, your instructions, your agent config file — all of it exists so that Claude starts every conversation already knowing your market, your buyers, and how you sound. The content plan is what you build on that foundation.

Open your config file and go to the Content Goals section. Decide what you want Claude producing for you over the next three months, and write those choices in. Then go back up to your Ideal Clients section and check that every content type you picked serves someone you named there. A content goal with no reader behind it produces content nobody reads.

Tick the types you want, then write them into Content Goals

Section 2

Find your five to eight content pillars

A pillar is a subject you return to often enough that people start associating it with you. Claude builds yours from three things it already has: your market, your ideal clients, and your services.

Five is the floor. With fewer than five you are repeating yourself by week six. Eight is the ceiling. With more than eight, no single subject gets enough repetition to stick.

1. 1

   Ask Claude for your pillars using the prompt from Guide 1, or the master prompt in the next section.

2. 2

   For each pillar it returns, make it tell you which part of your config file the pillar came from. If it cannot point at one, the pillar was invented and it goes.

3. 3

   Cut anything you would not want to be known for in three years. Pillars are a long commitment.

4. 4

   Write the survivors down. Every piece you plan from here gets tagged with one of them.

Section 3

Ask for twelve weeks, build out the first four

Ask Claude for twelve weeks in one go. A twelve-week horizon is long enough that the plan has to think about sequence, seasons, and repetition, and short enough that you can still picture finishing it. Then take the first four weeks and expand them into real briefs. Those four weeks are your month.

Ask for the buyer list and the seller list as their own deliverable, held apart from the calendar. They are your standing well of topics. When a week goes sideways and you need something publishable by Friday, you pull from the well instead of starting over.

The prompt below runs the whole thing in six steps and pauses between each one so you can correct course. Paste it into your Claude Project with your config file already uploaded.

The master content-plan prompt

Use my agent configuration file as the source of truth for everything below.

My website URLs are:
[paste your full URL list here, one per line]

I publish [3] pieces per week.

Work through this in six steps and pause after each one so I can correct you before you continue.

STEP 1 — PILLARS
Based on my market, my ideal clients, and my services, identify 5 to 8 content pillars I should focus on for my real estate website, blog, and social media. For each pillar, tell me which part of my config file it comes from and why it earns attention in my market.

STEP 2 — TWELVE-WEEK PLAN
Create a starter content plan covering 12 weeks. For every piece, give me: the type (blog post, community guide, FAQ, social caption, email, video outline), a working title, which pillar it belongs to, which specific ideal client it serves, the single call to action it should end on, which section of my config file it draws from, and which of my URLs it should link to.

STEP 3 — BUYER AND SELLER LISTS
Create a buyer topics list and a seller topics list as two separate deliverables. These are standing topic wells I can pull from, held apart from the calendar itself.

STEP 4 — ROTATION GRID
Build me a spreadsheet with a grid: five topics across five categories covering five different FAQs, rotated so that no combination is covered twice across the twelve weeks. This is what stops week nine from restating week two.

STEP 5 — LOCAL CONTENT MAP
Based on my target market, suggest community guide topics. Include living-in guides, moving-to guides, and what-to-do-when-you-live-here guides. Cover recurring local events and the things each community is known for. Do not invent an event, a statistic, or a local detail. If you are unsure, ask me and I will confirm it.

STEP 6 — THE FIRST FOUR WEEKS
Take weeks one through four and expand them. For each piece give me the working title, a one-paragraph angle, the three questions the piece must answer, the CTA, and the internal links it should carry.

Rules for all six steps:
- Ground everything in my config file. Do not invent market statistics, school rankings, neighbourhood claims, or local events.
- Follow Fair Housing principles. Flag any phrase that could be read as steering or as tied to a protected class before you include it.
- Write in my voice as described in my config file.
- Every piece needs one call to action, and only one.

Section 4

The rotation grid that stops you repeating yourself

This is the mechanic that separates a content plan from a list of ideas, and it is the one almost nobody sets up.

Ask Claude for a spreadsheet built as a grid: five topics across five categories, covering five different FAQs, rotated so the same combination never comes up twice. Twelve weeks of publishing is long enough that memory fails you. By week nine you will have a strong opinion about first-time buyer financing, having forgotten you wrote exactly that in week two.

The grid does the remembering. Keep it open beside the calendar, and cross cells off as they publish.

Section 5

Map the content only you can write

Every agent in your market can publish an article about mortgage rates. Almost none of them will write the piece about what happens in your town in October, because that takes local knowledge and the willingness to sit down and get it out of your head.

Ask Claude for community guide topics based on your target market. Three shapes work reliably: living in a place, moving to a place, and what to do once you live there. Push it toward the recurring events, the things each community is known for, and the local questions people ask before they ever call an agent.

One rule holds here above all others. Claude does not know your farmers market moved to Thursdays. Tell it plainly that it may not invent an event, a date, a statistic, or a local claim, and that it should ask you when it is unsure. Then verify every local detail yourself before it publishes.

Section 6

Hand Claude your URLs

A content plan that ignores your existing site produces orphan pages. Every Lofty site ships with a standard set of pages, and Claude has no way of knowing which of them you have, or what you called them, unless you say so.

Make a second markdown file that is nothing but your URLs and what each one is for. Upload it to your project beside your config file. Once it is there, you can ask for something like a short blurb for the top of your reviews page and get back something shaped for your business, because the project already knows who you are.

Teams that go deep on this end up with a real reference document. On the builds we run, this file has grown into a full interlinking guide — hundreds of lines telling Claude how the pages relate, so that when it writes, the links it chooses make sense to a reader.

Section 7

Month two, in one prompt

Month one is the expensive one. After that, a trained project turns a recurring piece into a single prompt.

Take a monthly market update as the example. Paste in last month's finished post exactly as it published, paste in this month's statistics, and ask for the new version. Because the project already holds your voice and your audience, one prompt gives you the article plus every field your website asks for: the meta title, the description, one focused keyword phrase, and the URL slug.

Keep the slug wording different from the headline so the two are working on separate search terms. And ask it to end the article on an H2, so your listings block has somewhere clean to sit.

The month-two prompt

Here is last month's finished post, exactly as it published:

[paste the full HTML of last month's post]

Here are this month's numbers:

[paste your statistics package]

Write this month's version. Keep the structure and the voice of the post above, and update every figure from the numbers I gave you. Do not carry forward a single stale statistic.

Then give me these fields separately, each one labelled:
- Meta title
- Blog description
- One focused keyword phrase, as a phrase rather than a list
- URL slug, worded differently from the headline so the two are working on separate search terms

End the article on an H2 so my listings block sits underneath it.

Section 8

Your prompt library

These are the working prompts from the class that go past setup. Copy any of them straight into your Claude Project.

Section 9

Read it before anyone else does

A plan this organized makes it easy to produce more than you can read. Resist that. The simplest standard there is: if you would not read it yourself, do not send it to a client.

The failure everyone is drifting toward is your AI emailing me, my AI emailing you back, and no conscious decision getting made anywhere in between. Your name is on every piece. Read it, check the local facts, check the Fair Housing language, and make sure the person on the other end would recognise it as yours.

• Every statistic and local detail is one you can verify
• No steering language, no reference to a protected class
• It sounds like you to someone who has met you
• One clear call to action, and the link behind it works
• Internal links point at pages that exist

Section 10

What you walk away with

At the end of this process, you should have:

• Five to eight content pillars drawn from your config file
• A twelve-week content plan, with the first four weeks written out piece by piece
• A buyer topics list and a seller topics list, held separately
• A rotation grid that keeps you from covering the same ground twice
• A local content map for the communities you serve
• A URL file so every piece links back into your site
• A one-prompt routine for month two
• A master template holding every formatting quirk you have already solved

Section 11

Ready to go further?