Claude Context Document Builder

What This Does

A context document makes Claude dramatically more useful

Without a context document, Claude is a generic assistant that knows nothing about you, your role, or TELEO. With one, every response is calibrated to your work — no re-explaining yourself every session.

WITHOUT A CONTEXT DOC

❌ Re-explain your role every session

❌ Generic responses not calibrated to PE

❌ Claude doesn't know your portcos

❌ Output format doesn't match your style

❌ Doesn't know what metrics matter to you

WITH A CONTEXT DOC

✓ Claude knows your role and background

✓ Responses use TELEO terminology and context

✓ References your portcos naturally

✓ Output matches how you want to receive information

✓ Focuses on metrics and priorities that matter

How It Works

Three steps, about 5 minutes

1

Build your document on this page

Answer questions about your role, work style, and priorities. We'll generate a personalized context document you can download.

2

Create a Project in Claude

Go to claude.ai → click Projects in the left sidebar → New Project. Name it something like "My Work — [Your Name]." This is where all your conversations will live.

3

Add your context document to the Project

Inside your Project, click the Settings or edit icon. Find the Project Instructions field. Paste your downloaded document in and save. Done — every conversation you start inside this Project will automatically have your context.

Use this document as your starting point for any Claude Project. The base document works across all TELEO work — deals, portcos, BD. If you're setting up a dedicated Project for a specific portco or use case, consider customizing a copy of this document with additional context specific to that work. The more specific the context, the better the output.

Bonus Round 🎯

Key documents to upload to your Project

Claude works best when it can reference your actual materials. Select your workstream below to see which documents to gather.

↑ Select a workstream above to see your document checklist

Context Document Builder

Tell Claude about you

Work through each section below. Your answers will be used to generate a personalized context document. Select everything that applies — you can always edit the document after downloading.

About You

Basic information Claude will use to understand your role and background.

Your Name

LinkedIn Profile URL

Claude will reference your background and skillset from your LinkedIn profile.

Your Role at TELEO

◈

Deal / M&A Team

Principals, VPs, Associates focused on sourcing and transactions

◎

Portfolio Operations

Ops team supporting portcos on GTM, finance, and technology

◉

Business Development

BD professionals focused on deal sourcing and firm relationships

Years of Experience

0–3 years 4–7 years 8–15 years 15+ years

Key Areas of Expertise (select all that apply)

Go-to-market strategy Financial analysis M&A / due diligence Sales operations Marketing strategy Technology / product Deal sourcing Portfolio operations Finance & accounting Legal & compliance HR & talent

How Claude Should Work With You

Select the preferences that match how you like to receive information. Claude will follow these by default in every response.

Output Format (select all that apply)

Lead with the "so what" — bottom line first, details below Executive summary (3–5 bullets) before structured detail Use tables for comparative or structured data Keep responses concise — depth only where it adds value PowerPoint-ready output when I ask for a document Proactively flag anomalies and risks when I share data

When I Ask for Options

Give 2–3 options with a clear recommendation and reasoning Give me a direct recommendation — I don't need options Present a balanced pros/cons analysis Give me options but flag which one you'd choose

Tone & Communication Style

Professional and direct — treat me as a sophisticated operator Collaborative — think out loud with me, show your reasoning Concise and efficient — minimal explanation, maximum substance Educational — explain the reasoning behind recommendations

Feedback Style

Push back if my framing or assumptions seem off Don't soften red flags — call a problem a problem Run a devil's advocate pass on materials unprompted Flag if information is missing that would change the conclusion Be diplomatic when discussing people or leadership Point out blind spots and weaknesses, not just strengths

Things Claude Should Always Do

Use TELEO terminology: "portco" not "portfolio company," "carve-out" not "separation" Distinguish between correlation and causation in any analysis Flag numbers or claims that need verification with [verify] Note data quality issues when analyzing pipeline or financial exports Separate what competitors claim from what they actually do Consider AI leverage opportunities in recommendations Suggest templating any task that could be reused Adjust urgency and format if I mention a deadline

Things Claude Should Never Do

