# Corporate Website Technical Specification Template

Version: 1.0 · Published: 2026-07-29 · Language: English
Source: https://www.bakibilisim.com/en/how-we-work/

This template sets out, heading by heading, what belongs in the request for
proposal (RFP) for a corporate website project. It is written to be filled in
jointly by procurement, IT and corporate communications.

There are no conditions of use: it works with any supplier, carries no brand
name and contains no hidden clause. Fields in square brackets are yours to
complete; delete the clauses you do not need. It may be reproduced with
attribution.

---

## 0. How to use this template

1. Copy the template and fill in the `[...]` fields.
2. Delete the clauses that do not apply to your organisation — do not leave
   them blank.
3. Settle the threshold values (clause 4) before you go out to bid; common
   thresholds are the only thing that makes proposals comparable.
4. Clauses 9, 10 and 11 need review by your legal team.

---

## 1. Organisation and project record

| Field | Value |
|---|---|
| Organisation | [name] |
| Industry | [industry] |
| Project name | [project] |
| Current domain | [domain] |
| Current platform | [WordPress / custom / static / unknown] |
| Target launch date | [date] |
| Budget range | [range] |
| Project owner (client side) | [name, department, e-mail] |
| Decision authority | [role] |
| Proposal deadline | [date] |

---

## 2. Purpose and scope

