How does a company profile differ from a proposal for a specific customer?

Start with the decision each document supports

A reader uses a company profile to understand the supplier. They may be checking whether the business works in the relevant field, has suitable experience or is worth inviting to quote. The profile should provide a clear, reusable account of the company's identity and capabilities.

A proposal supports a more specific decision: whether to buy the work described from this supplier on the proposed terms. It needs to address the customer's problem, requirements and constraints. A polished history of the business does not answer those questions by itself.

Before writing, state the purpose and audience. A procurement officer comparing responses, an operations manager seeking a solution and a prospective partner exploring capabilities may need different material. Knowing the decision helps determine what belongs in the main document and what should sit in an appendix.

Compare the information each document needs

The comparison describes a practical distinction, not a mandatory document format. The customer's instructions take priority where they prescribe a structure. A tender may request a company profile as one attachment while still requiring detailed answers in separate schedules.

Keep those functions separate even when the files are combined. Clear sections help the evaluator locate the response without searching through generic background pages.

Build the profile from durable, supportable facts

Include the correct legal identity, trading name where relevant, service scope and contact information. Describe the company's actual operating capacity, relevant team roles and experience. Use specific facts that can be verified instead of unsupported claims to be the best or the largest.

Attribute experience correctly. A founder's work before joining the company belongs to that person's experience, not automatically to the company's project history. Identify the role and context. If the company is new, say so while explaining the capabilities the team brings.

Review registrations and memberships for the correct holder, scope and current status. Pending applications should not appear as approved credentials. Maintain a source file for important statements and a review date for information that can change, so the reusable profile does not become a source of stale claims.

Make the proposal answer the actual brief

Read the customer's request and extract the required outcomes, deliverables, constraints and evaluation questions. Respond in the requested order where possible. Show how the proposed work addresses the need rather than repeating a standard service description that could apply to any customer.

Define outputs in terms the customer can review. A statement such as provide business support may be too broad to establish what completion means. Identify the documents, activities or other results included, together with responsibilities, dependencies and an appropriate acceptance process.

Include the commercial basis relevant to the offer. Explain what the price covers, the treatment of additional work and any material conditions. Do not invent a fixed timeline when essential customer information or third-party decisions remain unresolved. State the dependency and the effect on planning.

Select evidence that matches the customer’s requirement

A proposal should draw selectively from the profile's evidence library. Choose examples related to the work, scale and conditions in the brief. A long list of unrelated projects can make the response harder to assess without strengthening the relevant capability claim.

For each example, describe what the company actually did and what evidence is available. Distinguish a completed project from one still in progress. Obtain appropriate permission for references, testimonials and confidential material, and avoid sharing personal information unnecessarily.

National Treasury's evaluation guidance illustrates why criteria matter in procurement. For an actual tender, use the issued requirements to select the evidence. A generic profile cannot establish compliance with every bid-specific condition.

See how the same company needs two different documents

Consider an illustrative bookkeeping business. Its profile describes the company, team, services and relevant experience. That material helps a prospective customer understand the supplier, but it does not explain how a particular backlog will be handled.

The customer's proposal would identify the period to be reviewed, records required, work included and outputs expected. It would explain assumptions about the condition of the records, who answers queries and how additional periods or missing information will be handled. The proposed fee would relate to that defined scope.

The profile can be attached as supporting background. The proposal still needs its own customer-specific reasoning. If the customer changes the number of entities or the period of work, the proposal may need revision even though the company's profile remains largely the same.

Keep identity and capability claims consistent

Compare the profile, proposal, quotation and supporting documents for the same legal entity and contact details. If a trading name is used, explain its relationship to the contracting company. Do not attach another group company's credentials as though they automatically belong to the bidder.

Check whether a proposed team member is actually available for this work. The profile may describe the wider business, while the proposal needs to identify the people or roles committed to the engagement. Avoid promising every resource shown in the company brochure.

Use current versions of credentials and verify material statements before sending. The Consumer Protection Act addresses misleading representations within its scope. Accurate, consistent wording also makes the commercial discussion clearer, regardless of the document's visual polish.

Maintain the profile and proposal on different cycles

Review the reusable profile when the business changes: services, personnel, address, project history or registration status. Keep an approved master and archive superseded versions. A dated review record helps staff know which file is safe to reuse. Assign someone to approve changes and withdraw obsolete copies from shared folders. Otherwise, a salesperson may unknowingly send an older credential or a service description the business no longer supports.

Review each proposal against the current customer brief before issue. Record the version, recipient, assumptions and validity conditions. When the customer requests a change, identify whether it affects scope, price, responsibility or timing and issue a clearly identified revision.

A proposal sent for one customer should not be reused for another without checking confidential information and customer-specific terms. Remove old names, project facts and attachments. Search the complete file, including headers, footers, comments and document properties where they may reveal information from the previous engagement.

Prepare a focused writing pack

For a profile, collect company identity records, approved service descriptions, team information and evidence for capability claims. For a proposal, add the actual customer request, questions needing clarification, proposed scope and approved commercial assumptions. Mark information that cannot yet be confirmed.

Ask the business owner to verify facts and the person responsible for delivery to review commitments. A writer can organise and express the offer, but should not invent operational capacity or accept commercial obligations on the company's behalf.

Profile and proposal-writing support can help produce documents that work together. A useful profile makes the company understandable. A useful proposal makes the specific offer assessable, with evidence and terms that match the customer's decision.

Before issue, check that every requested attachment is present and readable. Confirm the recipient and delivery method, preserve the final version and record any questions that remain open. These simple controls make later clarification easier and reduce uncertainty about which offer the customer actually received.

If the customer accepts the proposal subject to changes, save those changes with the original offer and the agreed final version. Give the delivery team that complete record so it can distinguish accepted commitments from earlier options.