How to design AI-powered Templates - Word and PowerPoint example

Writes the letter body only, inside the template’s salutation and sign-off, using Smart Fields for every name and title.

As used in the example template:

You are writing on behalf of Redmond Consulting, a global strategy and technology consulting firm. Write the body of a proposal cover letter from [ENGAGEMENT PARTNER Smart Field] to [CLIENT CONTACT NAME Smart Field], [CLIENT CONTACT TITLE Smart Field] at [CLIENT NAME Smart Field].

Read the proposal request email and the discovery call transcript in this Pursuit, and use the Pursuit Smart Fields for names, dates, and engagement details.

The letter body must:
- Thank the client for the request and reference our recent discussions with them, using the actual dates and meetings described in the Pursuit documents
- Confirm what we are submitting: a proposal covering our understanding of their situation, our approach, our team, our relevant experience, and commercials
- Briefly affirm, in one or two sentences, why Redmond is well suited, drawing on the Differentiators content source
- Confirm our availability to discuss the proposal and our commitment to their stated decision timeline
- Close warmly and professionally

Rules: 200-275 words, 3-4 short paragraphs, plain prose with no headings or bullet points. Do not include an address block, salutation, date, or signature — the template provides these. Do not mention fees, budgets, or pricing. Use only facts found in the Pursuit documents and Smart Fields; if a detail is not available, write around it rather than inventing it. Mirror the client's own terminology for their business and challenges.

Make it yours:

• Replace the [square bracket] placeholders: your organization’s name and a one-line description, and your differentiators content source’s name as it appears in your hub.
• The [NAME Smart Field] references pull live values from the Pursuit’s Smart Fields; swap them for the fields your Pursuit Type carries.
• Keep the rule that excludes the salutation and signature if your template provides them, and drop it if the field writes the whole letter.

You are writing on behalf of [YOUR ORGANIZATION NAME], [A SHORT DESCRIPTION OF WHAT YOUR ORGANIZATION DOES]. Write the body of a proposal cover letter from [ENGAGEMENT PARTNER Smart Field] to [CLIENT CONTACT NAME Smart Field], [CLIENT CONTACT TITLE Smart Field] at [CLIENT NAME Smart Field].

Read the proposal request email and the discovery call transcript in this Pursuit, and use the Pursuit Smart Fields for names, dates, and engagement details.

The letter body must:
- Thank the client for the request and reference our recent discussions with them, using the actual dates and meetings described in the Pursuit documents
- Confirm what we are submitting: a proposal covering our understanding of their situation, our approach, our team, our relevant experience, and commercials
- Briefly affirm, in one or two sentences, why [YOUR ORGANIZATION NAME] is well suited, drawing on the '[DIFFERENTIATORS CONTENT SOURCE NAME]' content source
- Confirm our availability to discuss the proposal and our commitment to their stated decision timeline
- Close warmly and professionally

Rules: 200-275 words, 3-4 short paragraphs, plain prose with no headings or bullet points. Do not include an address block, salutation, date, or signature — the template provides these. Do not mention fees, budgets, or pricing. Use only facts found in the Pursuit documents and Smart Fields; if a detail is not available, write around it rather than inventing it. Mirror the client's own terminology for their business and challenges.

A client-led summary with a prescribed five-part structure, grounded in the Pursuit documents and three content sources.

As used in the example template:

You are writing the Executive Summary of a Redmond Consulting proposal to [CLIENT NAME Smart Field].

Read the proposal request email and the discovery call transcript in this Pursuit. Use the Pursuit Smart Fields for engagement details, and draw on the Differentiators, Our Services, and Our Experience content sources.

Structure the summary as:
1. The client's situation and ambition in two or three sentences, using their own framing and the specific facts they shared (growth, acquisitions, operational pressures)
2. What success looks like — restate the client's stated success criteria as the outcomes this engagement will deliver, with their numbers
3. How we will get there — one short paragraph on our phased approach: a diagnostic and roadmap first, then phase-one implementation, delivered under the Redmond Catalyst Framework and sequenced around the client's stated constraints
4. Why Redmond — two or three sentences grounded in our differentiators and one quantified proof point from the Our Experience content source relevant to the client's sector or challenge
5. A one-sentence closing commitment

Rules: 300-400 words. Short paragraphs; one brief bulleted list is permitted for the success criteria only. Lead with the client, not with Redmond. Do not mention fees, budgets, or pricing. Use only facts from the Pursuit documents, Smart Fields, and the named content sources; do not invent clients, statistics, or capabilities. Format in Markdown without top-level headings.

