Every commercial real estate adviser faces the same tension at pitch time: the most persuasive evidence you own — real transactions, real clients, real outcomes — is precisely the information you are most obligated to protect. Learning how to prepare pitch case examples when client confidentiality applies is not a workaround or a compromise; it is a core professional discipline that separates advisers who win new mandates from those who rely on vague reputation alone.
Why Confidentiality and Proof Are Both Non-Negotiable
Prospective clients want evidence. They are about to hand over a lease negotiation, a portfolio disposal, or a site selection assignment that could shape their business for a decade. They need to believe that your team has done this before, done it well, and learned something from it.
At the same time, the clients who generated that evidence trusted you with commercially sensitive information. Lease terms, acquisition prices, occupier identity, and negotiating strategy are competitively valuable. Disclosing any of them without permission — even in a pitch where the audience will never meet your former client — is a breach of professional duty.
The tension is real, but it is resolvable. The resolution is not to choose between proof and protection; it is to build case examples that carry genuine evidentiary weight while removing or transforming every identifying detail. That is a craft skill, and it can be learned systematically.
The Architecture of an Anonymous Case Example
A well-constructed anonymous case example has three structural layers. The first is the problem layer, which describes the business challenge in enough operational specificity that a prospect recognises it as real. The second is the process layer, which shows what your team actually did — the method, the sequence of steps, the trade-offs evaluated. The third is the outcome layer, which describes the result in terms that are meaningful without being identifiable.
Most advisers get the outcome layer right and neglect the problem and process layers. That is backwards. A prospect is primarily evaluating whether you understand problems like theirs, and whether your process is rigorous. The outcome layer confirms that the process works; it is not a substitute for showing the work.
The problem layer needs to describe the client's situation in category terms: a multinational technology occupier consolidating regional offices, a logistics operator expanding into a new distribution corridor, a fund manager facing a concentration of lease expirations within a twelve-month window. These descriptions are specific enough to be credible and vague enough to protect identity.
The process layer is where most advisers underinvest. This is where you document the steps your team took — how you scoped the brief, how you scored options, how you structured the financial comparison, how you managed the negotiation sequence. A well-described process is more persuasive than any headline metric because it lets the prospect mentally walk through what working with you would feel like.
Identifying What Must Be Stripped and What Can Stay
Before you begin writing, you need a clear taxonomy of sensitive information. Identifying details fall into several categories: client name and corporate identity; specific property addresses; transaction price, rent, or other financial terms; timing details that could allow reverse identification; and negotiating positions or counterparty information.
Some of these categories are absolute. Client name, counterparty name, and specific financial terms must always be removed or transformed. Others are contextual. A property address in a city with deep market activity can often be replaced with a submarket descriptor without losing the example's value. An address in a thinly traded submarket may be identifying even without the name.
Timing information is frequently overlooked as an identification risk. If you describe a lease restructuring that concluded during a narrow window in which only a handful of transactions occurred in the relevant submarket, a sophisticated reader may be able to deduce the client. The standard practice is to describe timing in relative rather than absolute terms: "over an eighteen-month engagement" rather than referencing a specific quarter or year.
Negotiating history and counterparty intelligence are perhaps the most sensitive categories. Even an anonymised description of how a landlord reacted to a particular concession request can damage a relationship if that landlord encounters your case study. The process layer should describe your team's methodology, not the counterparty's behaviour.
Transformation Techniques That Preserve Evidentiary Weight
Stripping information is only the first step. The more important skill is transforming specific details into generalised descriptions that remain credible. This is different from vagueness; vagueness loses the reader's trust, while transformation maintains the operational texture of the example.
One proven technique is category substitution. Instead of naming an industry, describe the operational characteristics that drove the real estate requirement. A financial services firm becomes "an occupier whose client-facing operations required a specific floor plate configuration and proximity to a regulated exchange." A pharmaceutical company becomes "a life sciences occupier managing containment and ventilation specifications across multiple floors." The description is accurate but not identifying.
A second technique is metric rescaling. When exact figures must be removed, consider whether a rescaled version — where all financial figures are adjusted by a consistent multiplier — preserves the analytical relationships without disclosing the actual amounts. If your analysis showed that a purchase option delivered superior net present value over a ten-year horizon compared with a renewal, you can describe that relationship and the discount rate framework you used without stating the actual lease NPV figures. Label these as hypothetical examples that illustrate your methodology rather than actual client outcomes.
A third technique is composite construction, where elements from two or more real engagements are combined into a single illustrative case. This is a legitimate method when disclosed transparently — you might describe the example as "a composite scenario reflecting the patterns we see in multi-site portfolio consolidations." Composites must be constructed carefully so they remain internally consistent and do not misrepresent what any individual engagement actually involved.
Building the Problem Layer With Operational Specificity
The problem layer must pass a credibility test with an experienced prospect. If it reads like a marketing brochure — "our client faced a complex real estate challenge" — it will register as filler. If it reads like a practitioner describing a real situation, it builds confidence.
Achieving specificity without identification requires focusing on structural features of the problem: the lease structure, the market conditions, the occupier's operational constraints, and the stakeholder dynamics. A logistics operator does not simply "need more space"; the problem might be described as a situation where remaining lease term on a primary distribution facility was insufficient to support a capital investment in racking systems, while the alternative sites available in the submarket carried occupancy costs materially higher than the incumbent position.
Stakeholder dynamics are often the most revealing aspect of a real problem, and they are also the most useful to describe because they resonate with prospects who face similar internal challenges. A corporate real estate mandate where the finance team and the operations team have conflicting criteria is a recognisable situation. Describing how your team structured the evaluation to surface and resolve that conflict demonstrates process sophistication without disclosing anything proprietary.
It is legitimate to describe market conditions at a submarket level if the transaction occurred in a liquid market. Vacancy rates, construction pipeline, and landlord incentive levels in a major gateway city at a given period in the cycle are matters of public record. These details ground the case example in a real market environment without pointing to a specific client.
Structuring the Process Layer for Maximum Persuasion
The process layer is your opportunity to differentiate your approach from every other adviser pitching the same mandate. It answers the question that prospects rarely ask directly but are always asking internally: how exactly will you do this?
For a tenant-rep or occupier advisory engagement, the process layer should describe how the brief was defined and refined, how the market was surveyed, how options were scored against weighted criteria, and how the financial comparison was structured. For a capital markets or investment assignment, it should describe how the asset was positioned, how buyer or investor groups were identified and sequenced, and how competing proposals were managed.
The scoring methodology deserves particular attention. A case example that describes how your team weighted criteria — giving, for instance, higher priority to operational continuity than to occupancy cost reduction because the client's business model depended on workforce retention — demonstrates strategic thinking. It shows that your process begins with the client's business objectives, not the market.
Financial comparison methodology is another high-value component of the process layer. Describing how you compared lease net present value against purchase cash flows, or how you modelled effective rent across proposals with different incentive structures, signals analytical rigour. You do not need actual figures; the structure of the analysis is what the prospect is evaluating. Lease NPV, effective rent, and total occupancy cost are the standard frameworks, and describing them by name establishes credibility.
Document management and decision governance are often overlooked in pitch case examples but are increasingly important to sophisticated occupiers and institutional clients. Describing how you organised proposals, letters of intent, and diligence materials — and how decision approvals were tracked through the engagement — demonstrates operational maturity.
Structuring the Outcome Layer Without Disclosing Terms
The outcome layer is where advisers most commonly run into confidentiality problems, usually because they reach for specific figures that are identifiable. The goal is to describe outcomes in terms that are meaningful to a prospect without disclosing exact terms.
Relative comparisons are more defensible than absolute figures. Describing that the transaction delivered a materially lower total occupancy cost than the client's incumbent position — expressed as a range, or as an ordering relationship without specific amounts — communicates the result without disclosing the terms. Describing that a lease restructuring extended weighted average unexpired lease term by a material margin communicates portfolio management success without specifying the duration.
Qualitative outcomes are often more persuasive than financial metrics anyway. Describing how the engagement resolved a board-level disagreement about occupancy strategy, or how it enabled an operational change that the client had been unable to implement for three years, speaks directly to the business impact of good real estate advice. These outcomes are rarely identifiable because they describe internal dynamics that are invisible to the market.
Time-to-completion and process efficiency outcomes can be described in relative terms: "concluded within the client's budget timeline" or "shortlisted from an initial market survey of more than forty options to a final three within sixty days." These convey pace and organisation without revealing transaction-specific information. If you use illustrative numbers like this, make clear they are representative of your process rather than guaranteed timelines.
Managing Client Permission and Tiered Disclosure
An anonymous case example is not the only tool available. For some clients and some engagements, you may be able to obtain permission to disclose more. Building a systematic approach to client permission — requesting it at engagement close, maintaining records of what was authorised, and tiering your case library accordingly — multiplies your options at pitch time.
A tiered case library has three levels. The first level contains fully anonymous cases that can be used without restriction. The second level contains cases where the client has authorised disclosure of their industry and transaction type, but not their name. The third level contains cases where the client has authorised named reference, either publicly or for specific use in a defined pitch.
Requesting permission at engagement close, when the relationship is at its strongest and the client's satisfaction is highest, is more effective than approaching a client months later when the relationship has cooled. A simple, honest request — explaining that you would value the ability to reference the engagement in future business development, and describing exactly what level of disclosure you are seeking — is usually well received.
Even at the highest tier, written authorisation is essential. Verbal agreements about disclosure scope are routinely misunderstood. A brief written record of what was agreed — shared with the client and kept on file — protects both parties and prevents the awkward situation of a client who does not recognise the description of their own transaction in a pitch document.
Integrating Case Examples Into the Pitch Narrative
A collection of well-constructed case examples is not, by itself, a pitch. The examples need to be integrated into a narrative that connects your team's track record to the specific challenge the prospect is facing. This is where many advisers lose the persuasion they worked to build.
The integration should be explicit: "We have navigated a similar situation, and here is what we learned from it." The case example then functions as evidence for a specific claim about your capabilities or approach. If your pitch argues that you bring a distinctive approach to multi-site portfolio consolidation, the case example should demonstrate that specific capability, not just illustrate that you have done real estate transactions.
Sequencing matters. Opening a pitch with a case example before establishing context risks confusing the prospect. Closing with a case example after the prospect has articulated their needs and you have proposed your approach works better — the example arrives as confirmation rather than preamble. In a written pitch document, case examples usually belong in a capability or experience section that sits after the strategic proposal.
The language used to frame the case example signals professionalism. Describing it as "an illustrative example reflecting the type of engagement we manage regularly" is accurate and sets appropriate expectations. Describing it as an exact model for the prospect's situation is a commitment you cannot and should not make.
Keeping the Source Material Organised and Audit-Ready
A pitch case library is only useful if it is maintained. The underlying records — the original engagement documentation, the permission authorisations, the transformation decisions made during anonymisation — need to be organised so that any case example can be traced back to its source and its confidentiality treatment can be defended.
For teams running multiple concurrent mandates across different client categories, this quickly becomes a document management challenge. Advisers who document their anonymisation decisions at the time of construction — noting which details were stripped, which were transformed and how, and which permissions were obtained — are protected if a client later questions how their transaction was handled.
A regular review cycle, ideally annual, ensures that case examples remain accurate. Market conditions change, and an example that described a supply-constrained submarket five years ago may now misrepresent the current environment. Examples should also be reviewed for continued accuracy against your team's current capabilities — if the process described in a case example no longer reflects how your team operates, the example is misleading.
Applying the Methodology to Different Deal Types
The core methodology applies across deal types, but each type has specific considerations. Tenant representation mandates are usually the most straightforward to anonymise because the client's identity is separated from the property by the adviser's role. Capital markets mandates require more care because the asset is often publicly marketed and the transaction may be a matter of public record even if the specific terms are not.
For portfolio strategy engagements — where the work involves lease analysis and critical-date management across a large estate — the case example needs to describe the analytical framework without disclosing the portfolio's composition. Describing the methodology used to prioritise lease events by financial exposure and strategic importance is specific and credible without revealing which leases or which properties were involved.
Site selection engagements offer an opportunity to describe the scoring framework in detail. How criteria were weighted, how markets were ranked, how shortlists were built and refined — these process steps are demonstrably proprietary to your team's methodology and can be described in full without disclosing where the client ultimately chose to locate.
Investment and acquisition mandates often involve confidentiality agreements with counterparties as well as obligations to the client. In these cases, the anonymisation discipline must be more rigorous, and composite construction is often the most appropriate approach.
The Role of Financial Modelling in Case Example Construction
Financial rigour is one of the most persuasive elements of a pitch case example, and it is also one of the most dangerous from a confidentiality perspective. The solution is to describe the modelling framework in detail while presenting only illustrative, clearly labelled hypothetical figures.
Describing a lease NPV analysis in structural terms — the discount rate approach, the treatment of incentive periods, the comparison of gross and net effective rent across proposals — demonstrates analytical capability without disclosing actual numbers. If you present a hypothetical example, label it explicitly: "To illustrate the framework, consider a hypothetical scenario where two proposals offer comparable headline rent but diverge significantly in incentive structure." A prospect who understands real estate will follow the logic and credit your team for the method.
Referencing the structure of this kind of analysis in a pitch case example — describing how assumptions were documented and stress-tested alongside the financial comparison — is a form of process disclosure that is both credible and confidentiality-safe.
Effective rent, lease net present value, and total occupancy cost are the three financial frameworks most commonly relevant in occupier advisory case examples. Capital markets examples typically involve investment cash flows, internal rate of return frameworks, and pricing sensitivity analysis. In either case, the framework is the persuasive content; the specific numbers from a real transaction are not needed and should not be used.
Reviewing Draft Case Examples Before Use
Every case example should pass through a structured review before it enters the pitch library or appears in a prospect document. The review has two dimensions: confidentiality compliance and evidentiary quality.
The confidentiality review should ask whether a knowledgeable industry participant — someone with direct knowledge of the market and the period — could identify the client, the property, or the counterparty from the description alone. This is a stricter standard than asking whether the name is present. If the answer is yes, the example needs further transformation before use.
The evidentiary quality review asks whether the example actually demonstrates the capability it is intended to support. A case example that describes a complex situation and a successful outcome but does not explain how your team achieved that outcome fails the evidentiary test. It tells the prospect that you were present for a good result without showing that your method caused it.
A second reader — ideally someone not involved in the original engagement — is the most reliable way to identify gaps in both dimensions. They bring no background knowledge to the confidentiality review, so they can test it honestly. And they can identify places where the process description assumes knowledge that the prospect will not have.
Applying These Principles Across Your Pitch Library
Building a pitch case library that is both confidentiality-safe and genuinely persuasive is a long-term investment. It requires consistent discipline at every engagement close — capturing the right details, requesting the right permissions, making the right transformation decisions — rather than a sprint of construction before each pitch.
Teams that build this discipline into their operating rhythm find that pitch preparation becomes faster and more confident over time. The case examples are ready; the question becomes only which ones are most relevant to the prospect's situation. That shift — from scrambling to selecting — is the operational benefit of treating pitch case example preparation as a methodology rather than an improvisation.
The methodology is not complicated. Strip what must be stripped. Transform what can be transformed. Describe the problem with operational specificity. Show the process in full. Report outcomes in terms that are meaningful without being identifying. Review every draft against a strict confidentiality standard before use. Maintain the library with the same discipline you bring to any client engagement. These steps, applied consistently, produce a case library that is both professionally sound and commercially powerful.
The source material is organised, the key decisions are documented, and the transformation decisions do not need to be reconstructed from memory.
That operational connectivity also supports the tiered permission model described earlier.
The goal, ultimately, is a pitch process that is both faster and more defensible.
About Advantai
Advantai is a commercial real estate intelligence and operations platform operated by ADVANTAGE AI LLC, a Delaware limited liability company. It connects client relationships, property research, documents and financial decisions in one workspace for commercial real estate teams — advisers and brokerage teams, occupier and facility teams, and portfolio teams. The platform covers CRM and origination, requirements and site selection, Property X-Ray (an interactive 3D building workspace), financial modeling and comparison, document intelligence, transactions and diligence, client collaboration, and portfolio strategy with critical dates. The optional Super Agent upgrade adds specialist, source-backed research and automated scenario analysis.
Get Started with Advantai
Ready to see your next move clearly? Go to advantaico.com, click Request a demo and tell us about your next project. Prefer to start with a single project? Visit advantaico.com/getting-started to plan your first one.