If a colleague recently told you Claude is worth trying, they were right.
Maybe you have been using ChatGPT, Gemini, or Copilot for a while now. Maybe you have been getting decent results. But increasingly, pastors and church leaders who made the switch to Claude are saying something keeps happening: their outputs feel sharper, their prompts feel more productive, and the tool actually seems to understand the nuance of ministry work.
Here is the thing: the interface looks basically the same as the AI tools you are already used to. It is a chat window. You type, it responds. But what makes Claude different is not how it looks. It is how you use it. And if you start with the right setup steps, you skip a lot of the frustration that slows most people down in the first few weeks.
Today, I want to give you the penny tour. Four concrete first steps to get you oriented and using Claude well from day one.
Let’s walk through each one.
Step 1: If you are coming from ChatGPT, transfer your context first.
This is the move most people skip, and it costs them weeks of friction.
ChatGPT has been learning about you. Your role, your writing style, your preferences, your communication patterns. All of that context is sitting inside that tool right now. And Claude has a dedicated feature to pull it right over.
Here is exactly how it works:
In Claude, go to Settings, then Capabilities, then find Import memory from other AI providers and click Start Import.
Claude gives you a specific prompt to copy:
Export all of my stored memories and any context you've learned about me from past conversations. Preserve my words verbatim where possible, especially for instructions and preferences.
## Categories (output in this order):
1. **Instructions**: Rules I've explicitly asked you to follow going forward — tone, format, style, "always do X", "never do Y", and corrections to your behavior. Only include rules from stored memories, not from conversations.
2. **Identity**: Name, age, location, education, family, relationships, languages, and personal interests.
3. **Career**: Current and past roles, companies, and general skill areas.
4. **Projects**: Projects I meaningfully built or committed to. Ideally ONE entry per project. Include what it does, current status, and any key decisions. Use the project name or a short descriptor as the first words of the entry.
5. **Preferences**: Opinions, tastes, and working-style preferences that apply broadly.
## Format:
Use section headers for each category. Within each category, list one entry per line, sorted by oldest date first. Format each line as:
[YYYY-MM-DD] - Entry content here.
If no date is known, use [unknown] instead.
## Output:
- Wrap the entire export in a single code block for easy copying.
- After the code block, state whether this is the complete set or if more remain.Take that prompt, paste it into ChatGPT, and ChatGPT will generate a structured export of everything it has stored about you: your instructions, your identity, your projects, your working preferences, all of it, organized and ready to move.
Copy that output. Come back to Claude. Paste it into the import box and click Add to Memory.
That is the whole process. No file exports. No technical setup. Copy, paste, paste.
Once it is imported, review what Claude stored and remove anything sensitive before moving forward. You are in control of what it keeps.
This memory feature is available on both free and paid plans, so there is no barrier to doing this on day one regardless of what tier you are on.
Do this before anything else. It means Claude is not starting cold. It already knows your context, your role, and how you work before you type your first real prompt.
Step 2: Set up your custom instructions in Settings.
Claude has a place in Settings called Profile. Think of this as the standing brief you give a new staff member on their first day.
This is where you tell Claude who you are and what you do, who you serve (your congregation, your staff, your community), how you like to communicate, what you never want it to do (no clichés, no filler phrases, no overly formal language), and any recurring context it should always have, like your church’s name, your denomination, or your current sermon series.
The more specific you are here, the less you have to explain yourself every single time you open a new conversation. Claude reads this before every response. It is invisible scaffolding that makes every output better without you having to think about it.
Step 3: Learn the F.A.S.T.E.R. prompt framework for AI before you write your first real prompt.
The quality of what Claude gives you is directly tied to the quality of what you give Claude. Most people type a vague one-liner and then feel like AI is not living up to the hype. That is almost always a prompting problem, not an AI problem.
Here is a simple framework that fixes it. It is called the F.A.S.T.E.R. Prompt Framework:
- F is for Form factor. Tell Claude exactly what you are trying to create. A sermon outline? A staff update email? A three-day devotional? A social media caption? Be specific about the format and structure you want.
- A is for Audience. Who is this for? New visitors? Your elder board? Parents of teenagers in your student ministry? Defining this changes the tone, vocabulary, and depth of the output dramatically.
- S is for Subject matter perspective. From what voice or angle do you want this written? As a senior pastor? Through the lens of a particular theological tradition? With a specific passage as the anchor?
- T is for Task details. What do you actually want Claude to do? List every task. Do not assume it will figure out your intent from a vague request.
- E is for Examples or evidence. This is the most underused piece. Paste in a sample of your own writing so Claude can match your voice. Give it a reference point for what a strong output looks like to you. This one step closes more of the quality gap than anything else.
- R is for Requirements and restrictions. Tell it what to avoid. No bullet points? Say so. Needs to stay under 300 words? Say so. Must reference a specific scripture? Say so.
You do not have to use every letter every single time. But the more of these you include, the sharper your results. Most church leaders who feel stuck are simply skipping E and R. Start there.
Step 4: Set up your first Project.
Projects are one of the features that genuinely separate Claude from the other tools. And they are worth understanding correctly, because they are not organizational folders.
A Project in Claude is a persistent workspace. When you create one, you can upload documents, guidelines, context files, and custom instructions that apply only inside that Project. Claude holds onto all of it across every conversation you have within that workspace.
For church leaders, here is how this plays out in practice:
A sermon series Project might hold your entire series arc document, your key scriptures, your theological guardrails for that series, and any illustrations you have already drafted. Every conversation inside that Project stays grounded in all of that material automatically.
A staff and leadership Project might hold your org chart, your staff handbook, your values document, and any coaching frameworks you use for one-on-ones. When you need to draft a difficult conversation or prepare for a performance review, all that context is already loaded.
A communications Project might hold your brand voice guide, past bulletin copy, and your upcoming calendar so that anything your communications team produces stays consistent without extra explanation every time.
One common question: should you have one big sermons Project or a separate Project per series? Best practice is a separate Project per series while you are in active production. It keeps the context tight and specific, and Claude performs better when it is not sorting through a massive, mixed document pile.
You do not need to build all of these today.
Pick the one area where you are doing the most work right now, create a Project, load in two or three relevant files, and run a few prompts inside it. That first experiment will show you more than any explanation can.
That is the penny tour. Four steps, and you are genuinely set up to use Claude well. We will go deeper on each of these areas in the weeks ahead, including more advanced prompting strategies, how to build out your Projects, and how to get Claude sounding like you instead of sounding like AI.
For now, just start. Because the absolute best way to get comfortable is to get in and use it.
