A Tailored One-Pager for a Specific Deal
Produce a leave-behind built for one buyer — their problem, their stakeholders, their objections answered — instead of emailing the generic deck and hoping it lands.
The generic deck is about you. The asset that moves a deal is about them.
A buyer forwards the thing that speaks to their situation, not your standard overview. Store your offer, proof, and brand, and deal context becomes a one-pager framed around their problem and the objections their stakeholders will raise — fast enough to make per deal.
The standard deck gets skimmed and filed. The version that names the prospect's actual problem gets forwarded to the person who signs.
An asset earns a forward when the buyer sees their own situation in it — not your feature list.
Tailored doesn't mean fabricated. Use real proof and honest claims; a one-pager that overpromises closes a meeting and loses the deal at procurement.
| Complexity | Easy |
| Tools needed | Claude Pro or above, Claude Desktop → Cowork mode, on macOS or Windows, Claude Projects |
| Time to build | ~25 min first time · ~10 min per deal after that |
| Best for | Founder or sales lead who makes their own collateral — B2B services and agencies |
What this solves
Deals losing momentum because the only thing fast enough to send is the generic deck — and the buyer can tell.
The problem
A deal is progressing and the champion needs something to show their boss or their team. You have a standard deck and a generic one-pager, so you send those — and they get skimmed and filed, because they’re about your product in general, not this buyer’s specific problem. What actually moves the deal internally is a page the champion can forward that frames the conversation around their situation: the problem they described, the stakeholders who’ll weigh in, the objections those people will raise. Building that per deal feels like too much work, so you send the generic version and lose a little momentum each time.
The fix is making a genuinely tailored asset fast enough to produce for every real deal.
Ingredients
- Claude Subscriptions — Cowork and Projects aren't available on the free plan
- Platforms & Modes — Cowork runs in the desktop app only — not on web or mobile. This recipe assembles a tailored asset from your materials — multi-step work that runs in Cowork
- Claude Projects — Your offer, your proof points, and your brand are constant. A Project stores them so every asset is on-brand and accurate, tailored only where it should be
How it works
You create assets for different deals, but your offer, proof, and brand are fixed. A Project stores them so every asset is accurate and on-brand, and you’re only tailoring the framing to the buyer — not rebuilding from scratch.
- Open Claude Desktop and click Cowork in the mode selector across the top (Chat · Cowork · Code).
- In the left panel, find Projects and click the + button.
- Choose Start from scratch. Name the project “Sales Assets” and let Claude set up its folder.
- You’ll know it worked when the project appears in the left panel with its own folder and an instructions field.
Your project has a folder on your computer — that’s where the two working files live.
- Ask Claude, right in the project: “Create two files in this project’s folder:
offer-and-proof.mdandbrand.md. Leave them empty — I’ll fill them in.” (Or create them yourself in any text editor and save them into the project folder.) - Fill in both files using the descriptions below.
- Confirm Claude can see them: ask “List the files you can see in this project.” Both filenames should come back. If they don’t, see If It Doesn’t Work.
offer-and-proof.md
What you sell and the real proof behind it — outcomes, numbers, named results you can stand behind. This is what keeps a tailored asset honest instead of overpromising.
Example: “We cut follow-up time for services teams. Proof: [Client] went from 2-day to same-day response; [Client] recovered 18% more leads in a quarter. Only use claims with a real source — never invent a stat to fit a deal.”
brand.md
Your visual and voice standards — tone, structure, what your assets look like — so tailored output still looks like it came from you.
Example: “Direct, concrete, no hype. One-pagers: problem at top, approach, proof, clear next step. Voice matches our site. No jargon.”
Open your Project in Claude Cowork. Give Claude the specifics for this run, ask for the main output, then follow up for any additional pieces you want. The exact wording for each prompt — with what it’s asking for and why — is in What you actually type below.
Check three things before you send it:
- It’s about them, not you. The asset should open with the buyer’s problem, not your company. If it reads like a product overview with their logo, it’ll get filed like one. Push for the version framed around their situation.
- Every claim is real. This is the one to watch hardest: a tailored asset is tempting to over-tailor with a stat that “would fit.” Confirm every proof point traces to
offer-and-proof.md. An invented number closes a meeting and dies at procurement. - It’s on-brand. Tailored framing shouldn’t mean off-brand voice. Run it against
brand.md— it should look and sound like it came from you, just aimed at this buyer.
Before you send: does it match what the champion actually needs to sell internally? You know the politics of this deal; the asset should arm the champion for the specific room it’s walking into. Your read of the buying group is what makes it land.
What you actually type
Name your files explicitly the first few runs, and ask Claude to show its work on anything that matters.
“Build a one-page leave-behind for [company]. Their situation: [paste your notes — their problem, who's involved, what they've objected to]. Using `offer-and-proof.md` and `brand.md`, frame it around their specific problem, speak to the stakeholders who'll see it, pre-answer the objection they raised, and end with a clear next step. Only use proof points from the file — flag if you'd want a stat we don't have.”
“Turn this into a short 3-slide version for their internal review meeting.”
A one-page leave-behind that opens with the buyer's problem, speaks to the stakeholders who'll see it, pre-answers the objection they raised, and ends with a clear next step — every proof point traceable to your file, with a flag wherever Claude wanted a stat you don't have. On request, a 3-slide version for their internal review meeting. If it opens with your company instead of their problem, or a number appears that isn't in `offer-and-proof.md`, it missed — send it back.
- It can't invent proof, and the recipe forbids it trying. If `offer-and-proof.md` is thin, the asset will be honest but light — the fix is collecting real results, not loosening the rule.
- It only knows the deal context you paste in. The politics of the buying group — who actually signs, what the champion needs to survive the room — comes from you.
- It writes the content, not the finished design. Turning it into a polished branded document or deck is the Extra Credit step, not the default output.
If it doesn’t work
- No Cowork tab in Claude Desktop — update the app to the latest version and confirm you’re on a paid plan; Cowork isn’t on the free tier. On Windows, Cowork also needs the Virtual Machine Platform feature enabled — if the tab still won’t appear, that’s the fix.
- Claude can’t see
offer-and-proof.mdorbrand.md— the files aren’t in the project’s folder, or they’re in a different folder than the one the project owns. Open the project, check which folder it points to, and move the files there. Then re-run “list the files you can see.” - The asset reads like a product overview with their logo on it — Claude got no real deal context, or the prompt didn’t name the files. Paste the buyer’s actual situation — their problem, the stakeholders, the objection they raised — and say “using
offer-and-proof.mdandbrand.md” explicitly. No context in, no tailoring out. - A stat appears that isn’t in
offer-and-proof.md— the prompt’s guardrail does the work: “only use proof points from the file — flag if you’d want a stat we don’t have.” If a number slipped through anyway, ask: “Trace every claim in this asset tooffer-and-proof.mdand flag anything you can’t.” Cut whatever doesn’t trace before you send.
Extra credit
Small additions that pay back the next time you run it.
- Polished formats — once the content’s right, have Claude build it as a clean document or short deck using your brand styling, ready to send.
- CRM connector — pull the deal context from your CRM so the asset reflects the latest notes automatically. See the Connectors guide.
- Reusable shell — keep the best tailored one-pager as a model so the next deal’s asset starts from a proven structure, just re-aimed.
“Buyers don't forward your overview. They forward the one page that describes their own problem back to them.”
What this teaches you about Claude Cowork
The recipe is one application. The principles apply to everything you’d hand to Claude.
Tailoring is the difference between filed and forwarded. A generic asset is about you; the one that moves a deal is about the buyer. Storing your offer and brand lets Claude tailor only the framing — fast enough to do per deal, which is what makes the tailored version actually happen.
Real proof is non-negotiable. The risk with tailored collateral is inventing a stat that fits. Keeping proof in a file and forbidding anything outside it is what keeps a persuasive asset from becoming one that collapses under scrutiny.
On-brand and on-target at once. Stored brand standards mean tailoring the message doesn’t cost you consistency. Every deal gets an asset aimed at it that still unmistakably comes from you.
Who this is for
Founder or sales lead who makes their own collateral in B2B services and agencies (5–100 employees).
The pain: Sending the generic deck because tailoring takes too long
The outcome: Every real deal gets a forwardable one-pager framed around the buyer's problem
Published June 30, 2026 · 0 views