Capability deck or proposal: use at the right time

This question comes up when the sales team grows beyond one person, or when you realize each employee is creating materials in their own way. The answer is not to choose one or the other but to clearly understand where each type stands in the journey from the first meeting to signing the contract.

Two documents, two different steps

The capability deck (or corporate deck, which is a comprehensive introduction to overall capabilities) is a general document. It is not aimed at a specific client, does not include pricing, and has no defined scope. Its sole purpose is to demonstrate: you have done this type of work, the level at which you operate, and who you are. It is used in the initial conversation.

A collaboration proposal sample is a document specific to one client. It includes the client's name, a specific scope of work, and figures. It is used at the closing stage, after the team has listened enough to understand what the client needs. Sending a proposal before understanding the needs is premature.

Factors that need consideration

Before deciding which team needs the documentation more urgently, you should answer these four questions:

• Which step is the team lagging behind: opening discussions with new clients, or closing deals with clients who already understand them?
• How many versions of the document exist: If each employee has a different version, prioritize creating a standard version first.
• Can the team update on their own: Sales documents need to be easily editable to keep information up to date, without relying on design each time.
• What stage are customers in: if the current pipeline mainly consists of referrals from existing customers who already trust you, lacking a proposal is a bigger issue than lacking a portfolio.

When to use capability statements?

Using a capability statement when meeting a client for the first time and they do not know much about you. At this point, the client is not ready to hear numbers; they need to know first: have you done this before, for whom, and what were the results. The capability statement answers those three questions without putting pressure to buy early.

The capability deck is also useful when clients are comparing multiple suppliers and have not yet decided to request pricing. Leaving this document after a meeting helps clients have a reference point when they hold internal discussions without you present.

When to use proposal templates?

Use a collaboration proposal template when you have enough information to write a specific scope: what the client wants to do, how long it will take, and what the budget is. At this point, the proposal serves its purpose, providing a clear option for the client to decide yes or no.

What matters is that the proposal does not need to be rewritten from scratch each time. A well-structured template allows the team to simply change the client's name, adjust the scope, and numbers to send it out. This saves time and ensures that all versions created by different people still look cohesive.

A sales deck closes deals by supporting purchasing decisions, unlike a pitch deck that opens conversations and a corporate deck that builds general trust. These three types serve three different moments.

Visualbest; Visible.vc

Common mistakes

• Sending a general capability profile when the client is waiting for a proposal with specific scope and pricing, leaving them unsure of the next steps after reading.
• Creating each proposal from scratch results in each document having a different presentation style, and the team spends many hours each time they send one.
• A proposal without evidence of foundational capability may lead to clients lacking trust upon seeing the numbers, making it easy to decline due to lack of comparative basis.
• When each employee creates their own slides, over time the brand appears disjointed and no one recognizes it as the same company.

Sinh Vũ's viewpoint

Sinh Vũ often provides the sales team with two parallel items: a capability statement to establish credibility for discussions, and a collaboration proposal template for the team to reuse. The original template is meticulously designed once, ensuring that all subsequent versions created by the team are consistent, whether made by five people or one.

The Sinh Vũ refines the narrative flow and presentation framework, while the specifics of pricing and scope are your decisions. This division of labor helps the documents be both beautiful and authentic, avoiding a situation where a beautiful design is not altered by the team for fear of ruining the layout.