Claude Project: Build a Reusable Coaching Assistant from Your Own Frameworks

What This Builds

Right now, every proposal, recap template, and development-plan outline you write starts closer to a blank page than it should, because a general chatbot conversation has no memory of your own materials from one session to the next. A Claude Project fixes that. You load it once with your own de-identified frameworks, proposal structure, and pricing tiers, and every draft you pull from it afterward already sounds like you instead of like a generic coaching template.

Prerequisites

• A Pro subscription ($20/month), which is required to create Projects.
• Thirty to forty-five minutes to assemble your own frameworks, proposal template, and pricing tiers into a document, with every client name, employer name, and identifying detail already removed.
• General comfort typing a request into a chatbot and refining the output through follow-up prompts.

The Concept

Think of a Claude Project as a filing cabinet that sits behind every conversation you have inside it. A normal chat forgets everything the moment it ends. A Project keeps whatever you upload to it (your proposal template, your intake questions, your standard development-plan structure) in view for every new conversation you start there, so you stop re-explaining your own business to the AI each time you want a draft.

Build It Step by Step

Part 1: Assemble your source material

Before touching Claude, gather the documents you rewrite most often and strip them of anything client-specific. A good starting set:

• Your standard proposal or statement-of-work template, with the pricing tiers you currently offer
• A blank development-plan outline (goals, milestones, check-in cadence) with no real client's goals in it
• A short document describing your coaching style, the frameworks you draw on (GROW, stakeholder-centered coaching, whatever you actually use), and how you like recaps worded
• Two or three past documents you're proud of, edited so no client, employer, or identifying detail remains

Save these as separate files. You'll upload them directly rather than pasting them into a prompt.

Part 2: Create the Project

1. Log in to claude.ai.
2. Click Projects in the sidebar, then New Project.
3. Name it something you'll recognize later, such as "Coaching Practice Assistant."
4. Open Project Instructions and paste a version of this, adjusted to your own practice:

You are a drafting assistant for my independent executive coaching practice.

Your job: draft proposals, session recaps, development plans, and related
business documents using the templates and frameworks I've uploaded to this
project, in my established structure and tone.

Always:
- Match the structure of the uploaded proposal template unless I ask for
  something different
- Use plain, professional language, not consulting jargon
- Leave placeholders in brackets for anything client-specific I haven't
  given you (name, company, dates, pricing) rather than inventing detail
- Ask a clarifying question if my request is missing something the
  template needs

Never:
- Invent client outcomes, quotes, or assessment results
- Retain or reference any specific client's real name or employer in this
  project. Every example and template here is de-identified on purpose,
  and any new client detail I paste into a chat should be described in
  general terms only (role, industry, theme), not by name.

1. Click Upload files and add every document from Part 1.
2. Save the Project.

Part 3: Draft your first document and refine the instructions

Start a new conversation inside the Project and try a request close to real use:

"Draft a six-month coaching proposal for a director-level client. Biweekly 60-minute sessions, focus areas are delegation and executive presence, includes one 360 debrief at the midpoint."

Read the draft against your actual style. If it reaches for language you'd never use, or misses a section your real proposals always include, go back into Project Instructions and add a line about it. This is the main tuning step: the first draft tells you what's missing from your uploaded materials, not just what's wrong with the AI.

Real Example: Turning Session Themes into a Development Plan Draft

Setup: A Project loaded with a blank 90-day development-plan template, a one-page coaching-style document, and two de-identified past plans as style references.

Input: "Outline a 90-day development plan for a new director-level manager working on strategic thinking and stakeholder influence, based on these three themes: reactive decision-making, thin cross-functional relationships, and a tendency to over-explain instead of delegate."

Output: A plan in the coach's own established format (the same section headers, the same milestone cadence) instead of a generic outline, with brackets left in place for the client's name and the specific check-in dates.

Time saved: Turning three themes into a client-ready plan starts closer to a finished first draft than a blank document does, because the structure and tone no longer need to be rebuilt each time.

What to Do When It Breaks

• Claude starts inventing outcomes or quotes that were never in your uploaded material → Add an explicit line to Project Instructions telling it to use brackets for anything you haven't supplied, and reject drafts that fill in specifics on their own.
• The tone drifts away from your voice over a long conversation → Start a fresh conversation inside the same Project rather than continuing a long thread. The uploaded files are still there; only the conversation history resets.
• A draft references a template section you removed months ago → Re-upload your current templates. Older files stay in the Project until you remove them, and Claude may pull from an outdated version if two similar documents are both present.
• You're tempted to paste in a real client's notes to get a more specific draft → Don't. Describe the situation in general terms (role, industry, theme) instead, the same way you would in any other AI drafting tool.

Variations

• Simpler version: Keep using a plain Claude chat and re-paste your template at the start of each session. No setup, but no persistent memory between conversations.
• Extended version: Once the Project is stable, add a second one scoped to marketing content (LinkedIn post structure, newsletter voice) so business-development drafts don't share a knowledge base with client-facing documents.

What to Do Next

• This week: Assemble your de-identified templates and set up the Project.
• This month: Route your next three real proposals or development plans through it and refine the instructions based on what needs correcting each time.
• Advanced: Once the wording is stable, pair this with a chained prompt sequence for multi-step work like 360 debrief synthesis, so extraction, ranking, and drafting happen as separate checkable steps inside the same Project.

A Note on Confidentiality

This Project is a shared knowledge base by design, which is exactly why nothing client-specific belongs inside it. The coaching agreement you sign with each client, and the ICF Code of Ethics you practice under, treat session content and identifying detail as confidential to that engagement. A document sitting in your Claude Project knowledge base is available to every conversation you start there and to anyone else who might get access to your account, so it needs to already be safe to show a stranger before it goes in. Keep real client work in the conversations you have about that client, described in general terms, never in the Project's permanent files.

Advanced guide for executive coaches. Building this requires a paid Claude subscription with Projects access.