RFP answer examples: company overview and "why us" sections

RFP Tips

Author:

Chris Mabry

Short answer: A strong company overview answer in an RFP is short, factual and tailored: who you are (legal name, founded, size, locations), what you do in one sentence, who you do it for (customers like this buyer), and one or two proof points relevant to this RFP. The "why us" answer is different: it's two or three reasons tied to the buyer's evaluation criteria, each backed by evidence. Keep the overview stable and approved; rewrite "why us" for every bid.

In Iris: company overview answers live in the Approved Answers Library, and when a past answer is reused, Iris strips other customers' names out of it.

Who this is for: proposal writers and sales teams answering "Provide a company overview," "Describe your organization," or "Why should we select you?"

On this page

  1. What should a company overview answer include?
  2. Which parts should you tailor for each RFP?
  3. Example 1: short overview (100 words)
  4. Example 2: full overview with a facts table
  5. Example 3: public-sector organization profile
  6. Example 4 and 5: "why us," weak vs strong
  7. Mistakes
  8. FAQ

What should a company overview answer include?

ElementExample placeholderWhy evaluators want it
Legal name and entity[Legal name], a [entity type] in [jurisdiction]Contracting and due diligence
Founded and ownershipFounded [year]; [privately held / subsidiary of …]Stability
Size[Employees]; [offices]Capacity
What you doOne sentenceRelevance
Who you serve[Customer types / industries]; [number] customers as of [date]Fit
Relevance to this RFPComparable workConfidence
CredentialsCertifications, audits, awards (dated, named exactly)Risk reduction

Which parts should you tailor for each RFP?

Keep stable (approved, owned)Tailor every time
Legal name, entity, founding yearWhich customers and projects you highlight
Employee count and locations (refresh quarterly)Which credentials you lead with
One-sentence descriptionThe "relevance to this RFP" paragraph
Certifications and their datesThe entire "why us" answer

Example 1: short overview (100 words)

Fictional company: Juniper Ridge Analytics. Prompt: "Provide a brief company overview (max 100 words)."

Juniper Ridge Analytics, Inc. (Delaware corporation, founded 2016) builds forecasting software for regional grocery and convenience retailers. Our 140 employees work from offices in Denver and Toronto. We serve [number] retail chains as of [date], ranging from 20 to 400 stores; [x] of them are of similar size to [buyer]. Our platform forecasts demand by store and SKU and feeds replenishment orders to the retailer's existing ERP. We hold a [SOC 2 Type II report for [period]], available under NDA.

Why it works: every sentence is a fact an evaluator can use, it says how many customers look like this buyer, and it stays under the limit.

Example 2: full overview with a facts table

Fictional company: Calloway Benefits Administration. Prompt: "Describe your organization, history and experience."

Calloway administers employee benefits for mid-size employers. Since 2009 we've grown from a single-state administrator to serving employers in [x] states, and benefits administration is all we do.

FactDetail
Legal entityCalloway Benefits Administration LLC
Founded2009
Employees[number] as of [date]
LocationsColumbus (HQ), Raleigh
Employers served[number], 200–5,000 employees each
Relevant experience[number] public school districts and [number] municipalities
Assurance[SOC 1 Type II report, period], available under NDA

For [buyer], the most relevant experience is our administration of [comparable program] for [comparable client type], described in the references in Section 6.

Why it works: narrative for the story, table for the facts, and a closing line that bridges to the buyer.

Example 3: public-sector organization profile

Fictional company: Brightmoor Environmental Services. Prompt: "Provide your firm's profile, including size classification and certifications."

Brightmoor Environmental Services, Inc. · UEI [number] · CAGE [code] · Founded 2004 · [number] employees · [Small business classification, if applicable, under NAICS [code]] · Certifications: [state DBE/MBE/WBE, if held, with certificate number and expiry]. Headquarters: [address]. Brightmoor has completed [number] stormwater compliance contracts for county governments since [year]; three are listed as past performance in Volume II.

Why it works: public-sector evaluators check identifiers, size status and certifications first. Put them in the first lines, exactly as registered.

Example 4 and 5: "why us," weak vs strong

Example 4, weak (fictional Juniper Ridge):

"Juniper Ridge is a leading, innovative provider with a passionate team and a customer-first culture. We are the best choice for your needs."

Example 4, strong:

"Three reasons, mapped to your evaluation criteria:
1. Forecast accuracy (criterion 2, 30%). We forecast at store-and-SKU level, and [reference customer, with permission] will describe their results on a call.
2. Fast integration with your ERP (criterion 3, 20%). We've connected to [your ERP] at [number] retailers; the connector is standard, not custom.
3. Grocery focus (criterion 4, 15%). Every customer is a grocery or convenience retailer, so fresh and seasonal items are built into the model, not configured later."

Why: reasons are numbered, mapped to weighted criteria, and each has a checkable proof. See win themes for how to develop them.

Example 5, strong, short form (fictional Calloway, 50-word limit):

"We only do benefits administration, for employers your size. We already administer [comparable program] for [number] school districts, so your staff won't be our first. And your account team, named in Section 5, stays with you after go-live."

Mistakes

  • Starting with the founding story when the RFP asked for facts.
  • Superlatives without proof: "leading," "best," "innovative."
  • Out-of-date numbers (employee count, customer count) that contradict your website.
  • Another customer's name left in a reused answer.
  • Unverifiable customer counts. Only state numbers your finance or sales ops team can stand behind.
  • One "why us" for every bid. It should change with the buyer's criteria.

How Iris helps

Iris is AI software for RFPs, security questionnaires and proposals.

  • One approved version. Company facts live in the Approved Answers Library with an owner, expiration date and review cadence, so the employee count doesn't drift between bids.
  • Safe reuse. Iris reuses your approved wording instead of rewriting it, and strips other customers' names out of reused past answers.
  • Length and tone control. Custom instructions set length and tone per question, useful for 50- and 100-word limits.

Iris is rated 4.9/5 on G2 from 85 reviews (October 2026). Try Iris free on an RFP you've already answered.

FAQ

How long should a company overview be in an RFP?
Follow any limit. Without one, 100–250 words plus a facts table is usually enough.

What's the difference between "company overview" and "why us"?
The overview states who you are; "why us" argues why you're the best choice for this buyer.

Should I include customer logos?
Only with permission and if the format allows. Named references, with permission, are more useful to evaluators.

How often should the standard overview be updated?
Whenever a fact changes, and at least quarterly for numbers like employees and customers.

See it live

Respond to RFPs
without the grind.

Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.