Your one-page capability statement

A capability statement is a one-page document that tells a stranger — typically a prospective foreign buyer, partner, distributor, or trade commissioner — what your business does, who you serve, and what evidence you have that you can deliver. It is not a brochure, a pitch deck, or a website in printed form. It is a tightly structured reference document, designed to be read in under sixty seconds by someone who has never heard of you and is deciding whether to take a meeting.

In international trade, the capability statement functions as your business card, your elevator pitch, and your evidence file compressed onto a single page. It is the document a trade commissioner forwards to a contact in their market on your behalf. It is the document a prospective distributor reads before agreeing to a call. It is the document an embassy commercial officer skims while you are in the meeting, to remember what you do.

Because it travels without you, it has to work without you. Every word, every figure, and every layout decision should be made with that constraint in mind.

You need a capability statement if any of the following apply:

• You are attending a trade mission, trade show, or B2B matchmaking event.
• You are asking a trade commissioner, embassy, or industry association to introduce you to a foreign contact.
• You are approaching prospective distributors, agents, or partners in another market.
• You are responding to a foreign government procurement opportunity that requests company information.
• You are seeking export finance or insurance and the lender has asked for a company overview.

If you are none of these, you do not yet need a capability statement. You will. Drafting one early — before you need it — is also a useful exercise: it forces you to articulate what you do and what evidence you have, and it surfaces the gaps in your story before they surface in a meeting.

A capability statement should fit on a single page, in this order:

• Company name and logo. Top of the page. Logo should be legible at print size and at screen thumbnail size.
• One-sentence description. What you do, for whom, in plain language. No jargon, no mission statement, no "passion."
• Capability summary. Three to five bullet points naming your main products, services, or areas of expertise.
• Proof points. Three specific, verifiable pieces of evidence that you can deliver. See the next section.
• Markets and sectors. The industries you serve and the markets you currently operate in or are targeting.
• Differentiators. Two or three things that distinguish you from comparable competitors — certifications, IP, scale, partnerships, regulatory clearances.
• Contact information. Name, role, email, phone, website. Include time zone.

That is the entire document. If you cannot fit it on one page, you are including too much. The discipline of one page is the point: it forces you to decide what actually matters.

The proof points are the heart of the document. They are the difference between a capability statement that reads as marketing and one that reads as evidence. A proof point is a specific, verifiable statement about work you have done. The test is whether a stranger could check it.

Weak proof points are vague and uncheckable: "trusted by leading clients," "extensive experience," "proven results." Strong proof points name a client, a project, a figure, or a certification:

• "Supplied 12,000 units to [Client] in 2024 under a three-year supply agreement."
• "Implemented [Project] for [Client], reducing processing time by 35 percent over 18 months."
• "ISO 9001 certified; CE marked for the European market."
• "Granted US Patent 11,XXX,XXX in 2023; trademark registered in Canada, the United States, and the European Union."

If you are early in your business and do not yet have client names or patents to cite, use what you have: completed pilots, signed letters of intent, sector certifications, founder credentials, or measurable outputs from internal projects. Be honest, but be specific. "Three completed pilots with municipal water utilities in Ontario" is more credible than "extensive pilot experience."

The contact block is the most often-broken part of a capability statement, and the easiest to fix. It should include:

• A named contact — not "info@company.com" — with their role.
• A direct email address and a phone number that reaches a human or a clear voicemail.
• Your website, ideally in English and any other language relevant to your target market.
• Your time zone, written out: "Eastern Time (UTC-5)."

The time zone matters because the document travels. A reader in Berlin needs to know whether your business hours overlap with theirs. A reader in Tokyo needs to know whether to expect a reply the same day or the next. Omitting the time zone forces them to look it up, and most will not.

• More than one page. If you cannot fit it on one page, the reader will not read the second page.
• No proof points. Marketing claims without evidence are ignored.
• Jargon and acronyms. The reader is often a trade officer, not a sector specialist. Write for an intelligent non-specialist.
• Outdated information. A capability statement with a two-year-old client list signals that you do not update your materials. Refresh quarterly.
• Unreadable at print size. Body text below 10pt is not legible on a printed page held by someone in a meeting. Use 10pt or larger.
• Generic contact block. "info@company.com" with no name and no phone is read as "we are not really set up to receive inbound interest."
• PDF only, no editable source. You will need to produce versions. Keep the source file.

A single capability statement is a starting point. As you target specific markets or audiences, you will produce versions:

• A version translated into the language of your priority market, with proof points chosen for that audience.
• A version for procurement opportunities, with emphasis on certifications, scale, and past performance.
• A version for distributors, with emphasis on product range, margins, and support.
• A version for investors, with emphasis on IP, market traction, and growth.

Keep the master document as your source of truth. Each version is a controlled variant, not an independent document. When you update the master, update the variants in the same session.