# Tailored Client Deck > Tailored Client Deck - Skill: `ingridleiria/tailored-client-deck` (Agent Skill) - Install (CLI): `npx skillmds@latest add ingridleiria/tailored-client-deck` - Raw SKILL.md: https://api.skillmd.com/api/skills/ingridleiria/tailored-client-deck/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: ingridleiria (https://skillmd.com/u/ingridleiria) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/ingridleiria/tailored-client-deck --- # Tailored Client Deck A tailored deck is a standard deck rebuilt around one client. What usually arrives instead is the standard deck with a logo on the cover, and clients read it accurately within three slides: this is the deck they show everyone. The meeting then converts into "send us something in writing", which is the polite ending, and the momentum a live conversation was supposed to create is spent. The second failure is quieter and lands with the people who notice detail. A stretched logo, a client wordmark sitting in the presenter's position, a version retired in last year's rebrand, or the previous client's name surviving in a footer on slide nineteen. None of it changes the argument, and all of it tells a careful audience how much attention their account is getting. ## When to use this, and when not to Use it when a presentation is going to a named external audience and a baseline deck or narrative already exists: a sales or expansion meeting, a kickoff, a quarterly review, a renewal conversation, an executive briefing, a partnership pitch, or any co-branded material. Do not use it to build the argument from nothing after discovery. Where the raw material is discovery notes or interview transcripts from one client and the deck's job is to prove the problem was heard correctly, that is `discovery-to-proposal-deck`. Where the idea has no named buyer yet, or the audience is internal, that is `ideation-deck`. The document that asks the client to buy, with the price and the terms, is `proposal-writer`; this deck usually accompanies it and is a different artefact. Other adjacent cases. `pitch-deck` is for investors and `board-deck` for governance, both with different structures. `partnership-assessment` covers the case where the counterparty is a partner being evaluated rather than a client being sold to. The organisation's own brand system, rather than its application to one account, lives in a brand skill such as `breaktalk-brand`. ## What you need before starting **The baseline deck or narrative.** The thing being tailored. Missing: there is nothing to tailor, so either build the argument first with `discovery-to-proposal-deck`, or agree a narrative outline before any slide is made. **The audience by name and role, and who decides.** Missing: ask the person who set the meeting. Where they do not know, write the deck for the most senior likely attendee and open with a slide that asks who is in the room, which is better than guessing wrong silently. **What the client is trying to achieve this year, in their own words.** From their website, annual report, results call, job postings, or leadership interviews. Missing: use `external-insights` to gather and source it, or use connected research and enrichment tools where available. Where nothing can be found, say so on the slide and ask them to correct you rather than inventing a priority. **Their vocabulary.** How they name their customers, products, regions, and teams. Missing: pull it from any public document they have written. This is the cheapest tailoring available and the most noticed. **The history with them.** What has been discussed, promised, or delivered before, and by whom. Missing: ask internally before the meeting, because contradicting a colleague's earlier commitment in front of the client is expensive to repair. **Their logo files and brand rules, and any constraints.** Official files from their brand or press page, plus procurement rules, budget cycle, and competing vendors in play. Missing: request the file rather than taking a screenshot from a web page, and where only a low-resolution version exists, say so and ask, rather than shipping a blurred mark. ## The method 1. **Build the client context sheet first, on one page, and confirm it before touching slides.** Audience and decider, their stated goals in their words with sources, the specific problem this meeting addresses, what they already know about you, their vocabulary, and their constraints. Confirming it takes five minutes and prevents a day of tailoring built on a wrong assumption. 2. **Fix the one outcome the meeting is for.** A next meeting, a pilot agreed, a proposal invited, a renewal confirmed, an introduction to a colleague. Rule: one outcome. A deck built for two outcomes achieves neither, because the closing slide has to ask for both. 3. **Run every inherited slide through one question: what does this mean for this client?** Three answers only. Rewrite, where the point holds but must be restated with their numbers, their example, their words. Keep, where the slide is general and still lands, which is rare and is usually credentials or method. Cut, where it does not bear on their decision. Rule: cut it even when it is the best-looking slide in the deck, and especially then. 4. **Add the three slides a standard deck never has.** Their situation as the opening, stated as a fact about them with a source. A slide mapping what you do onto the priorities they have publicly stated. A concrete first step sized to their constraints, their calendar, and their approval process. 5. **Sequence for a named audience.** Their situation, what is at stake in their numbers, the approach in their vocabulary, evidence from comparable clients, what it would look like for them, investment and terms plainly, and one next step with a date. Rule: nothing about your organisation appears before the situation slide. 6. **Sweep for vocabulary and for internal shorthand.** Replace every internal method name, product codename, and abbreviation with either their term or plain language. Read the deck aloud once; internal shorthand is audible in a way it is not visible. 7. **Apply branding correctly, and decide whose brand leads.** The presenter's brand governs the template. The client's logo appears on the cover and, if wanted, small in a "prepared for" position on section dividers, never in the presenter's logo position and never resized to dominate. Use their official files, preserve aspect ratio, never recolour or add effects, respect clear space of at least the logo's height on all sides, and pick the variant (full colour, mono, reversed) that suits the background. For a genuinely co-branded deck, both marks sit on the cover at equal visual weight, presenter left and client right, separated by clear space, with interior slides in the presenter's system. 8. **Rebuild the charts to the same standard as the argument.** One message per chart, stated in the chart title. Direct labels rather than a legend floating inside the plot area; where a legend is needed it sits outside it. Series separated by marker shape and dash pattern, and by texture in bars, rather than by colour alone, so the chart survives a bad projector or a monochrome print. The accent colour appears only on the series the slide is about. 9. **Put the sources in the speaker notes, with the talk track.** Every client fact on a slide gets its source and date in the notes. This is what allows anyone to defend the slide when the client says "where did you get that", and it is what makes the deck reusable next quarter. 10. **Run the tailoring test before delivery.** Slide by slide, ask whether it could be sent to a different client unchanged. Rule: more than three passes means the deck is not tailored, and the fix is to rewrite the offenders rather than to accept the count. Then check the client's name spelling and capitalisation everywhere, including footers, file name, and chart labels, and search the file for the previous client's name. ## Worked example **Situation.** Larkfield Learning, a training firm of thirty-five people, had a two-year relationship with Calder Retail Group, 210 stores, delivering induction training for store staff. The account director wanted to expand into supervisor development and had a ninety-minute slot with Calder's people director and two of her team. The baseline deck was twenty-four slides and had last been rebuilt for a different sector. **Task.** A deck that would get supervisor development invited as a proposal, not merely discussed, using facts Calder had already stated publicly. **Action.** The context sheet came first. Calder's half-year results call, six weeks old, named three priorities: reducing store manager turnover, improving stock availability, and opening eighteen stores in the year. Their own vocabulary mattered: they say colleagues rather than staff, and stores rather than sites, and the baseline deck used the wrong word in eleven places. Of the twenty-four inherited slides, twelve were cut, nine rewritten, three kept. The cuts included a slide on the firm's five-stage methodology that had taken a day to build the previous year. It went because it answered a question Calder had not asked; it was replaced by a single slide mapping supervisor development onto the manager turnover priority, using Calder's own stated figure. The wrong turn worth recording: the first version pulled Calder's logo from a web search. It was the pre-rebrand wordmark, retired eight months earlier, which their press page made obvious within a minute. Nobody in the room would have said anything, and everybody would have noticed. The correct files came from the press page, and the cover used the reversed mono variant because the cover was dark. Three slides were added. The opening stated their turnover figure and its source and date. The second mapped the offer to the three stated priorities, honestly showing that it addressed one of them fully and one partly. The third was a first step sized to their constraints: one region, twelve supervisors, eight weeks, ending before the peak trading period their results call had described as starting in October. The tailoring test caught two survivors: a generic slide on learning retention and a case study from a manufacturing client. The first was cut, the second rewritten around a retail client with the name withheld and the figures kept. **Result.** Fifteen slides. Calder's people director asked for a proposal in the meeting and named a budget range, which had not been expected before a second conversation. The proposal followed the next week using `proposal-writer`, with the deliverables and the first step carried over unchanged so the two documents agreed. The account director's view was that the priority-mapping slide, which took forty minutes to build, did more than the twelve slides that were cut. ### A second scenario, where it goes differently The same firm built a co-branded deck with a software partner for a joint webinar to a shared audience of prospects. The rules invert. Neither brand leads, so the cover carries both marks at equal weight with clear space between them, and interior sections are visually owned by whichever organisation is presenting them rather than kept in one house style. The tailoring test does not apply, because the audience is a segment rather than a named account, so the specificity has to come from the segment's shared situation instead. And approval changes: joint material needs sign-off from both brand owners, which takes days rather than hours, so the deck is drafted a week earlier than a client deck of the same size. What stayed identical was the logo discipline, the chart rules, and the sourcing of every fact in the speaker notes. ## Output The client context sheet, one page, confirmed before slide work starts: ``` CLIENT CONTEXT SHEET Client [name, spelled as they write it] Meeting [date, length, format] Attendees [name, role] per line; Decider: [name] Their stated goals [goal, source, date] per line This meeting's issue [the specific problem or opportunity] Prior history [what has been discussed, promised, delivered] Their vocabulary [their words for customers, products, regions, teams] Constraints [budget cycle, procurement, competing vendors, timing] Meeting outcome [the one thing this meeting is for] ``` The deck spine for a named client: | # | Slide | Title written as | Source needed | | 1 | Their situation | A fact about them | source and date in notes | | 2 | What is at stake | Their number, their words | source and date in notes | | 3 | The approach | Mapped to their stated priorities | none | | 4 | Evidence it works | Comparable client, results in figures | case reference in notes | | 5 | What it looks like for them | Timeline against their calendar, named team | none | | 6 | Investment and terms | Plainly, one figure | matches the proposal exactly | | 7 | Next step | One action, one date, one owner | none | Slide-by-slide disposition, kept as a working record: slide number, inherited or new, rewrite, keep, or cut, and the reason. ## Failure modes **Logo on, content untouched.** Recognise it with the tailoring test: if more than three slides could go to another client unchanged, no tailoring happened. Rewrite the offenders rather than adjusting the threshold. **The client's logo mishandled.** Stretched, recoloured, placed in the presenter's position, or a retired variant taken from a web search. Recognise it by checking their own press or brand page before use, and never accept a low-resolution file. **Internal shorthand left in.** Method names, product codenames, internal abbreviations. Recognise it by reading the deck aloud; the shorthand is audible where it is not visible. **Stale client facts.** A priority quoted from a two-year-old annual report, or a quote from an executive who has since left. Recognise it by checking the date on every sourced fact, and treat anything older than two quarters as needing confirmation. **Beautiful slides kept for their own sake.** Recognise it when the reason a slide survives is the effort that went into it. That is a sunk cost, and the client cannot see it. **Sources missing from the speaker notes.** Recognise it by picking any client fact at random and asking where it came from. If the answer is not in the notes, the deck cannot be defended by anyone but its author. **The previous client's name in a footer.** Fatal, common, and preventable by one search of the file before sending, including chart labels and the file name itself. ## Edge cases **No baseline deck exists.** This skill has nothing to rebuild. Build the argument first with `discovery-to-proposal-deck` where discovery has happened, or with `ideation-deck` where the concept is still an idea, then tailor. **Their brand guidelines forbid third-party use of their logo.** Common in regulated sectors and with large brands. Use their name in text only, on the cover and the "prepared for" line, and drop the mark. Check before the meeting, not after. **The client competes with another client whose case you want to show.** Anonymise by sector and size, keep the figures, and say plainly that the name is withheld under confidentiality. Clients read that as evidence you will protect them too. **The deck will be forwarded without you.** Speaker notes will not travel. Move the essential context onto the slides, add a short written summary as the second slide, and accept a slightly denser deck, or produce a separate leave-behind version. **Procurement or legal are in the room.** Add the terms, security, and data handling material as slides rather than as an appendix, since those attendees judge the meeting on whether their questions were anticipated. **The facts come from a public company's results call.** Quote precisely, cite the call and its date, and avoid inferring anything the transcript does not say. Clients recognise their own words and notice when they are stretched. ## Quality bar - No more than three slides could be sent to a different client unchanged. - The client's situation appears before anything about the presenter's organisation. - Every client fact on a slide carries its source and date in the speaker notes. - The client's name is spelled and capitalised as they write it, in every slide, footer, chart label, and the file name. - Logos are official files, correct variant, correct aspect ratio, with clear space respected. - The deck asks for one outcome, with one action, one date, and one owner. - Charts carry their message in the title and separate series by shape and pattern, not colour alone. - No previous client's name survives anywhere in the file. ## Adapting this to your context The three-slide tailoring threshold, the two-quarter staleness rule and the assumption that a client publishes its priorities come from business-to-business services selling into listed or large private companies. - **The three-slide test.** Calibrated for a fifteen to twenty-five slide deck rebuilt for one account. On a seven-slide meeting deck the threshold is one. The proportion matters, not the number. - **Public sources for the client's stated goals.** Private companies, family businesses, public bodies and charities publish different things: filed accounts, strategic plans, inspection reports, tender documents, annual reviews. Find their equivalent rather than inferring a priority from the sector. - **Two quarters as the staleness limit.** Where the client reports annually, or the fact is a multi-year strategy commitment, a year-old source is still current and the date on the slide does the work. - **Speaker notes carrying the sources.** This assumes you present the deck. Where it will be forwarded, and most are, move the essential context onto the slides or build a separate leave-behind. - **What not to change.** The client's situation appears before anything about your organisation, and every client fact on a slide carries its source and date somewhere in the file. ## Related skills `external-insights` gathers and sources the client facts that make the context sheet credible, and `customer-interview-synthesis` supplies the client signals behind the situation slide. `discovery-to-proposal-deck` builds the argument this skill rebuilds when no baseline deck exists, and `ideation-deck` covers a concept with no named buyer. `proposal-writer` carries the commercial ask that usually follows this meeting, and the deliverables, price and terms must match it exactly; `sow-and-scope` follows once the client agrees. A brand skill such as `breaktalk-brand` supplies the presenter's visual system that this deck applies. `executive-briefing` prepares the person presenting, `principal-simulator` rehearses the client's likely reaction, and `partnership-assessment` covers the case where the counterparty is a partner rather than a client.