Author: admin

Some of the best work we do happens in rooms where the stakes are high and the internal team cannot ask the hard questions without creating friction. But we can—we are your strategic advantage. Not because we are external to the organization, but because we are embedded enough to understand what matters and confident enough to say it. 

That is what embedded strategy looks like in practice. Not a status update. Not a standing check-in. A partner who elbow-deep in the work with you, tracking the pipeline, watching the horizon, and advising on which opportunities are worth your best effort. 

What that work looks like in practice 

It can mean running a pursuit workshop before a major RFP, developing the win themes, reviewing competitive positioning, or presenting market research that influences how the organization sees its own opportunity. It can mean sitting in a strategy session and asking the question the room has been avoiding or has not thought to ask. It can mean showing up after a pursuit is lost and helping the team have an effective debrief, prepare for the next client conversation, and walk into the client interview with confidence. 

What we call it 

Advisor. Strategic partner. The language that feels most honest describes what we do and how we work: We embed, do the work alongside the team, and build toward the moment they can carry it forward without us. Embed, Solve, Advise, Step back. 

If you are looking for someone to help your organization grow, win better work, and show up more strategically, this is how we engage.

We use AI. We use it for research, for first drafts, for synthesizing large amounts of information quickly. We are not here to argue against it. 

What we want to be honest about is what it cannot do, because that gap is where the real work lives, and it is a gap that is not closing as fast as the word on the street around AI suggests. 

What using AI well looks like 

We fed a lead’s corporate website, annual reports, and growth strategies into a chat, then asked where the intersections were with what we offer. What would have taken hours of manual research came back in minutes. That is AI doing what it is designed to do well: pulling from a large volume of information and synthesizing patterns. 

But the reason that output was useful is that we knew enough about our own capabilities, and about what a credible intersection looks like to evaluate what came back. We were not copy-pasting and sending. We were using the output as a starting point for our own judgment. 

That is the distinction. AI is a capable research assistant and a strong first draft generator. It is not a strategist. Knowing how to ask the right questions, push back on the outputs, verify sources, and evaluate what is useful requires the expertise that the AI is drawing upon. The tool is only as good as the person directing it. 

What AI consistently cannot do 

It cannot read the room, by identifying micro-expressions and tone shifts in a workshop informing that a conversation needs to change direction. It cannot know that a client prefers to meet over coffee and will give you more in an informal setting than in a formal presentation. It cannot pick up on the political context in an organization, the history between two people in the room, or the thing that is not being said but is shaping every response. 

It cannot decide what to cut from a proposal when you are three pages over the limit and everything feels essential. It cannot make the judgment call about which win theme will resonate with a specific evaluator based on what is known about their priorities. It cannot run an interview, facilitate a workshop or strategy session, or build the trust that turns a client relationship into a long-term partnership. 

These are not soft things. They are the core of what makes strategy work. 

Where we recommend leaning in 

• Research and synthesis, where the volume of information is large and the question is clear 
• First drafts, where speed matters and the human review is thorough  
• Compliance checking on proposals, where the task is systematic and the output can be verified 
• Identifying gaps in a document against a checklist 
• Tasks that are structured, specific, and where the output will be evaluated by someone who knows what good looks like 

Where we counsel caution

• Any output that goes to a client without a thorough human review 
• Any strategic recommendation generated without the context that only comes from being in the engagement 
• Any use of AI that skips the step of asking: do I know enough about this topic to recognize when the output is wrong? 

That last question is the most important one. AI produces confident, well-formatted, plausible-sounding content on topics it does not fully understand. The only protection against that is expertise. You cannot outsource the expertise to the tool. 

We use AI as an assistant. It saves time. It makes our work faster. It is not a replacement for the judgment that makes the work worth doing.

Most Business Development teams spend more time producing a proposal than they spend developing the strategy behind it. That imbalance is where most losses occur. 

A pursuit workshop flips that ratio. It is a structured session, run well before the RFP drops, and designed to build your capture strategy when you still have time to act. Done well, it is one of the highest-return investments a BD team can make. 

Here is what it is, when to run it, and how to make it work. 

What a pursuit workshop is 

It is not a proposal kickoff meeting or planning session, those come later. It is a deliberate conversation about the opportunity, the client, and your organization’s ability to position before the formal procurement process begins. 

The goal is to surface what you know, name what you do not, build a strategy around both, and obtain  clarity around these questions: Why this opportunity? Why us? Why now? Why not someone else? 

If your team cannot answer those questions well in advance of the RFP, the proposal is going to struggle to answer them under deadline. 

When to run it 

