A company profile introduces the business. A capability statement summarises relevant capabilities and selected evidence. A technical proposal responds to a particular project’s requirements. They may support each other, but changing a cover does not make them interchangeable.
Company profile: a general introduction
A profile explains who you are, which services you provide, where you work and which evidence supports your experience. It is useful for introductions, correspondence and meetings, and should be updated when services or business details change.
Its scope is broader than a response to one project, but it need not contain every activity in the business’s history. Select accurate information that helps the reader, and make the next contact step clear.
Capability statement: a focused summary
A capability statement highlights specialisms, relevant services, verified capacity and selected examples. One or two pages may work for a brief introduction, but this is not a universal qualification standard or mandatory length.
For example, replace “we offer every construction solution” with the work the business actually performs, its service area and its role on a comparable project. The reader should be able to assess relevance before requesting a longer profile.
Technical proposal: a specific response
The buyer’s documents determine the required content and format. Depending on the project, a response may need a delivery method, team, programme, outputs and answers to technical criteria. No single generic checklist covers every tender.
Preparing this response requires relevant technical knowledge and review by the responsible specialists. Good presentation cannot resolve a missing technical response, required document, signature or submission deadline.
Match the document to the request
- “Send us your company information”: start with an updated profile relevant to the audience.
- A brief procurement meeting: a capability statement may work, with a detailed profile available when needed.
- A response to project requirements: review the buyer’s documents and identify who will prepare and approve the technical response.
- An unclear request: confirm purpose, format, language and deadline before sending a large bundle.
Do not describe material as approved or fully compliant without a specific, verifiable basis for that statement.
A practical preparation checklist
Record four fields for each requirement: what the recipient asks for, the available evidence, who is responsible for its accuracy, and what remains outstanding. For example: “Comparable project — description and images — project manager — publication permission required”. This supports organisation; it does not determine eligibility.
WJAZ organises and designs company and capability materials from approved inputs. Developing technical solutions, commercial pricing, legal advice and registration with buyers are not assumed obligations within the supplier presentation service.