**Purpose (one sentence):** [e.g. "Launch a multilingual corporate site on
which an overseas buyer can reach technical documentation and capacity
information quickly."]

**In scope:**
- [ ] Information architecture and URL structure
- [ ] Interface design and design system
- [ ] Development and content management layer
- [ ] Content production / rewriting
- [ ] Multilingual structure — target languages: [languages]
- [ ] Product / service catalogue
- [ ] Technical document library (datasheets, certificates, manuals)
- [ ] Location / dealer / branch pages — count: [n]
- [ ] Forms and enquiry flows
- [ ] Integrations with existing systems: [ERP / CRM / PIM / other]
- [ ] Search visibility work (SEO / AEO / GEO)
- [ ] Post-launch maintenance — duration: [months]

**Out of scope (not expected from the supplier):** [copywriting, photography,
video, hosting fees, third-party software licences, translation …]

---

## 3. Audience and decision scenario

| Audience | First information they look for | Evidence they expect |
|---|---|---|
| [procurement specialist] | [capacity, certification] | [documents, references] |
| [engineer / technical buyer] | [technical documentation] | [datasheet, drawing] |
| [end user] | [product, location] | [price, availability] |
| [investor / press] | [corporate information] | [report, statement] |

Usage context: [desktop / mobile / on site, weak network / factory network]

---

## 4. Acceptance criteria and thresholds (mandatory)

The bidder must state **line by line**, in writing, whether each threshold
below is accepted. If a threshold is missed, the correction belongs to the
supplier and cannot be billed as an extra item.

> **We hold ourselves to these thresholds too.** The rows below are not only
> what you ask of a supplier; they are the thresholds bakibilisim.com is
> measured against. The current **measured** values for our own site — with the
> measurement tool, its version, the date and the number of runs — are published
> at <https://www.bakibilisim.com/en/proof/>. You should be able to ask us for
> exactly the evidence you are asking your supplier for.

| # | Criterion | Suggested threshold | Measurement tool | Accepted |
|---|---|---|---|---|
| 1 | Lighthouse Performance (mobile) | ≥ 95 | Lighthouse, mobile emulation | [ ] |
| 2 | Largest Contentful Paint (LCP) | < 1.8 s | Lighthouse lab measurement | [ ] |
| 3 | Cumulative Layout Shift (CLS) | < 0.05 | Lighthouse + field data | [ ] |
| 4 | Interaction to Next Paint (INP) | < 200 ms | Field data + interaction test | [ ] |
| 5 | Accessibility | WCAG 2.1 AA | Automated scan + keyboard pass | [ ] |
| 6 | Structured data (JSON-LD) | 0 validation errors | Schema validator + rich result test | [ ] |
| 7 | Titles and descriptions | Unique on every address | Site-wide crawl report | [ ] |
| 8 | Language mapping (hreflang) | Reciprocal + x-default | Site-wide crawl report | [ ] |
| 9 | Redirect integrity | 0 indexed addresses left without a counterpart | Redirect table + crawl | [ ] |
| 10 | Heading hierarchy | A single h1 on every page | Structure checklist | [ ] |
| 11 | Third-party requests (first load) | [0 / max n] | Network log | [ ] |
| 12 | Browser support | [last 2 versions + …] | Manual test matrix | [ ] |

Measurement conditions: the device and network emulation, the list of measured
pages and the measurement date must be stated in the report. A single homepage
measurement is not accepted; at least [5] different page types are measured.

---

## 5. Content and search visibility requirements

- [ ] A single `h1` on every page, with a logical `h2`/`h3` hierarchy
- [ ] Question-form headings with a direct answer paragraph beneath each
- [ ] `sitemap.xml` and `robots.txt` generation
- [ ] AI crawler policy (allowed / blocked bots) — the decision is the client's
- [ ] `llms.txt` generation (compact, at most [6] KB)
- [ ] Organization / LocalBusiness / Service / FAQPage / BreadcrumbList schemas
- [ ] Consistent canonical address and trailing-slash policy
- [ ] 301 redirect table (for every currently indexed address)
- [ ] Open Graph and Twitter cards, unique on every page

---

## 6. Technical requirements

| Topic | Requirement |
|---|---|
| Technology preference | [static / headless / WordPress / supplier's choice] |
| Content management | [who updates, how often] |
| Hosting | [in the client's name, provider: …] |
| Domain and DNS | Remain registered in the client's name |
| Certificate (TLS) | Automatic renewal |
| Backups | [frequency, retention, restore test] |
| Security headers | CSP, HSTS, X-Content-Type-Options, Referrer-Policy |
| Repository | In the client's account, or transferred at project end |
| Environments | [development / staging / production] |
| Access management | Per person, revoked on departure |

---

## 7. Deliverable list

The format and the moment of delivery must be written for each deliverable.

| # | Deliverable | Format | Delivered at |
|---|---|---|---|
| 1 | Information architecture map and redirect plan | [ ] | [ ] |
| 2 | Design system / token file | [ ] | [ ] |
| 3 | Codebase and version history | [ ] | [ ] |
| 4 | Multilingual structure and hreflang mapping | [ ] | [ ] |
| 5 | Structured data graph | [ ] | [ ] |
| 6 | Dated performance report | [ ] | [ ] |
| 7 | Accessibility report | [ ] | [ ] |
| 8 | Content management training and handbook | [ ] | [ ] |
| 9 | Source code, design files and copyright transfer | [ ] | [ ] |

---

## 8. Process, division of work and communication

- Phases and dates: [table]
- Approval cycle: client-side feedback within [n] working days
- Meeting rhythm: [weekly / fortnightly], duration [minutes]
- Point of contact: one named accountable person on the supplier side
- Change management: scope changes are priced through a written addendum

---

## 9. Service levels (SLA)

| Priority | Example situation | First response | Intervention |
|---|---|---|---|
| Critical | Site unreachable, form flow stopped | [same working day] | [same working day] |
| High | An important function is broken | [1 working day] | [2 working days] |
| Normal | Content or minor fix | [2 working days] | [planned release] |
| Low | Improvement request | [5 working days] | [roadmap] |

- Durations are counted in working days and exclude public holidays.
- The uptime commitment belongs to the hosting provider; the provider's SLA
  document is attached to the proposal.
- On day [30] after launch the acceptance criteria are measured again.

---

## 10. Intellectual property, handover and exit

- [ ] Source code, design files and content copyright belong to **the client**.
- [ ] Open source component and font licences are listed.
- [ ] Third-party licences (stock imagery, commercial plugins) are bought in
      the client's name.
- [ ] Account ownership (domain, DNS, hosting, search console, analytics, app
      store accounts) is created in and stays with the client's name.
- [ ] On termination, full handover is completed within [10] working days:
      repository, documentation, design sources, measurement archive, open
      task list.
- [ ] No additional fee is charged for handover; code or data is never withheld.
- [ ] Reference or portfolio use requires the client's written consent.

---

## 11. Personal data, confidentiality and regulation

- [ ] The privacy notice and explicit consent flow are part of the delivery.
      In Türkiye this is governed by KVKK (Law No. 6698); for organisations
      also subject to GDPR, both regimes must be addressed separately.
- [ ] Where form data goes and who can access it is written down.
- [ ] Analytics and tracking run only after consent.
- [ ] A data processing addendum is signed with the supplier acting as processor.
- [ ] Subcontractor use is notified in advance; the same confidentiality
      obligation applies.
- [ ] The cookie policy reflects the cookies actually in use.

---

## 12. Bid evaluation criteria

Weights are set by the client; a total of 100 points is suggested.

| Criterion | Weight | Note |
|---|---|---|
| Line-by-line acceptance of clause 4 criteria | [25] | A reason is requested where a threshold is not accepted |
| Verifiable work at a comparable scale | [20] | A live address and measurements are requested |
| Clarity of process and division of work | [15] | |
| Copyright, handover and exit clauses | [15] | |
| SLA and maintenance model | [10] | |
| Price | [15] | |

**Five verifying questions to ask the supplier:**
1. What is your own site's mobile Lighthouse score, and on what date was it
   measured?
2. Who owns the source code and design copyright on delivery?
3. If we part ways, what do you hand over, and within what period?
4. For which items do you use subcontractors?
5. If an acceptance criterion is missed, who pays for the correction?

---

## 13. Attachments

- [ ] List of current site addresses (indexed addresses)
- [ ] Brand guidelines / logo source files
- [ ] Sample product or service data source
- [ ] Existing measurement screenshots or reports
- [ ] Internal IT security requirements