The earlier the better. Ideally, six to 12 months or more before a major procurement. That window gives you room to act on what you learn build relationships you are missing, address gaps in your qualifications, identify the right teaming partner, and position your team with the client before the formal evaluation begins. 

For smaller or faster-moving opportunities, even two to four weeks of structured pre-positioning changes what goes into a submission. The discipline of the conversation is what matters, not the length. 

Who should be in the room 

The pursuit lead, the people who know the client best and the technical lead. Someone who can speak to your organization’s differentiators with honesty, including where you are strong and where you are reaching. And a facilitator who is not emotionally invested in the outcome. 

That last role matters more than it sounds. When teams facilitate their own pursuit workshops they tend to reinforce what they already believe. An outside perspective creates the conditions for a more honest conversation. 

The questions that do the work 

Do we have a relationship with this client? What do we know about this client’s real priorities, beyond what the RFP will say? Who makes the decision, and who influences it? What do they know about us? 

What is our win theme for this specific opportunity? Hint: It’s not a tagline. It is the one thing that makes us the right choice for this client on this project. If it could apply to any proposal, it is not a win theme. 

Where are we strong, and where are we reaching? What would a well-prepared competitor say about us? What do we need to address before the submission? 

What does a strong submission look like for this client? What will they remember after reading several proposals? 

What happens after the room 

The value of a pursuit workshop is not the conversation. It is what the conversation makes possible. A capture plan. Clear ownership of relationship-building activities before the RFP. A win theme that the entire proposal and project delivery team can articulate. A proposal that knows what it is trying to do from the first page. 

Proof in Action 

TSD was engaged by a construction contractor for a major design-build pursuit. We had six weeks until submission with two extensions. When we got started there was no established proposal process of this scale on their side. It was their first time working with us, and their first time sitting down before a proposal was written to develop win themes and review competitive positioning. That session, and the market research we brought into the room, shaped everything that followed. 

The organizations that win consistently do this work. The ones that keep losing are still starting with the template.

If a lost pursuit doesn’t change how the next one is approached, the loss was wasted. 

Most organizations move on too quickly. The next pursuit takes over, timelines compress, and the loss gets explained away, close scoring, a preferred competitor, a tough call. Maybe all of that is true. None of it changes what happens next.  

A structured debrief does. 

What a debrief is 

It is a structured conversation with the right people in the room, designed to extract specific, actionable intelligence from a pursuit that did not go your way. Not a post-mortem. Not a blame session. It has two parts: an internal debrief and, when possible a client debrief. Each serves a different purpose. Both matter. 

The internal debrief 

Run the debrief within two weeks of a loss, while the pursuit is still fresh. Focus the conversation on what will change future outcomes. 

• What did we know about this client before the RFP? What did we not know that, in hindsight, would have changed our approach? 
• What was our win theme? Could every person on the pursuit team articulate it the same way? If not, the proposal probably could not either. 
• What did the executive summary argue? Was it a specific case for selection, or a summary of our qualifications? 
• Where were we genuinely strong, and where were we reaching? Were we honest about that in the proposal, or did we glaze over the gaps? 
• What would we do differently in capture, six months before this pursuit opened?

That last question carries the most weight. The debrief is not about the proposal. It is about what changes before the next one begins. 

The client debrief 

Request it. Most organizations do not. Many evaluators will agree to a brief conversation, especially if the pursuit was competitive and the relationship was professional. 

When the opportunity is there, use it well. Do not defend or explain. Instead ask and listen.  

• What did the winning submission do that resonated?  
• What would have made the proposal stronger?  
• Was there anything in our approach that raised questions you could not answer? 

Even partial feedback is useful. A comment about stronger alignment with constraints signals that the proposal lacked specificity, regardless of how it was perceived internally. 

What changes as a result 

Organizations that improve win rates treat debriefs as a standard practice, not a response to major losses. 

Over time, the impact is visible: 

• Stronger intelligence gathered before the next RFP 
• More precise and credible win themes 
• Better discipline in go/no-go decisions 
• Executive summaries that argue clearly and directly 

None of this comes from a general intent to improve. It comes from specific insight, consistently applied. 

The debrief is where the loss becomes an asset. 

An RFP tells you what a client is asking for. Your relationships tell you what they need. 

The gap between the two is where most proposals either win or lose. 

Procurement language is written to be defensible, not revealing. The evaluation criteria reflect what can be scored, and not necessarily what will drive the decision. By the time a formal opportunity is published, the client already has a sense of who they are comfortable with, who they trust, and the type of partner they are looking for. The document codifies the process because the decision has been forming for longer. 

