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

If Claude Skills is new to you

Skills are reusable folders of instructions, resources, and optional scripts that Claude can load when a task matches the Skill description. Anthropic's current help says Skills are available on Free, Pro, Max, Team, and Enterprise plans when code execution is enabled.

For this workflow, you only need the basics: create a folder with a Skill.md file, ZIP the folder, upload it in Claude under Customize > Skills, enable it, and test that Claude routes proposal FAQ requests to the Skill. The Claude Skills tool hub is useful further reading, but the setup steps you need are included below.

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 one proposal-support FAQ that answers common questions without expanding scope, softening boundaries, or making unapproved promises.

What skill you will use in this workflow

You will build a private custom Skill called proposal-faq-builder. Its job is to group repeated prospect questions, normalize wording, draft concise client-facing answers, and keep review-needed items separate from answers you already approve.

This task is repetitive enough for a Skill because your FAQ should use the same boundary rules every time: what is included, what is not included, what requires a separate quote, what depends on project type, and what needs legal, pricing, or founder review before it appears in a proposal.

Before using the Skill, prepare a small set of real prospect questions, your current proposal or SOW language, and a short reference note that states your delivery boundaries.

Prerequisites

• Claude with Skills available and code execution enabled.
• A sample of real prospect questions from email, discovery calls, or message threads.
• Your current delivery policy, scope boundaries, revision rules, payment cadence, and approval process.
• One recent proposal or statement of work that reflects how you work now.
• A human reviewer who can approve scope, pricing, legal wording, and outcome claims before the FAQ is reused.

How to gather the source material

1. Pull repeated prospect questions into one document. Use real questions from email, calls, chat, proposal comments, or discovery notes.
2. Delete duplicates and merge similar wording into a short list. Keep enough variation to show what prospects actually ask.
3. Add your current proposal or SOW so Claude can ground answers in real terms instead of memory.
4. Create one file called policy-reference.txt with your actual revision limits, payment cadence, timeline assumptions, included work, excluded work, and out-of-scope rules.
5. Mark anything that varies by project type, package, or contract. The Skill should label those as variable instead of pretending one answer fits every proposal.

Build the custom skill for this workflow

Create a folder named proposal-faq-builder. Inside it, create a file named Skill.md. Paste the starter Skill below, then edit it so it matches your actual service language and proposal boundaries.

When the folder is ready, ZIP the folder itself so the ZIP file contains proposal-faq-builder/Skill.md at the root. In Claude, open Customize > Skills, upload the ZIP file, and enable the Skill before you run the workflow.

Use this as a starting template, not a perfect final Skill:

---
name: proposal-faq-builder
description: Turn repeated prospect questions and objections into a reusable proposal FAQ with grouped questions, concise answers, and review-needed flags.
---

# Proposal FAQ Builder

Use this skill when the user wants to turn repeated prospect questions into a reusable FAQ that supports proposals or sales conversations.

## What this skill should do
- Group repeated questions into clean FAQ entries.
- Rewrite answers in concise client-facing language.
- Flag any answer that needs legal, pricing, or scope review.

## Guardrails
- Do not promise outcomes.
- Do not imply included work that is not actually included.
- Keep answers short and direct.
- Separate approved answers from review-needed answers.

## Examples
- Turn these repeated prospect questions into a reusable proposal FAQ.
- Use my proposal FAQ workflow on these sales objections.
- Group the questions, draft short answers, and flag anything that needs review.

Optional official Anthropic skill

Anthropic's official internal-comms skill is the closest public reference because proposal FAQs are a form of structured internal or client-facing communication. It can be a useful shortcut for seeing how FAQ-style communication instructions are written.

Use the private proposal-faq-builder Skill for the actual workflow when your FAQ needs your own service language, offer boundaries, pricing caveats, revision rules, and approval language. A public Skill should not decide what your freelance service includes.

Skill-creator helper

Anthropic's official skill-creator skill can help draft or refine your private Skill if you want Claude to improve the Skill instructions before you upload them. Review the generated files before enabling any Skill, especially if it includes scripts or bundled resources.

Why this should be a custom skill, not a one-off prompt

A one-off prompt is easy to forget and easy to soften under pressure. A custom Skill keeps the same FAQ sections, review flags, and boundary rules available every time you update proposal language. That matters when the goal is not just nicer wording, but fewer repeated questions and fewer accidental promises.