Make it yours:

• Replace the [square bracket] placeholders: your organization’s name, your methodology or framework name, and your content source names as they appear in your hub.
• Adjust point 1’s examples to the facts your clients typically share, and the document names to what your Pursuits actually hold.

You are writing the Executive Summary of a [YOUR ORGANIZATION NAME] proposal to [CLIENT NAME Smart Field].

Read the proposal request email and the discovery call transcript in this Pursuit. Use the Pursuit Smart Fields for engagement details, and draw on the '[DIFFERENTIATORS CONTENT SOURCE NAME]', '[SERVICES CONTENT SOURCE NAME]', and '[EXPERIENCE CONTENT SOURCE NAME]' content sources.

Structure the summary as:
1. The client's situation and ambition in two or three sentences, using their own framing and the specific facts they shared
2. What success looks like — restate the client's stated success criteria as the outcomes this engagement will deliver, with their numbers
3. How we will get there — one short paragraph on our phased approach, delivered under [YOUR METHODOLOGY OR FRAMEWORK NAME] and sequenced around the client's stated constraints
4. Why [YOUR ORGANIZATION NAME] — two or three sentences grounded in our differentiators and one quantified proof point from the '[EXPERIENCE CONTENT SOURCE NAME]' content source relevant to the client's sector or challenge
5. A one-sentence closing commitment

Rules: 300-400 words. Short paragraphs; one brief bulleted list is permitted for the success criteria only. Lead with the client, not with [YOUR ORGANIZATION NAME]. Do not mention fees, budgets, or pricing. Use only facts from the Pursuit documents, Smart Fields, and the named content sources; do not invent clients, statistics, or capabilities. Format in Markdown without top-level headings.

The longest section, with Markdown subheadings, the firm’s methodology from the content sources, and the client’s stated dates and constraints used exactly.

As used in the example template:

You are writing the Project Overview section of a Redmond Consulting proposal to [CLIENT NAME Smart Field].

Read the proposal request email and the discovery call transcript in this Pursuit. Use the Pursuit Smart Fields for dates and engagement details, and draw on the Our Services and About Us content sources — in particular the Redmond Catalyst Framework — for how we describe our methodology.

Cover, in this order, using ### Markdown subheadings:
1. Scope — the areas of work the client has asked us to address, organized as they described them (network and inventory, integrated planning, systems and process integration, change management)
2. Our approach — how the Catalyst Framework phases apply to this engagement: a combined Discover and Diagnose diagnostic producing a cost-to-serve baseline, benchmarks, a network recommendation with business case, and a roadmap; then Design and Deliver as phase-one implementation; with Drive Adoption and Determine Impact embedding and measuring the change
3. Timeline and constraints — the phasing against the client's stated dates, explicitly honouring any change blackout or operating-calendar constraints they described, including structured site visits during the diagnostic
4. Governance and ways of working — the client's stated governance expectations (steering cadence, working-level cadence, on-site presence), plus our standard peer review and 90-day post-implementation support
5. What the client receives — a short list of the diagnostic-phase deliverables

Rules: 450-550 words. Do not mention fees, budgets, or pricing. Use only facts from the Pursuit documents, Smart Fields, and the named content sources. Where the client stated specific numbers, dates, or constraints, use them exactly; where something was not specified, describe our standard practice from the content sources rather than inventing client-specific detail.

Make it yours:

• Replace the [square bracket] placeholders: your organization, content source names, and methodology or framework name.
• The example’s scope list and phase descriptions are specific to this engagement and this firm’s methodology; the generic version describes the shape and leaves the specifics to your content sources and the client’s documents.
• Swap the quality and support commitments for your organization’s standard practices.

You are writing the Project Overview section of a [YOUR ORGANIZATION NAME] proposal to [CLIENT NAME Smart Field].

Read the proposal request email and the discovery call transcript in this Pursuit. Use the Pursuit Smart Fields for dates and engagement details, and draw on the '[SERVICES CONTENT SOURCE NAME]' and '[ABOUT US CONTENT SOURCE NAME]' content sources — in particular [YOUR METHODOLOGY OR FRAMEWORK NAME] — for how we describe our methodology.

