Prepare a clear description of your business, the people you want to reach, the action they should take, and the content you already have. A short, specific brief is more useful than a long list of unrelated features.
Define the first version
- Audience: who buys from you, where they are based, and what they need to know before contacting you.
- Goal: choose the main action, such as sending a project brief, requesting a product quote, or viewing a menu.
- Pages: list the pages needed to support that action.
- Features: separate essentials from additions that could come later.
- Language: specify English, Arabic, or other requirements early.
Gather content and assets
Prepare your company description, service details, contact information, logo files, and photography you have permission to use. Include completed project examples and genuine customer feedback where available. Confirm who will write and approve the final copy.
For a product catalogue like Cobija Industries, useful inputs include product categories, descriptions, and manufacturing information. For a menu-led website like Happy Tea, category names and product imagery are central. These examples come from the different content structures documented in our client work.
A manufacturer's content checklist
- Products: the agreed categories, example products, and information buyers need to establish suitability.
- Capabilities: accurate materials, processes, customisation options, order requirements, and sampling information where relevant and suitable to publish.
- Evidence: usable product or facility photographs and any certifications or customer references you have permission to show. Do not supply unsupported claims.
- Contact: the person or inbox receiving quotation enquiries and the information a buyer should send.
- Approval: one person to confirm facts, image rights, final copy, and launch approval.
If the material is incomplete
Start with what you have: existing website text, a brochure, approved specifications, or images. Tell us what is missing. We agree the content list and responsibilities in the proposal, organise and lightly edit supplied material, and identify work that needs a separate writing or photography quote.
Agree how the material will be shared, who collects it, and when approvals are needed. We confirm the launch schedule after reviewing those dependencies; there is no fixed promise about the amount of time your team will need.
List systems and access requirements
Identify the domain registrar, hosting provider, existing CMS, email service, and any booking or payment services involved. At the enquiry stage, tell the developer which systems exist. Do not send passwords through a contact form; agree a secure access process when the project starts.
Choose one approval process
Nominate a person who can collect feedback from your team and make final decisions. Agree who approves the structure, visual design, content, and launch. Consolidated feedback makes a revision round clearer and avoids conflicting instructions.
Share your budget and timing
Give a useful range and explain whether the deadline is tied to a real event. State what content is ready and what is still missing. Website delivery depends on both implementation and timely decisions; the proposal should describe those dependencies.
A brief you can copy
“We are a [type of business] serving [audience and market]. We need a [new website/redesign] with [pages]. Visitors should be able to [main action]. We already have [content and assets], need help with [missing items], and use [existing systems]. Our budget is [range] and our preferred launch is [date].”
Compare your brief with our website scopes, then send it to Innowink. Need to replace an existing site? Review the redesign process and launch safeguards.