A Claude Project is a persistent workspace that remembers a system prompt and uploaded documents across every conversation inside it — which makes it the right home for specialized sales assistants. Set one up in five minutes, load it with a role-specific system prompt and your account context, and every conversation in that project starts as a specialist instead of a blank slate.
Specialized system prompts are only as useful as the setup around them. A great discovery-analyst prompt pasted into a fresh chat evaporates when the conversation ends; the same prompt installed as project instructions becomes a standing capability you return to daily.
What a Claude Project actually is
Unlike a regular conversation that starts fresh each time, a Project remembers its system prompt across every conversation inside it, holds uploaded files and documents that persist across sessions, and can be named, organized, and reused indefinitely. Paste a specialized sales system prompt into the project instructions and every conversation in that project runs Claude in that role — no re-pasting, no drift.
Setting up your first project in five minutes
- Go to claude.ai — a free account works.
- In the left sidebar, click the plus next to Projects, or New Project.
- Name it clearly. "MEDDPICC Discovery Analyst" or "SDR Cold Outreach" beat "Sales Project 1" — the name is how you will find it at speed.
- Click "Set project instructions."
- Paste the full system prompt for the role you want — from the Promptifi Claude Skill library or one you have written.
- Save, and start your first conversation in the project.
If you are writing your own instructions rather than pasting a prepared skill, start from this frame:
Prompt: "You are a [ROLE — e.g., MEDDPICC discovery analyst / cold outreach specialist / pipeline coach] for a rep selling [SOLUTION] to [ICP] in [INDUSTRY]. Your job in every conversation: [PRIMARY TASKS]. Always structure output as [FORMAT]. Never [BEHAVIORS TO EXCLUDE — invented statistics, generic filler, vendor-speak]."
The projects most reps should have
For SDRs and BDRs: an elite cold outreach specialist. For AEs: a discovery and deal intelligence analyst plus a pipeline coach and deal strategist. For CSMs: an account growth and retention advisor. For sales managers: a coaching and team performance partner. For everyone: a CRM intelligence and documentation specialist that turns raw notes into structured records. Start with the one that matches your heaviest weekly workload; add the second only after the first is habitual.
What to upload beyond the system prompt
The system prompt sets the role; the uploads set the context. Add your ICP profile, your product's key differentiators and competitive positioning, your latest battlecard against your top competitor, and the discovery notes for deals you are actively working. Each document becomes context Claude references in every conversation — a qualification analysis of a call gets dramatically more specific when the project already knows your ICP and positioning.
Prompt: "Using my uploaded ICP profile and battlecard, score this discovery call: [PASTE NOTES]. Flag where the prospect matches or misses our ICP, note any competitor signals against the battlecard, and give me the three questions for the next call."
Per-deal projects: the pattern that compounds
Beyond role projects, create a project per major deal, named after the account, holding every call note, email thread, and document for that opportunity. Ask it anything — "what did the CFO say about timeline?", "draft the recap referencing our security discussion" — and it answers from the accumulated record. The per-deal project quietly becomes the best-organized account file you have ever kept, and it hands off cleanly if the deal changes owners.
Keeping projects from going stale
A project is only as good as its most recent upload. Set two habits: refresh the battlecard and ICP documents whenever they change upstream, and prune per-deal projects when opportunities close — archive the wins as reference material, delete the rest. A monthly ten-minute review of project instructions catches drift, like a methodology change or new differentiators that never made it into the standing context. Stale context is worse than none, because outputs stay confident while quietly arguing from last quarter's positioning.
Building the library over time
Start with one or two projects. Add one per month as workflows earn them. After six months you will have a library of specialized partners — each tuned for a specific job — plus a per-deal archive for everything active. The compounding is the point: every conversation makes the next one better informed, which is exactly what an ad hoc chat can never do.
Frequently Asked Questions
Do Claude Projects require a paid plan?
Projects are available on free accounts with limits; heavier document uploads and daily use make a paid plan worthwhile. For a rep running per-deal projects with transcripts, paid is the practical answer.
How many Claude Projects should a sales rep maintain?
Two to four role projects plus one per major active deal. Beyond that, consolidation beats sprawl — an unused project is just a stale document store.
What is the difference between a Claude Project and a custom system prompt in a chat?
Persistence. A chat's context dies with the conversation; a Project's instructions and documents carry across every session, which is what turns a good prompt into a standing capability.
Put It to Work
Promptifi Pro includes 160+ complete Claude Skills — full system prompts built for exactly this setup — inside a library of 2,900+ B2B sales prompts across 16 categories. Browse the library and install your first specialist project in five minutes.