Cover, in this order, using ### Markdown subheadings:
1. Scope — the areas of work the client has asked us to address, organized as they described them
2. Our approach — how the phases of [YOUR METHODOLOGY OR FRAMEWORK NAME] apply to this engagement, from the initial diagnostic through implementation to embedding and measuring the change
3. Timeline and constraints — the phasing against the client's stated dates, explicitly honouring any operating-calendar constraints they described
4. Governance and ways of working — the client's stated governance expectations, plus [YOUR STANDARD QUALITY AND POST-IMPLEMENTATION PRACTICES]
5. What the client receives — a short list of the first phase's deliverables

Rules: 450-550 words. Do not mention fees, budgets, or pricing. Use only facts from the Pursuit documents, Smart Fields, and the named content sources. Where the client stated specific numbers, dates, or constraints, use them exactly; where something was not specified, describe our standard practice from the content sources rather than inventing client-specific detail.

A fee schedule whose every rate comes from one content source, with consistency rules a person can check and the client’s stated budget as the envelope.

As used in the example template:

You are writing the Project Pricing section of a Redmond Consulting proposal to [CLIENT NAME Smart Field].

Read the documents in the "Customer Documents" folder of this Pursuit — in particular the discovery call transcript, which contains the client's stated budget parameters, timeline, governance expectations, and constraints. Use the Commercials content source — in particular the Standard Rate Card, the Engagement Pricing Models and Fee Structures document, and the Sample Fee Schedule — as the only source of rates, fee ranges, and commercial terms.

Structure the section as:
1. Our commercial approach — one short paragraph: phased commitment, each gate earning the next, consistent with what we discussed with the client
2. Fee schedule — a table with columns Phase, Duration, Pricing Model, and Professional Fees (USD), with one row per engagement phase and a program total row. Derive the phases and durations from the approach and timeline discussed in the call transcript. Follow the structure of the Sample Fee Schedule. Price the diagnostic and roadmap as a fixed fee and the implementation phase as a monthly run rate, choosing amounts from within the typical ranges in the Engagement Pricing Models document.
3. Rates and team basis — one short paragraph stating that fees reflect the 2026-2027 standard rate card and the diagnostic team configuration, per the rate card roles
4. Assumptions and expenses — a short bulleted list: client responsibilities as discussed in the call (data access, stakeholder availability, site access), travel and expenses at cost within the standard cap, taxes excluded, invoicing and payment terms, change control
5. Discounts — state any multi-phase or program-volume discount that applies under the rate card rules, with the discounted program total

Rules: every rate, fee range, discount rule, and commercial term must come from the Commercials content source — do not invent or adjust them. Choose phase fees so the arithmetic is simple and the table is internally consistent: the program total must equal the sum of the phase rows, and the monthly run rate multiplied by the number of months must equal that row's total. The program total must fall within the budget envelope the client stated in the call transcript; if it would not, reduce the implementation duration or team configuration rather than discounting below the rate card rules. Respect any change blackout or operating-calendar constraints the client described when stating phase timing. Label all figures as indicative and subject to confirmation at contracting. 400-500 words plus the table. Do not include rate-card daily rates for roles not used in this engagement.

Make it yours:

• Verify every figure before the proposal goes out. The rules keep the table simple enough to check at a glance, but AI predicts language, not math: it may quote amounts from your fee documents rather than calculate, and totals need a human pass. That is what the indicative-figures label is for.
• Replace the [square bracket] placeholders: your organization, your commercials content source’s name, and the names of your rate card, pricing models, and sample fee schedule documents.
• Adjust the currency, the pricing models per phase, and the rate card reference to your own commercial standards.
• Swap ‘Customer Documents’ for your Pursuit Type’s upload folder name if it differs.

You are writing the Project Pricing section of a [YOUR ORGANIZATION NAME] proposal to [CLIENT NAME Smart Field].

Read the documents in the "Customer Documents" folder of this Pursuit — in particular the discovery call transcript, which contains the client's stated budget parameters, timeline, governance expectations, and constraints. Use the '[COMMERCIALS CONTENT SOURCE NAME]' content source — in particular [YOUR RATE CARD DOCUMENT NAME], [YOUR PRICING MODELS DOCUMENT NAME], and [YOUR SAMPLE FEE SCHEDULE DOCUMENT NAME] — as the only source of rates, fee ranges, and commercial terms.

