Prompt Chain in a Claude Project: From Discovery Transcript to a POC Plan

What This Builds

A ninety-minute discovery call usually turns into three separate documents over the following week: a requirements summary, a gap analysis against your catalog, and a POC plan with success criteria. Each one waits on the last, and each one gets written from scratch in a different tab. This chain keeps all three inside one Claude Project thread, where the output of one prompt becomes the input to the next, so a transcript becomes a full POC plan in a single sitting instead of three separate work sessions spread across a week.

Prerequisites

• Pro plan or higher ($20/month), the plan level where Projects is available
• Comfortable creating a Claude Project and adding files to its knowledge (Level 3 guide above)
• A discovery call transcript or detailed notes, and your product catalog or spec sheet as a file you can upload
• Total ongoing cost: $20/month (the Project holding your catalog and past answers already needs this plan, so this build adds no new subscription)

The Concept

A prompt chain is a set of prompts run one after another inside the same conversation, where each step's answer becomes part of the next question. Instead of asking Claude to do everything in one shot (which tends to produce a shallow pass at each part), you break the work into stages and check each one before moving on. It's closer to how you'd hand a task to a colleague in stages: draft the requirements, then the gap analysis, then the demo plan, checking each piece before it goes to the next person. The Project's knowledge (your catalog, past POC plans) stays available to every stage, so you're not re-uploading files between prompts.

Build It Step by Step

Part 1: Set Up the Project

If you don't already have one, create a new Claude Project called something like "Discovery to POC Chain." In the Project's knowledge section, add your current product catalog or spec sheet, and one or two past POC plans you're proud of, so the model has a sense of the format you want. Keep this separate from an RFP answer library project if you have one. It's a different job and mixing the two makes both harder to keep current.

Part 2: Run the Five Chained Prompts

Start a new chat inside the Project. Run each prompt below in order. After each response, read it, fix anything wrong or missing, and paste your corrected version forward before starting the next prompt. Don't skip the correction step. An error in stage one becomes a bigger error by stage four.

Prompt 1: Transcript to requirements summary

Before you paste the transcript in, replace the customer's company name with [Customer] and any employee names with their role (for example [IT Director]).

Here is a discovery call transcript with a prospective customer. Turn it into a structured requirements summary with these sections: Business Problem, Technical Requirements, Integration Constraints, Security or Compliance Requirements, Timeline, and Open Questions. Use only what's in the transcript. Where something is unclear or unstated, list it under Open Questions instead of guessing.

Transcript:
[paste transcript or notes here]

Prompt 2: Requirements summary to gap analysis

Using the requirements summary above and the product catalog in this project's knowledge, identify:
1. Requirements we fully meet, with the matching catalog feature
2. Requirements we partially meet, and what the gap is
3. Requirements we don't meet

Only cite features that actually appear in the uploaded catalog. If you're not sure a feature exists, say so instead of guessing.

Prompt 3: Gap analysis to demo plan

Using the gap analysis above, build a demo plan for [Customer]. Include: a suggested order for the features to show (lead with what fully meets their top requirement), a one-sentence talk track per feature tying it to something they said in discovery, and a list of the gaps we should address verbally before they come up as objections.

Prompt 4: Demo plan to POC success criteria

Using the demo plan and the confirmed gaps above, draft POC success criteria for [Customer]. Each criterion should be specific enough that both sides agree whether it passed or failed at the end of the trial. Group them into Must-Pass and Nice-to-Have.

Prompt 5: Success criteria to POC plan document

Combine everything above into a one-page POC plan for [Customer] with these sections: Scope, Timeline (weeks, not calendar dates), Resources Needed From Each Side, Success Criteria (from above), and Exit Criteria (what happens if it passes, what happens if it doesn't). Write it so I can paste it into an email to the customer with light editing.

Part 3: Test and Refine

Run the full chain once with a real (redacted) transcript before trusting it on a live deal. Watch for two failure patterns: the gap analysis citing a catalog feature that doesn't actually exist (check every citation against the real spec sheet), and the chain drifting away from what the customer actually said by stage four or five. If the final plan feels generic, go back and check whether your correction at Prompt 1 kept enough of the customer's specific language, since everything downstream is built on it.

Real Example: Mid-Market Logistics Software Deal

Setup: A ninety-minute discovery call with a logistics company evaluating a route-optimization platform. Their IT director raised concerns about a legacy ERP integration and data residency.

Input (Prompt 1): The redacted transcript, with [Customer] and [IT Director] standing in for real names.

Output after the chain:

• Requirements summary flagging the ERP integration and a data residency requirement (EU-based warehouse data) as the two open questions needing a follow-up call
• Gap analysis showing the platform fully meets the ERP integration through an existing connector, but data residency needs the EU hosting add-on, a partial match
• Demo plan leading with the ERP connector, with a talk track addressing data residency before the customer asks
• POC success criteria including "route recalculation completes in under [X] seconds during a live ERP sync test" as a Must-Pass item
• A one-page POC plan ready to send to the account executive for the customer email

Time saved: what used to take a follow-up call plus a day of writing across three documents happened in one working session, with each stage checked before moving forward.

What to Do When It Breaks

• The chain drifts off-topic after several turns → start a new chat in the same Project. The Project's knowledge carries over, so you're not starting from zero.
• The gap analysis cites a feature that isn't in your catalog → this is the model filling a gap instead of admitting one. Re-run Prompt 2 with an explicit line: "If a requirement has no matching feature in the catalog, say so plainly."
• The discovery notes are too messy for Prompt 1 to make sense of → feed in your own bullet notes instead of a raw transcript. A rough outline beats a rambling transcript for this step.
• The final POC plan reads generic, like it could apply to any customer → check Prompt 1's output. If it lost the customer's specific language, everything after it will too. Re-run it with tighter instructions to quote the customer directly where possible.

Variations

• Simpler version: Run just Prompts 1, 2, and 5, skipping the demo plan stage, when you only need the POC plan and not a scripted demo.
• Extended version: Add a sixth prompt that drafts the technical sections of the RFP or SOW from the confirmed POC plan, handing off to whatever document your team uses for handoff to implementation.

What to Do Next

• This week: Run the chain on one real discovery call and compare the time spent against your usual process.
• This month: Save your best chain outputs as examples in the Project's knowledge so future runs match your preferred tone.
• Advanced: Connect the POC plan's Must-Pass criteria to your weekly POC status report so the two don't drift apart over the life of the trial.

Advanced guide for sales engineer professionals. Strip customer names, employee names, and any network or architecture detail from a transcript before pasting it into the project. Check your Claude plan's data settings if you're on an individual paid plan rather than a business one, since a personal chat history setting may allow your conversations to be used for training unless you turn it off.