Skill trigger test

After enabling proposal-faq-builder, test it with a small question set before processing your full backlog. Use two or three real questions plus your policy-reference.txt.

Try prompts like:

• Turn these repeated prospect questions into a reusable FAQ.
• Use my proposal FAQ workflow on this objections list.
• Draft short client-facing answers and flag anything that needs review.
• Build a proposal FAQ from these questions without promising scope, pricing, or outcomes beyond my reference note.

If Claude does not appear to use the Skill, revise the Skill description so it clearly mentions proposal FAQs, repeated prospect questions, objections, grouped answers, and review-needed flags.

Numbered workflow steps

1) Gather and clean the source material

Create a source package with three parts:

• prospect-questions.txt with repeated questions and objections.
• current-proposal-or-sow.txt with a recent proposal, SOW, or proposal section that reflects how you work now.
• policy-reference.txt with approved boundaries for scope, revisions, pricing caveats, timelines, approval, and out-of-scope work.

Remove client names unless they are needed for context. Keep examples realistic, but do not include private data that does not help the FAQ.

2) Create or enable the custom Skill

If this is your first run, create and upload proposal-faq-builder using the build steps above. If you already created it, open Claude's Skills settings and confirm the Skill is enabled before starting a new chat.

Use a fresh chat for the production run so the Skill starts from the current source package, not an old discussion.

3) Run a quick trigger test

Before the full run, paste a small mixed sample of prospect questions and ask:

Use my proposal FAQ workflow on these repeated prospect questions. Group the questions, draft short answers, and flag anything that needs pricing, scope, or legal review.

Check that Claude produces grouped FAQ entries, keeps review-needed items visible, and does not promise work, pricing, timelines, or outcomes that your reference note does not support.

4) Run the actual workflow with the Skill active

Attach or paste the full question set, current proposal or SOW language, and policy-reference.txt. Ask Claude:

Use proposal-faq-builder to turn these repeated prospect questions into a reusable proposal FAQ. Base answers on the proposal and policy reference. Keep answers concise, separate approved answers from review-needed answers, and do not promise scope, pricing, timelines, or outcomes beyond the source material.

The useful output is not just a polished FAQ. It should also show where your current documents do not answer recurring questions cleanly.

5) Review the FAQ before reuse

Do a human pass before the FAQ goes into a proposal template, sales email, or client-facing document. Check:

• Does each answer match your current proposal and policy language?
• Are variable answers marked instead of hidden?
• Are pricing and scope statements accurate for the offer?
• Are legal, compliance, or guarantee-like statements flagged for review?
• Did Claude avoid deciding questions that need your explicit business judgment?

If Claude cannot answer a recurring question from your real policies, treat that as a business process signal, not just a writing gap.

6) Save, send, or reuse the result

Save the approved FAQ beside your proposal template or sales materials. Keep the review-needed list with it so you know what still needs a decision.

When your offer, pricing, revision policy, or delivery process changes, update policy-reference.txt and rerun the Skill before reusing the FAQ.

Tool-specific instructions

Claude Skills

Use proposal-faq-builder as the main workflow tool. The Skill should encode your FAQ structure, approved answer rules, review-needed flags, and boundaries around scope, pricing, timelines, and outcomes.

Use the official skill-creator skill only as a helper for drafting or improving your private Skill. Treat the Claude Skills tool hub as further reading for broader setup context, not a prerequisite for this workflow.

Official public skill reference

The internal-comms public Skill is a relevant reference for FAQ-style communication patterns. It is not a substitute for your private proposal FAQ Skill because it does not know your packages, contract language, review rules, or offer boundaries.

Quality checks

1. Each FAQ answer matches your current proposal, SOW, or policy reference.
2. Variable answers are marked instead of hidden.
3. The FAQ reduces prospect confusion without becoming legal language.
4. No answer promises scope, pricing, timelines, deliverables, or outcomes beyond what you actually offer.
5. Review-needed answers stay separate from approved answers.
6. The final FAQ is short enough to live inside a proposal or proposal appendix.

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 and rerun the Skill.

Claude resolves a business decision on its own

Fix: revise the Skill guardrails so pricing, scope, legal, and outcome questions are flagged for review unless your source material gives an approved answer.

The FAQ gets too long

Fix: keep only questions that truly recur and cut one-off edge cases. Move rare questions into a private answer bank instead of the proposal FAQ.