Websites where every claim can be checked
Bilingual company sites and web apps built from a content model you own, where every fact on the page traces to one checked file.
- Languages
- Arabic and English, right-to-left designed in
- Hosting
- In your account, under your company's name
- Content
- Held as structured data, not locked in a page builder
- Proof
- The site you are reading is one we built
A company website in this market is read by procurement officers checking whether you are real. We build bilingual Arabic and English sites from a content model you own, with one page per service, facts that can be verified and forms that reach a named person.
- 01 Enquiry
- 02 Systems audit
- 03 Specification
- 04 Build
- 05 Pilot
- 06 Deploy
- 07 Handover
- 08 Support
Websites where every claim can be checked sits at step 4 of the build cycle. You receive a working increment you can use.
Procurement reads your site first
Before a vendor registration is approved or a tender is shortlisted, somebody opens your website.
They check that the company exists, that its registration matches the work in the tender, and that the services you quote for are services you describe. A two-page template with a stock photograph and "0+ projects" in a counter fails that check quietly. Nobody tells you. You simply are not called.
The fix is depth, not decoration: a real page per service, stating what you do, how the work runs and what you hand over.
Pages that earn their place
A page exists because a buyer has a question it answers. A location page that swaps one city name for another is worse than no page, so the page map leaves it out.
| Page type | Why it exists | What it must contain |
|---|---|---|
| Service page | Answers one buyer question in depth | What the work is, the steps and what you hand over |
| Sector page | Speaks one industry's language | The records, regulators and customers of that industry |
| Location page | Only where you have something local to say | Named zones, the local regulator, how you cover it |
| Guide | Catches the search before the buyer knows you | The answer in the first 60 words, then the detail |
| Contact | Gets the enquiry to a named person | A short form and what happens next |
| Web app | Where the site has to do something: route a quote request, build a scope, take a booking | A data model written down and handed over like any other application |
Yours at launch
The site source
In your repository with its history, so the next developer starts from the real thing.
Accounts in your name
Hosting, domain and analytics opened in your company's name, so nothing sits in a supplier's account.
The content model
Every page type and every field, documented, so most edits are a field rather than a page.
The facts file
The legal name, the CR number, the cities you cover and every other checkable fact, each with the source it was checked against.
The page map
Every page listed against the buyer question it answers.
The editing guide
Written for whoever maintains the content, usually a marketing or admin coordinator.
How a site gets built
- 01
The page map
One page per service you actually deliver, sector pages where you have an industry to speak to, and the buyer question each page answers. Agreed before any design.
- 02
One fact, one place
The company facts live in one file, and pages read from it. Change the CR number once and every page that cites it changes. A block whose fact is unconfirmed stays off the page, with no placeholder, bracket or "coming soon" in its place. The site you are reading keeps its company facts this way.
- 03
Copy with your people
Written with the person who does the work, because the substance is theirs.
- 04
Arabic laid out, then written
Right-to-left is a layout, not a translation. Menus, tables, icons with direction and number formats mirror or hold on purpose. Arabic copy is written or reviewed by a native reader before it is published.
- 05
Your content owner approves
Every page goes to your named content owner before it goes live. Their approval is recorded against the page, and publishing waits for it.
- 06
Launch in your accounts
Hosting, domain and analytics opened in your company's name, and every form tested through to the named inbox it routes to.
Twelve services in one paragraph
An industrial services contractor with its office in Khobar has an English-only template site with a single Services page listing twelve services in one paragraph.
A prospective client's procurement team cannot tell whether it does the scope in their tender. The page map comes first: one page per service the contractor actually delivers, two sector pages, and no city pages, because it has nothing local to say beyond its Khobar office.
The facts file holds the legal name, the CR number and the cities the contractor covers, each checked against the CR certificate. Copy is written with the contractor's operations lead, in Arabic and English. The enquiry form routes by service to a named inbox.
Hosting, the domain and the analytics account are opened in the contractor's own name. The contractor holds the site source, the content model, the page map and an editing guide its marketing coordinator can follow.
What owners ask before a rebuild
WordPress or custom?
Whichever you can maintain. If your team will edit pages weekly and wants a familiar editor, a well-built WordPress site is a sensible answer. If the site is mostly structured service content and speed matters, a static build from a content model is lighter and cheaper to host. We explain the trade before you choose.
Can we edit it ourselves?
Yes. The editing guide is written for your coordinator, and the content model means most edits are a field, not a page.
Can you guarantee search rankings?
Nobody can honestly guarantee a ranking. What we build is what search engines and buyers both reward: a page per real question, answered in the first paragraph, with structure a crawler can read.
Who writes the content?
We do, with your people, because the substance is theirs. A site written without the person who does the work reads like it.
Is this site built the same way?
Yes. Its company facts sit in one file, its pages are built from a content model, and a block waits off the page until the fact behind it is confirmed.
What drives the cost?
The number of distinct pages, how much content exists already, the Arabic volume, whether any page needs a working web app, and whether we migrate an old site's content.
Often the same project
Internal tools and portals
When the site needs a working part: a client portal, a lookup or a booking flow.
Read moreDigitalDocument and report generation
Proposals and reports produced from the same facts and records the site reads.
Read moreCyberSecure development
The review gates and dependency rules for software you build or buy, with ITF Cyber.
Read morePart of one system
Every division keeps records to the same standard, so the second one you need works the way the first one did.
Start with the page map
Bring your current site, your CR certificate and the list of services you actually deliver. The scoping call turns them into a page map, one buyer question per page.