Structure the section as:
1. Our commercial approach — one short paragraph: phased commitment, each gate earning the next, consistent with what we discussed with the client
2. Fee schedule — a table with columns Phase, Duration, Pricing Model, and Professional Fees ([CURRENCY]), with one row per engagement phase and a program total row. Derive the phases and durations from the approach and timeline discussed in the call transcript. Follow the structure of [YOUR SAMPLE FEE SCHEDULE DOCUMENT NAME]. Price each phase using the pricing model your commercial standards assign to that kind of work, choosing amounts from within the typical ranges in [YOUR PRICING MODELS DOCUMENT NAME].
3. Rates and team basis — one short paragraph stating that fees reflect [YOUR CURRENT RATE CARD] and the proposed team configuration, per the rate card roles
4. Assumptions and expenses — a short bulleted list: client responsibilities as discussed in the call, travel and expenses treatment, taxes, invoicing and payment terms, change control
5. Discounts — state any discount that applies under the rate card rules, with the discounted program total

Rules: every rate, fee range, discount rule, and commercial term must come from the '[COMMERCIALS CONTENT SOURCE NAME]' content source — do not invent or adjust them. Choose phase fees so the arithmetic is simple and the table is internally consistent: the program total must equal the sum of the phase rows, and any monthly run rate multiplied by its number of months must equal that row's total. The program total must fall within the budget envelope the client stated; if it would not, reduce the duration or team configuration rather than discounting below the rate card rules. Respect any operating-calendar constraints the client described when stating phase timing. Label all figures as indicative and subject to confirmation at contracting. 400-500 words plus the table.

Proof of listening: the client’s situation, issues, and stakes in their own terminology and numbers.

As used in the example template:

You are writing the "Understanding Your Situation" content for a one-slide section of a Redmond Consulting services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as Redmond speaking to them: "we" is Redmond, "you" is the client. Use the client's company name at most once.

Read the Pursuit documents. Write a tight summary of your understanding of their situation that proves we listened, using their own terminology and numbers wherever possible.

Write exactly three short paragraphs, separated by blank lines, with no headings and no bullet points:

Paragraph 1 — your situation: what your regulator's examination was and what it responds to, in one or two sentences.

Paragraph 2 — the findings: the three examination findings you described to us, woven into two or three sentences, each carrying at least one specific detail you told us rather than a category label.

Paragraph 3 — the clock and the stakes: your remediation deadline, and what you have told us is at stake, in one or two sentences.

150 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. No text about Redmond's capabilities — this content is about your situation as we understand it. Use only facts from the Pursuit documents; do not invent findings, dates, or figures, and do not soften what you told us.

Make it yours:

• Replace [YOUR ORGANIZATION NAME] and keep the voice block word for word; it is what keeps the output a pitch rather than a briefing.
• The example names the client’s situation (a regulator’s examination, three findings) in the briefs; the generic version describes the paragraphs functionally so it works for any pitch.

You are writing the "Understanding Your Situation" content for a one-slide section of a [YOUR ORGANIZATION NAME] services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as [YOUR ORGANIZATION NAME] speaking to them: "we" is [YOUR ORGANIZATION NAME], "you" is the client. Use the client's company name at most once.

Read the Pursuit documents. Write a tight summary of your understanding of their situation that proves we listened, using their own terminology and numbers wherever possible.

Write exactly three short paragraphs, separated by blank lines, with no headings and no bullet points:

Paragraph 1 — your situation: the event or pressure that brought you to us, and what it responds to, in one or two sentences.

Paragraph 2 — the issues: the specific issues you described to us, woven into two or three sentences, each carrying at least one specific detail you told us rather than a category label.

Paragraph 3 — the clock and the stakes: your deadline, and what you have told us is at stake, in one or two sentences.

150 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. No text about [YOUR ORGANIZATION NAME]'s capabilities — this content is about your situation as we understand it. Use only facts from the Pursuit documents; do not invent issues, dates, or figures, and do not soften what you told us.

One paragraph per client issue, pairing it with the capability that answers it, drawn from the services content source.

As used in the example template:

You are writing the "Our Capabilities" content for a one-slide section of a Redmond Consulting services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as Redmond speaking to them: "we" is Redmond, "you" is the client.

Read the Pursuit documents, and use the Our Services content source for how Redmond describes its risk and regulatory capabilities.

Write exactly three short paragraphs, separated by blank lines, with no headings and no bullet points — one paragraph per examination finding you raised with us, in the same order you raised them:

Paragraph 1 — the capability that answers your fragmented risk governance: compliance operating model redesign, in one or two sentences tying it to your situation.

Paragraph 2 — the capability that answers your manual compliance processes across legacy platforms: controls uplift and automation, in one or two sentences tying it to your situation.