Over-qualify or hedge every statement Pad responses with summaries of what it's about to do — just do it Ask multiple clarifying questions at once Use generic frameworks (BCG matrix, Porter's Five Forces) unless asked Give a framework when I need a decision Present balanced analysis when data clearly points one direction Cite general best practices as if they apply universally

Prompt Library

Ready-to-use prompts for your role

Copy any prompt below and paste it directly into Claude. These are designed to work best after you've added your context document to a Project.

Adoption Tracking

Claude Adoption Dashboard

Tracking document generation across the TELEO team.

By Role

By Title

Completion Records

Note on tracking: This dashboard records completions in your browser's local storage on this device. For team-wide tracking, share this page link and ask team members to view their own completions, or collect names manually from the records below. Data persists until browser storage is cleared.

A/B Test

See the difference your context doc makes

The best way to see the impact of your context document is to run the same prompt in two side-by-side Claude Projects — one bare, one with your context doc. Follow the steps below to set it up.

💡 What you'll need

Your generated context document (from the Build Doc tab) and a Claude account with Projects access. The whole setup takes about 3 minutes.

Step 1 — Create a Blank Project

Set up your "No Context" project

This project will be your control — a plain Claude with no instructions, so you can see what the default experience looks like.

1

Go to claude.ai and open Projects

Click Projects in the left sidebar, then click New Project.

2

Name it "Baseline — No Context"

This makes it easy to identify during the demo. Leave the Project Instructions field completely empty.

3

Save and open a new conversation inside it

Don't type anything yet — you'll run the test prompt here in Step 3.

Step 2 — Create Your Context Project

Set up your "With Context" project

This is your personalized project — Claude will have full knowledge of who you are, how you work, and what TELEO does before you type a single word.

1

Create a second new Project

Click New Project again and name it "[Your Name] — With Context".

2

Open Project Settings and find Project Instructions

Click the edit or settings icon inside the project. You'll see a Project Instructions text field.

3

Paste in your context document and save

Go to Build Doc tab, generate your document if you haven't already, copy it, and paste it into the Project Instructions field. Click Save.

4

Open a new conversation inside this project

Keep this tab open alongside the Baseline project — you'll run the same prompt in both.

Step 3 — Run the Same Prompt in Both

Send an identical prompt to each project

The more specific and role-relevant your prompt, the more dramatic the difference. Good prompts reference real work you'd do — not generic questions.

💬 Suggested demo prompts

Pick one that matches your role, or use your own. Copy it and paste it into both projects.

◈ Deal / M&A

I'm looking at a $20M ARR SaaS business being carved out of a large industrial conglomerate. What are the first 5 questions I should ask management?

Draft a one-page investment thesis for a founder-owned vertical SaaS business with 92% gross retention and $15M ARR growing 18% YoY.

◎ Portfolio Operations

Our portco has pipeline coverage of 1.8x and win rates dropped from 28% to 19% over the last two quarters. What should I focus on first?

Help me build a 90-day onboarding plan for a new VP of Sales joining a B2B SaaS portco with a broken sales process.

◉ Business Development

Map out the key players in the fleet telematics software market — who are the likely carve-out or founder-owned targets we should be calling?

Draft a cold outreach email to the CEO of a $25M ARR logistics software company that hasn't raised outside capital.

What to look for: The Baseline project will give you a generic response with no awareness of TELEO, your role, or your preferences. The Context project should reference your background, use TELEO terminology, tailor its format and tone to your stated preferences, and focus on the metrics and priorities you selected. The difference is usually obvious within the first few sentences.

Build Your Claude
Context Document

A context document makes Claude dramatically more useful

Three steps, about 5 minutes

Key documents to upload to your Project

Tell Claude about you

Your context document is ready

Ready-to-use prompts for your role

Claude Adoption Dashboard

See the difference your context doc makes

Set up your "No Context" project

Set up your "With Context" project

Send an identical prompt to each project

Build Your ClaudeContext Document

A context document makes Claude dramatically more useful

Three steps, about 5 minutes

Key documents to upload to your Project

Tell Claude about you

Your context document is ready

Ready-to-use prompts for your role

Claude Adoption Dashboard

See the difference your context doc makes

Set up your "No Context" project

Set up your "With Context" project

Send an identical prompt to each project

Build Your Claude
Context Document