Relationship intelligence is the practice of understanding that context before the RFP is written. 

What it truly means to know your client 

It means understanding who makes the decision and who influences it. They are rarely the same and the influencers are often more accessible well before formal procurement begins. It means understanding the real challenge behind the stated scope. Every project tells a story. There is a reason this is happening now, why it hasn’t been resolved, a shift in leadership, and/or a growth trajectory that changed the requirements. When that context is understood, proposals are written very differently. 

It also means knowing the political context. Who championed this initiative? What has been tried before? What failed, and why? What is the client organization worried about that they did not putin writing? 

It means understanding the competitive landscape from the client’s perspective, not just your own. Which firms have they worked with? What has their experience been? Why and where are they looking for something different? 

How to gather the right information 

Show up before the procurement. Attend industry events, join client office hours, and engage in informal conversations across the organization. The goal isn’t to sell, it’s to listen and learn to understand. The same relationship-building that gives access to insight is what builds trust, and trust is what a capture strategy is ultimately building toward. 

Ask better questions in the meetings you are already having. Most BD conversations stay at the surface because the questions do. What keeps the client awake at night about this project? What would give them confidence in a partner six months into delivery? Those questions get to what matters. 

Pay attention to what the client pays attention to. What they publish, what they present. Understand what shows up consistently in industry conversations. Organizations signal their priorities constantly. Most competitors aren’t paying attention. 

What it changes 

When you have built genuine relationship intelligence before any RFPs, the proposal writes differently. The executive summary speaks to what the client truly cares about, not what the template calls for. The win theme is specific to this opportunity, not carried over from the last one. The team section explains why these specific people, for this specific project, and it lands because it’sgrounded in truth. 

The difference is visible early. Proposals built on real client intelligence read with clarity and intent. Those built from the RFP alone do not. Evaluators feel it, even if they can’t immediately name why.  

The intelligence is the strategy. Everything that follows, the workshop, the proposal, the interview and presentation, is execution. Start there. 

Workshops shouldn’t start with an agenda. They should start with a clear understanding of what the organization needs to resolve. 

The most effective sessions are anchored in leadership priorities, where clarity is missing, decisions are stalled, or alignment is at risk.  

Often, the issues are clear. Where to begin is not.  

Before we design anything, we focus there: what needs to move, what’s been avoided, and what success must look like beyond the room. And that starts with a small set of questions:  

The questions we ask 

What decision needs to be made, and who makes it? This one emerges faster than people anticipate given how unclear decision authority often is. Because without clear ownership, nothing resolves. 

What conversations have not happened yet? Every organization has them. The ones teams circle but never name directly. An effective and impactful workshop creates the conditions for those conversations to bring them forward, address them openly, and ensure every voice is part of the conversation. 

Who is most impacted by the outcome? When stakes are uneven, behavior follows. An impactful workshop accounts for that; bringing perspectives forward and aligning the group around a shared goal. It is about designing a process that does not inadvertently silence the people most invested in the outcome. If someone stands to lose ground based on what the group decides, they manage that risk. Better to know going in. 

Where are the tensions that will need to be named? They exist in every organization. What goes unspoken doesn’t disappear but shows up sideways. A facilitator who knows where the pressure points are can move toward them deliberately rather than stumble into them. 

What would success look like six weeks or six months from now? Not at the end of the session. Not in the summary document or implementation plan. But when momentum is tested and priorities compete. That is the real measure. Designing backward from there influences what gets prioritized in the room. 

Why this matters more than the agenda 

An agenda is a schedule and discovery is strategy. 

When pre-work is skipped, the first hours of a session are spent determining what should already be clear: what the group is trying to accomplish. That is an expensive and uncomfortable way to get oriented, especially when time is limited and decisions need to be made. 

The quality of the questions asked before the session determines the value created in the room. 

If you are preparing to lead or commission a workshop, the agenda can wait. Start with the questions. The answers inform the agenda. 

It’s true: your website is the first proposal you will ever write for a client who is deciding whether to invite you into a conversation. And, it’s provocative to think about it this way. 

Many websites are treated as a description of what a business does. However, that is not what an effective, hard-working website does. 

When an evaluator, a potential client, or a decision-maker lands on your site, they are trying to answer one question fast: is this the team worth serious consideration? If the answer is not clear within seconds, they leave. And they may not come back. 

The four things a hard-working website gets right 

It does four things well; it:  

1. Tells you immediately what the organization does and for whom  
2. Provides credibility through specific, recent evidence and subject matter expertise: case studies, project descriptions, client work that shows capability, and thought leadership 
3. Makes clear who their people are and why they are the right people to perform the work  
4. Gives the visitor a reason to take a next step through a call to action (CTA) 

