Building a Pitchbook

A typical pitchbook follows a recognizable narrative arc: an introduction establishing the bank's credentials and the situation at hand, a market or industry overview setting context, a discussion of strategic alternatives available to the client, a detailed valuation section, and a recommendation or next steps, each section building the case for a specific conclusion rather than presenting a neutral, disconnected series of facts.

Understanding this arc is what lets an analyst build individual pages that actually serve the deck's overall argument, rather than producing technically correct but disconnected slides that don't clearly support the narrative the senior bankers are trying to tell the client.

A weak deck presents information (here's the market, here's the valuation, here's the company) without connecting the pieces into an argument; a strong deck uses each section to build toward a clear conclusion, with transitions and framing that make the logical thread visible, why the market context matters for the client's specific situation, why the valuation supports the specific strategic recommendation being made.

This is the same underlying skill as the 'deck narrative, not listing' professional-craft lesson, applied specifically to the pitchbook's overall structure rather than an individual page, every page should visibly serve the deck's larger argument, and an analyst who understands the intended narrative arc produces noticeably better individual pages than one building each slide in isolation.

The standard arc flexes based on context: a sell-side pitch for a company actively considering a sale emphasizes valuation and buyer universe heavily; a defense-oriented pitch responding to an unsolicited approach emphasizes strategic alternatives and standalone value; a routine relationship-maintenance deck (no active transaction) might emphasize market conditions and ideas rather than a specific recommendation.

Recognizing which type of pitch is being built, and adjusting emphasis accordingly, rather than mechanically filling in the same template regardless of context, is a judgment skill that develops with exposure to multiple real pitches, and it's worth asking a staffer directly, early in a new deck, what the intended emphasis and takeaway should be before building out the full structure.

A 'football field' is the standard summary valuation chart showing the value range produced by each methodology (comps, precedents, DCF, sometimes 52-week trading range or analyst price targets) as horizontal bars stacked or aligned on a common axis, letting a reader see at a glance where the methods overlap and where the current or proposed price falls relative to that range. Building one cleanly in Excel or PowerPoint, with each bar accurately reflecting its underlying analysis and clear labeling of what each range represents, is one of the most common individual pages a junior analyst builds.

The chart should be immediately legible without requiring the reader to consult the underlying detail pages, clear axis labels, a visible marker for the current share price or proposed offer price, and a range that's been sanity-checked against the individual analyses feeding it.

A company profile page summarizes a business at a glance for a reader unfamiliar with it: business description, key financial metrics and recent trends, ownership structure, and often a brief SWOT-style summary of strengths and considerations, typically one of the first pages in a deck, setting context before the deeper valuation analysis. Building a good one requires synthesizing information from multiple sources (filings, data platforms, management materials) into a clean, accurate, appropriately concise summary, not simply reproducing a company's own investor-relations description verbatim.

Because this page is often a reader's first impression of both the target company and the deck's overall quality, formatting precision and clean sourcing matter as much here as on any of the more analytically complex pages later in the deck.

Behind the summary football field sit detailed backup pages for each methodology, a full comps table, a precedent transactions table, a DCF output page with sensitivity tables, that a sophisticated reader or a challenging question in the room might need to reference directly. These pages need to tie out exactly to the summary figures shown on the football field; any discrepancy between a summary chart and its own backup page is an immediate, visible credibility problem if caught in a client meeting.

Building these pages accurately and keeping them synced with the summary page as numbers get updated throughout a live deal is exactly the kind of detail-oriented, easy-to-get-wrong work that separates analysts who are trusted with valuation pages from those who are still being closely double-checked.

In banking, formatting precision is read as a direct proxy for analytical rigor: a deck with inconsistent fonts, misaligned numbers, or sloppy spacing signals, fairly or not, that the underlying analysis might be similarly careless, since the same attention to detail that catches a formatting inconsistency is assumed to be what catches an analytical error. This is why formatting standards in banking are enforced far more strictly than in most other professional contexts, and why a technically correct page with poor formatting is still considered unfinished work.

Understanding this logic, not just following the rules mechanically, helps an analyst prioritize correctly under time pressure, since formatting isn't a final cosmetic step to skip when short on time; it's part of what makes the analysis itself credible to the reader.

Every bank (and often every group within a bank) has an established house style, specific fonts, color palettes, chart formats, page layouts, and footnote conventions, codified in a template deck and reinforced through repeated correction during an analyst's first months. Learning this house style precisely, rather than applying generic 'good design' instincts, is the actual, specific skill being built: a beautifully designed page that doesn't match house style is still considered wrong in this context.

The fastest way to learn it is studying recent, well-regarded decks from the same group closely, noting exact color codes, font sizes, and spacing conventions, rather than guessing, since house style is rarely written down comprehensively and is mostly absorbed by example and correction.

Before any page is considered done: fonts and sizes consistent throughout, numbers aligned and formatted consistently (decimal places, thousands separators, parentheses for negatives per house convention), consistent color use for data types (per the black/blue/green input convention, extended visually into charts and tables), objects aligned to a visible grid rather than eyeballed, and every data point sourced with a footnote. A quick zoom-out view of the full page, checked purely for visual alignment and consistency before reading the content in detail, catches many formatting issues faster than a close read does.

Building this checklist into habit, running through it on every page before considering it finished, rather than only when a VP flags an issue, is what turns formatting from a source of repeated correction into a non-issue, freeing up review time to focus on the substance of the analysis instead.