Paragraph 3 — the capability that answers your delays in surfacing and reporting compliance incidents: regulatory remediation program delivery, in one or two sentences tying it to your situation, including how we build your team's capability as we deliver.

200 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. Describe capabilities only in terms the Our Services content source supports; do not invent offerings, tools, or claims. Every paragraph must connect a capability to something specific you told us — this slide answers you, it does not recite a brochure.

Make it yours:

• Replace the [square bracket] placeholders: your organization and your services content source’s name.
• The example maps each named finding to a named capability for tight control; the generic version has the agent pair the client’s issues with capabilities from your content source.
• The closing line is the slide’s quality bar; keep it.

You are writing the "Our Capabilities" content for a one-slide section of a [YOUR ORGANIZATION NAME] services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as [YOUR ORGANIZATION NAME] speaking to them: "we" is [YOUR ORGANIZATION NAME], "you" is the client.

Read the Pursuit documents, and use the '[SERVICES CONTENT SOURCE NAME]' content source for how we describe our capabilities.

Write exactly three short paragraphs, separated by blank lines, with no headings and no bullet points — one paragraph per issue you raised with us, in the same order you raised them:

Paragraph 1 — the capability that answers the first issue you raised, in one or two sentences tying it to your situation.

Paragraph 2 — the capability that answers the second issue you raised, in one or two sentences tying it to your situation.

Paragraph 3 — the capability that answers the third issue you raised, in one or two sentences tying it to your situation, including how we build your team's capability as we deliver.

200 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. Describe capabilities only in terms the '[SERVICES CONTENT SOURCE NAME]' content source supports; do not invent offerings, tools, or claims. Every paragraph must connect a capability to something specific you told us — this slide answers you, it does not recite a brochure.

The delivery framework from the content source, phased against the client’s own dates.

As used in the example template:

You are writing the "Our Approach & Timeline" content for a one-slide section of a Redmond Consulting services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as Redmond speaking to them: "we" is Redmond, "you" is the client.

Read the Pursuit documents, and use the About Redmond Consulting content source for how our delivery framework is described.

Write exactly three short paragraphs, separated by blank lines, with no headings and no bullet points:

Paragraph 1 — the diagnostic: a focused six-to-eight week diagnostic against your regulator's findings, what it covers, and what it produces for you, in two or three sentences.

Paragraph 2 — the remediation program: how delivery is structured after the diagnostic, with your people in the delivery seats and ours coaching and governing, so the capability stays with your team, in one or two sentences.

Paragraph 3 — the clock: how this phasing meets your stated milestones — the diagnostic landing in time for your board to endorse the plan, and your deadline to your regulator — using the specific dates you gave us, in one or two sentences.

200 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. Use only dates and milestones you stated to us; do not invent dates, and do not promise outcomes with your regulator. Name our delivery framework as the About Redmond Consulting content source names it.

Make it yours:

• Replace the [square bracket] placeholders: your organization, your about-us content source’s name, and your own first phase in paragraph 1.
• ‘Do not promise outcomes with your regulator’ is engagement risk control; swap it for whatever your organization must not commit to on a slide.

You are writing the "Our Approach & Timeline" content for a one-slide section of a [YOUR ORGANIZATION NAME] services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as [YOUR ORGANIZATION NAME] speaking to them: "we" is [YOUR ORGANIZATION NAME], "you" is the client.

Read the Pursuit documents, and use the '[ABOUT US CONTENT SOURCE NAME]' content source for how our delivery framework is described.

Write exactly three short paragraphs, separated by blank lines, with no headings and no bullet points:

Paragraph 1 — the first phase: [YOUR TYPICAL FIRST PHASE, e.g. a diagnostic] against the issues you described, what it covers, and what it produces for you, in two or three sentences.

Paragraph 2 — delivery: how delivery is structured after the first phase and how we work with your team, in one or two sentences.

Paragraph 3 — the clock: how this phasing meets your stated milestones and deadlines, using the specific dates you gave us, in one or two sentences.

200 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. Use only dates and milestones you stated to us; do not invent dates, and do not promise outcomes we cannot control. Name our delivery framework as the '[ABOUT US CONTENT SOURCE NAME]' content source names it.

Each paragraph pairs one differentiator with one thing the client explicitly asked for, so the slide answers requirements instead of reciting strengths.

As used in the example template:

You are writing the "Why Redmond Consulting" content for a one-slide section of a Redmond Consulting services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as Redmond speaking to them: "we" is Redmond, "you" is the client.

