How Freelancers Can Use Claude Skills to Turn Repeated Prospect Questions Into a Proposal FAQ

Warning: Do not let a FAQ make promises you would not honor in a contract. Keep the source material current and remove any outdated pricing or scope language first.

If Claude Skills is new to you

Start with the Claude Skills explainer page in the site's Tools menu before you run this workflow. The short version is that Skills are reusable instruction bundles Claude can load for repeatable work. The public skills repository also makes good reference material when you want to copy the pattern into a private skill for your own team. For curated examples, see the Claude Skills tool hub and the Anthropic Workflows series.

Problem and who this is for

Freelancers answer the same prospect questions over and over: What is included? How many revisions? How long will it take? What happens after approval? A reusable FAQ block saves time, but only if it reflects how you actually work now, not how you worked six months ago.

This workflow is for freelancers and consultants who send proposals regularly and want a cleaner, more consistent answer bank.

Prerequisites

• Claude with Skills available.
• A sample of real prospect questions from email, discovery calls, or message threads.
• Your current delivery policy, scope boundaries, and approval process.
• One recent proposal or statement of work that reflects how you work now.

How to gather the source material

1. Pull the repeated prospect questions into one document. You do not need every email thread. A curated list is better.
2. Delete duplicates and merge similar questions into a single clean version.
3. Add your current proposal or SOW so Claude can answer from real terms instead of memory.
4. Create one file called policy-reference.txt with your actual revision limits, payment cadence, timeline assumptions, and out-of-scope rules.
5. If some answers vary by project type, label those variations in the reference note instead of forcing one generic answer.

Numbered workflow steps

1) Normalize the questions before you draft the FAQ

The internal-comms pattern fits this job because FAQ writing is really a consistency problem. Claude should first cluster the repeated questions and map them to policy-backed answers.

{
  "task": "Turn repeated prospect questions into a clean proposal FAQ map",
  "input": {
    "question_list": "ATTACH OR PASTE",
    "recent_proposal_or_sow": "ATTACH OR PASTE",
    "policy_reference": "PASTE policy-reference.txt"
  },
  "rules": [
    "Merge duplicate or near-duplicate questions.",
    "Base answers on the policy file and current proposal language.",
    "Flag any answer that varies by project type as [VARIABLE ANSWER].",
    "Do not write marketing copy."
  ],
  "output": {
    "normalized_questions": "Best version of each recurring question",
    "draft_answer_basis": "Policy-grounded answer notes",
    "variable_answers": "Answers that need a project-specific version",
    "gaps": "Questions that your current documents do not answer cleanly"
  }
}

2) Review the extracted material before Claude writes the final deliverable

Review the gaps section carefully. If Claude cannot answer a recurring question from your real policies, that is a business process signal, not just a writing problem.

3) Draft the final deliverable

{
  "task": "Write a proposal FAQ from a verified question-and-answer map",
  "input": {
    "verified_faq_map": "PASTE THE REVIEWED OUTPUT FROM STEP 1"
  },
  "rules": [
    "Write in plain business language.",
    "Keep answers short enough to live inside a proposal or proposal appendix.",
    "Use [PROJECT-SPECIFIC] markers where needed instead of pretending every answer is fixed.",
    "Do not promise anything that belongs only in the signed agreement."
  ],
  "output_format": {
    "type": "faq"
  }
}

4) Save the output where you actually work

Keep the final deliverable in the same folder as the source package, or paste it into the system you already use. The value here is repeatability. Once your source files and section order are stable, the next run gets much faster.

Tool-specific instructions

Claude Skills helps here by preserving the same FAQ structure every time you update it. The public internal-comms skill is directly relevant because it includes FAQ-oriented communication patterns.

Quality checks

1. Each FAQ answer matches your current proposal and policy language.
2. Variable answers are marked instead of hidden.
3. The FAQ reduces prospect confusion without becoming legal language.
4. No answer makes a promise your contract would later narrow.

Common failure modes and fixes

The FAQ sounds generic

Fix: feed in real proposal terms and real repeated questions, not hypothetical examples.

Answers drift from current policy

Fix: refresh policy-reference.txt before each major round of proposals.

The FAQ gets too long

Fix: keep only questions that truly recur and cut one-off edge cases.

Sources Checked

• Anthropic Claude Help Center: What are Skills? (accessed 2026-03-23) https://support.claude.com/en/articles/12512176-what-are-skills
• Anthropic Claude Help Center: Use Skills in Claude (accessed 2026-03-23) https://support.claude.com/en/articles/12512180-use-skills-in-claude
• Anthropic Claude Help Center: Creating custom Skills (accessed 2026-03-23) https://support.claude.com/en/articles/12512198-creating-custom-skills
• GitHub: elliepetalmedia/skills README (accessed 2026-03-23) https://github.com/elliepetalmedia/skills
• GitHub: internal-comms skill in elliepetalmedia/skills (accessed 2026-03-23) https://github.com/elliepetalmedia/skills/tree/main/skills/internal-comms

Quarterly Refresh Flag

Review on 2026-06-21 to confirm any updates to Claude Skills, Claude Cowork, file handling, plan availability, and setup paths.