Most websites do some of these things partially. Few do all of them well. The gaps are usually in the evidence: organizations that have done strong work but have not made the time to document it. Case studies that don’t exist or are dated. Testimonials have been collected without being published.  

We have seen firms with impressive track records that were not verifiable anywhere on their site, which means an evaluator who does not already know them has no way to build confidence. 

If a visitor lands on your site and cannot quickly find what you do and why you are credible, they leave. And they go somewhere else. A chaotic or underdeveloped website signals an organization that has not yet decided to take itself seriously. 

The thought leadership connection 

Your website is where the ecosystem comes together. A LinkedIn post creates awareness and drives curiosity à A thought leadership article, hosted on your site, converts that curiosity into credibility à A case study converts credibility into confidence à The post gets people in the door à The site is where the case gets made. 

This means the site must be doing its part. If someone reads a strong post, clicks through, and lands on a page that has not been updated in two years, the signal they receive is that the post was a one-off, not evidence of a consistent practice. The site reinforces what the content is building. 

The update problem 

Small and mid-sized organizations struggle here for a predictable and understandable reason: nobody owns it. The website gets built, goes live, and then quietly becomes obsolete. A team member updates it when they have time, which means it updates inconsistently and without strategic intent. 

The most practical approach we have seen is systematizing the content creation process so that updates happen as a byproduct of the work. The moment a project is won is the right time to create the foundation of the case study, using material already in hand from the proposal process. By the time the project closes, the case study is nearly written. That reusable content strengthens the website, the next proposal, and the firm’s credibility simultaneously. 

The hardest thing to get right 

Treating the website the same way you would treat any other channel: with intention, consistency, and a clear sense of what it needs to do. 

Organizations know the value of a strong proposal. They have seen what a polished, well-structured submission can do for a relationship. The website is that submission, running continuously, to every person who is deciding whether to invite you in. Investing in it is a business development strategy. 

Every potential client who researches you before reaching out is reading a document you have not updated in two years. That is the first impression you are making. 

One of the most effective ways to generate testimonials is to write them first. 

This is a practice, not a tactic. A specific, honest recommendation for a client or collaborator, with no expectation of return. Simply a genuine contribution to someone whose work deserves to be named out loud. 

The reciprocity tends to follow anyway. But that is not the point. 

Why this matters 

We close every engagement thinking about what we can give before we think about what we might ask for. A recommendation or an introduction. It could be a referral to someone we know who could help with what comes next. Sharing something we learned during the project that has value beyond the deliverable. 

This is not altruism. It is a deeply practical orientation toward how relationships compound over time. The firms that grow on trust rather than transactions are the ones that have built a reputation for showing up generously, consistently, over years. That reputation is not earned in a single gesture. It is built through a pattern. 

What generosity looks like at the end of an engagement 

It’s a structured close that centers the client. What did we learn together? What is the client better positioned to do now than they were at the start? What matters next and who can help? 

It’s writing the testimonial or recommendation before asking whether the client would be willing to provide one. Most clients are happy to provide a reference. Very few initiate it. Making it easy is a generous move. 

It’s staying connected after the project closes. Not to sell, but because the relationship has value beyond the transaction. A check-in a few weeks later. A relevant article shared or an introduction made because it was useful. 

Generosity is a growth strategy 

This is not a soft idea. It’s how effective business development works. 

Referrals come from relationships. Relationships deepen when people feel supported without an immediate transaction attached. The firms that generate the most referrals are rarely the most aggressive—they are the most consistent. Cass has made generosity her word of the year for 2026 for a reason. Practiced deliberately, it becomes operational. The question at the end of every engagement—and in the day-to-day—is simple: what can be given here before anything is asked for? 

That orientation, practiced consistently, builds the kind of reputation that grows a firm over time. Quietly, durably, and without a pitch. 

Most pursuits are decided before they are ever released. Capture is not an activity. It is a way of operating. 

The distinction matters because capture strategy is not a tool you deploy for your biggest pursuits and set aside for the rest. It is business as usual. The intelligence-gathering, relationship-building, and proactive positioning are the things that compound over time. Teams that treat capture as a project versus practice keep starting from zero and get progressively better at winning. 

Here is what that transition looks like. 

Where most BD teams start 

Reactive. An RFP lands, the team pivots, the proposal is built in a matter of days or weeks. There is little clarity on why the pursuit is being chased beyond surface-level alignment. The capture work that should have happened months ago did not happen at all. 

