Corporate profile
Who you are, backed by facts a reader can check: founded, headcount, footprint, volume
the document that answers the question before the meeting does
Company profile design · UAE
Here a profile goes into a vendor registration or a tender file before anyone opens it in a meeting. Webzenia builds the credential block first and the story around it.
Get the structure your profile is missingWhat the document has to survive
Three readers meet the same document, in this order, and only the last of them reads it the way it was designed to be read. The first two are checking.
A registration file with named fields: the trade licence, the tax registration number, the ISO certificates, audited financials, the ICV score. It does not read; it checks whether something is there.
An evaluator scanning against criteria rather than reading for story. What cannot be found in one pass is treated as absent, which is why the credentials are laid out as a block and not mentioned in prose.
The one reader who opens it front to back, and only after the first two have already passed you. This is the reader the whole category designs for, and the third one to arrive.
What we design
Six documents that share a name and almost nothing else. The reader decides the length, the order, the language and the format.
Who you are, backed by facts a reader can check: founded, headcount, footprint, volume
the document that answers the question before the meeting does
The capability statement a registration wants: competencies, the licence and its issuing authority, the TRN, the ISO set and evidenced past performance
a file that answers the checklist
The business framed for a reader who will verify every line: trajectory, structure, exposure and the people accountable
a document that survives diligence
Plant, throughput, tolerances and certification laid out for a buyer or an auditor rather than a browser
the document an overseas distributor asks for first
The work carrying the argument, with the thinking beside it rather than under it
a profile that reads as a shortlist of proof, not a gallery
A bookmarked, linked version sized to upload and navigable without scrolling twenty pages
the copy that goes into a portal and into an inbox
What you are actually buying
A Business Bay consultancy on a DET mainland licence and a Musaffah contractor are usually sold the same thing. Only one of them can use it.
| A brochure about the companyWritten to impress a reader | A capability statementWritten to explain what you do | A prequalification dossierWritten to answer a checklist | |
|---|---|---|---|
| Who reads it | A prospect, briefly, after they have already decided to meet you. | A buyer working out whether you do the thing they need. | An evaluator with a form, looking for named fields in a fixed order. |
| What it has to prove | That you take yourselves seriously. | That the capability is real and the scope fits. | That the entity, the registrations and the record all exist and are current. |
| If a certificate expires | Nobody notices, because nothing in it was checkable. | A line goes stale and the document still circulates. | One page is reissued, because the credentials were designed as a block. |
| How long it stays true | Until the photography dates it, which is sooner than anyone plans for. | Until the services change. | As long as the register behind it is kept, which is an edit rather than a rebuild. |
| At a registration | It is uploaded, and then everything is asked for again separately. | Most of it is there, in the wrong order. | It is the file, and the fields are where the form expects them. |
If nothing you are chasing needs a registration, the middle column is the honest answer and we will say so rather than sell you the third. If you are going onto a vendor list, and in Abu Dhabi that is how most work is bought, the third is not a longer version of the second: it is a different document with the credential block designed first. Most firms end up with one document that behaves as both. Where the profile is one output of an identity engagement rather than a commission of its own, that is branding in Dubai.
The UAE context
Webzenia has worked with Gulf clients since 2018. Four things decide whether a profile does its job here, and none of them is the cover.
An ADNOC supplier prequalification is centralised across the whole group and ADNOC puts the timeline at 90 days, evaluated on three completed projects with values, a quality management system to ISO 9001 or equivalent, and HSE documentation. A Musaffah contractor on an Abu Dhabi mainland licence plans for that window.
A company bidding with ADNOC, Abu Dhabi government entities or a participating federal or semi-government body is scored on its MoIAT National ICV certificate as a line item in the evaluation. A profile that mentions ICV in a sentence has buried the one line an evaluator was sent to find.
They belong on the cover and in one designed block, taken from your own documents rather than retyped from a brief. A Jebel Ali manufacturer on a free zone licence is judged on that block by an overseas distributor long before anyone reads what the company believes.
The entity reading it may work in Arabic, and the layout has to be composed for it rather than reflowed into a grid drawn for Latin. We scope the Arabic version in the same breath as the English one, or say plainly that the engagement does not include it.
What the engagement covers
Six parts, starting with the documents rather than the brief. What you can evidence decides what the profile is allowed to say.
We collect the licence, the TRN, the certificates, the registrations held and the project record from your own documents, and note what has an expiry date attached to it.
The page order is set by what the reader verifies first, so the fields a form asks for are found in one pass rather than hunted for across a narrative.
Every spread is designed on your existing identity rather than a house template, with the hierarchy weighted so a long document stays readable at speed.
Capacity, coverage and the project record become visuals a reader can take in at a glance. Where photography is needed we say who shoots it rather than quietly assuming a library.
One design leaves as a print booklet, a bookmarked interactive PDF and a version sized and named for an upload field that will reject anything heavier.
The editable source in your name, with the credential block built so a renewed certificate is a field change. A renewal should not arrive as an invoice from us.
Our stack
The kit behind a long document a checker can navigate and your team can keep current. Select one to see why it earns its place, and what we do with it that most do not.
A profile is a long document, and long documents are a machinery problem: master pages, paragraph styles, a contents page that renumbers itself and a credential table that holds its shape when a line grows.
We build the credential block as styled table rather than as artwork, so replacing an expired certificate line is a text edit your own team can make without the layout moving.
How the work runs
The order starts with the documents. What a profile is allowed to claim is decided by what you can put behind it, so that comes first.
We work from your licence, certificates, registrations and project record rather than from a questionnaire, and we confirm what the registration or the tender actually requires. Where a certificate is missing or lapsed, you hear it here, while it is still a scheduling problem rather than a rejected submission.
The page order is fixed against what the reader verifies first, the credential block is laid out as a designed object, and the record becomes evidence a scan can take in. Where Arabic is in scope it is composed in parallel rather than retrofitted into a grid drawn for Latin.
A print booklet, a bookmarked interactive PDF and a portal copy sized to clear an upload field all come from the one design. The editable source and the credential register go with them, in your name, so the next certificate renewal is a field change rather than a fresh commission.
You receive the source and the credential register, so a renewed certificate never needs us.
Our commitment
A profile fails when a claim is checkable and wrong, when the credentials are buried, or when nobody can update it. These four are about that.
Nothing goes in unchecked
Where a claim cannot be evidenced from a document you hold, it is cut or reworded, and we say which. An evaluator who catches one unverifiable line reads the rest of the file differently.
Credentials come from your documents
The licence number, the TRN, the certificate numbers and the dates are taken from the source documents and checked back against them, never retyped from a brief. A transposed digit in a registration number is an error nobody proofreads for.
One design with proper Arabic
The print booklet and the interactive PDF come from one design rather than being rebuilt, and where Arabic is in scope it is set as its own composition. We will not run English copy through a translation and call the document bilingual.
Renewals are simple edits
You receive the editable file, the exports and the credential register in your own name. A certificate renewed in March should be a field change your team makes that afternoon, not a line item on a quotation.
Common questions
Keep exploring
Marks, a bilingual system, and the files your team can run.
A position your licence supports and a buyer can verify.
A mark drawn in both scripts, and made to be fabricated.
A deck built for the pocket of capital reading it.
One master that sets decks in both directions.
A master set your own team can fill, in both scripts.
Written twice, because a committee watches it twice.
One permitted shoot, cut for every place it sells.
Shot to two marketplace specs, against the sellable pack.
Next step
Send the profile you have and the registration or tender it has to go into. We will come back with the structure and the credentials it needs to carry.
Tell us what you need.