Read the Pursuit documents, and use the Differentiators content source for how Redmond describes its strengths.

Write exactly three short paragraphs, separated by blank lines, with no headings and no bullet points — each pairing one of our differentiators with one thing you explicitly asked us for:

Paragraph 1 — your requirement for a local, partner-led team, and how we meet it, in one or two sentences.

Paragraph 2 — your requirement that capability stays with your own team rather than leaving with the consultants, and how we work that way, in one or two sentences.

Paragraph 3 — your requirement for people credible in front of your board, and the experience and seniority we bring, in one or two sentences.

130 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. Draw differentiator language only from the Differentiators content source; do not invent claims, statistics, or client names. Each paragraph must answer your requirement directly, not state a generic strength.

Make it yours:

• Replace the [square bracket] placeholders: your organization and your differentiators content source’s name.
• The example writes the client’s three known requirements into the briefs; the generic version has the agent take them from the Pursuit documents instead.

You are writing the "Why [YOUR ORGANIZATION NAME]" content for a one-slide section of a [YOUR ORGANIZATION NAME] services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as [YOUR ORGANIZATION NAME] speaking to them: "we" is [YOUR ORGANIZATION NAME], "you" is the client.

Read the Pursuit documents, and use the '[DIFFERENTIATORS CONTENT SOURCE NAME]' content source for how we describe our strengths.

Write exactly three short paragraphs, separated by blank lines, with no headings and no bullet points — each pairing one of our differentiators with one thing you explicitly asked us for, taking your three most important stated requirements from the Pursuit documents, in the order you raised them:

Paragraph 1 — your first requirement, and how we meet it, in one or two sentences.

Paragraph 2 — your second requirement, and how we meet it, in one or two sentences.

Paragraph 3 — your third requirement, and how we meet it, in one or two sentences.

130 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. Draw differentiator language only from the '[DIFFERENTIATORS CONTENT SOURCE NAME]' content source; do not invent claims, statistics, or client names. Each paragraph must answer your requirement directly, not state a generic strength.

The closing slide: the agreed path and dates, framed as readiness, with contact details left to the template.

As used in the example template:

You are writing the "Proposed Next Steps" content for the closing slide of a Redmond Consulting services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as Redmond speaking to them: "we" is Redmond, "you" is the client.

Read the Pursuit documents for the agreed next steps and dates.

Write exactly two short paragraphs, separated by a blank line, with no headings and no bullet points:

Paragraph 1 — the immediate path: the executive presentation and your decision timing, with the specific dates and events you set out, in one or two sentences, framed as our readiness to meet them.

Paragraph 2 — getting started well: the materials you offered to share under NDA and how early access shortens the diagnostic, in one sentence framed as shared readiness rather than a request.

80 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. Use only dates, events, and commitments stated in the Pursuit documents; do not invent meetings or deadlines. Do not include contact details — the slide carries those separately.

Make it yours:

• Replace [YOUR ORGANIZATION NAME]; paragraph 2’s NDA materials are specific to this engagement, so the generic version covers anything the client offered ahead of kickoff.
• Keep the no-contact-details rule when your template carries them as fixed content, as this one does.

You are writing the "Proposed Next Steps" content for the closing slide of a [YOUR ORGANIZATION NAME] services pitch that will be presented directly to [CLIENT NAME Smart Field].

Voice: this text appears on a slide the client's executives will read. Address the client directly in the second person — "you", "your", "your team", "your board". Never refer to them as "the client", "they", "their", or "the firm", and never describe the call or the documents ("the client described", "on the call", "the transcript"). Write as [YOUR ORGANIZATION NAME] speaking to them: "we" is [YOUR ORGANIZATION NAME], "you" is the client.

Read the Pursuit documents for the agreed next steps and dates.

Write exactly two short paragraphs, separated by a blank line, with no headings and no bullet points:

Paragraph 1 — the immediate path: the next meeting and your decision timing, with the specific dates and events you set out, in one or two sentences, framed as our readiness to meet them.

Paragraph 2 — getting started well: anything you offered to share ahead of kickoff and how early access helps us start well, in one sentence framed as shared readiness rather than a request.

80 words maximum in total. Plain text only: no asterisks, no dashes, no bold, no numbered lists, no symbols at the start of any line. Use only dates, events, and commitments stated in the Pursuit documents; do not invent meetings or deadlines. Do not include contact details — the slide carries those separately.