This is not a failure of intent. It is a failure of infrastructure. Without a shared vocabulary for capture, a consistent approach to intelligence gathering, and structured pursuit conversations, reactive becomes the default. It is the path of least resistance, and it produces average results at significant cost. 

The leadership conditions that make it possible 

Capture culture does not start with the BD team. It starts with what leadership prioritizes. 

Organizations that do this well keep senior leaders close to the client and grounded in the forward pipeline. They are asking well before a pursuit opens, what is known, what is missing, and where the organization needs to be positioned. RFPs are not a surprise. That posture, curious, proactive, and relationship-forward, sets the tone. Without it, BD teams default to what is urgent: the proposal in front of them. 

The shared vocabulary that accelerates it 

One of the earliest gains in building capture culture is alignment on language. What does capture mean in practice? What counts as a qualified opportunity? What is required for a go/no-go decision? What distinguishes a win theme versus a capability statement? 

Clarity here sharpens pursuit conversations. The debate about whether to pursue shifts from an instinctive reaction to a disciplined assessment. The pursuit workshop becomes standard practice, not a special event. 

This shift is often most visible in organizations where capture was not previously formalized. Introducing a shared vocabulary changes how the pipeline is understood and acted on.  

What it looks like: Early adoption vs. When it sticks 

Within the first number of months, new habits are forming with some friction. The go/no-go process is being applied with some discomfort. Workshops are happening. Internal debriefs are becoming standard. Intelligence gathering is more intentional, even if not yet systematic. 

In time those habits are embedded. Pipeline conversations reference intelligence gathered months earlier. Win themes are clear before pursuit sessions begin. Proposals are more specific, more aligned to the client. The increased win rate reflects it. 

This shift does not come from a one-time effort. It comes from sustained leadership focus, shared language, and consistent application over multiple cycles.  

Capture culture is a long game. It is also the only BD strategy that compounds. 

A compliant proposal is safe. A compelling one sparks recognition that highlights, “this team truly gets it”. Technical compliance is required, yet not sufficient. 

Evaluators read a lot of proposals. The ones that blur together are those that answered the questions and ticked the boxes. The ones that are remembered tell a story, a specific, credible, client-centric story and how the proposed team fits, for this project, right now. 

What compliance looks like 

A compliant proposal addresses every section of the RFP in the order it was requested. It demonstrates qualifications, experience, methodology, and approach. It includes the required forms and certifications, team bios, project descriptions. 

It also, in many instances, looks nearly identical to the many competing proposals submitted alongside it. Same structure. Same language. Same generic win themes about being client-focused, collaborative, and committed to excellence. Same executive summary that opens with a variation of. “We are pleased to submit this proposal for your consideration…”. 

Compliance won’t win the work. It only keeps you from losing it. The evaluation committee already expects it. What moves a score is what lives above the baseline. 

What compelling looks like 

A compelling proposal demonstrates a clear understanding of the client’s specific situation, not the category of client they belong to. It reflects intelligence gathered before the RFP dropped. It names the real challenge beyond the stated scope. The executive summary reads as if the work has already been considered in context, because it has. 

The differentiators are real. Not generic claims of deep technical expertise, but specifics: experience working alongside the client’s operations group on a comparable project in the same region, with a clear understanding of the constraints that will define success. The narrative has a through-line. The client reads the executive summary and knows the story. They read the methodologysection, and it reinforces the same story. They read the team bios and understand why these specific people, in this specific configuration, are the right team to deliver the work. Nothing contradicts anything else. The proposal is clear in what it is arguing. 

Proof in Action 

Where the story comes from 

It does not come from the writing. It comes from the work that happens before the proposal opens. 

In a Toronto infrastructure pursuit, TSD helped a team with strong technical capability and no shared narrative find their story under significant time pressure. When we started asking questions, we found brilliant, disconnected perspectives. Each person could explain their own piece. Nobody had put the pieces together into a coherent argument for why this team, assembled this way, was the right choice for this client. 

Several weeks later, the submission ranked first in technical scoring. The qualifications were strong before we arrived. What changed was the narrative architecture: the through-line that made those qualifications legible, connected, and client-specific. 

A practical test 

Read the last executive summary as an evaluator would. Not as the lead reviewer who has part of every conversation, but as a committee member encountering your organization for the first time. 

Does it clearly convey an understanding of the client’s situation? Does it make a specific case for selection? Does it give the evaluator language they can carry into the room? If it reads like a summary of what follows rather than an argument for selection, the proposal is working too hard.  

Here’s a tip: the executive summary should function as the proposal itself, with everything that follows serving as evidence. 

Compliance gets you to the table. The story gets you the contract.