Begin with verified business facts
Prepare the correct legal or trading name, contact details, physical location where applicable, service areas, registration information, operating hours and preferred communication methods. These details should be consistent across the website, business listings and formal documents.
Conflicting phone numbers, addresses or business names weaken trust and can create technical SEO problems. Decide which details are current before they are added to headers, footers, forms and structured data.
Define the purpose of the website
The content should support a clear purpose. A website may generate enquiries, explain programmes, sell products, accept applications, publish resources, attract donors or support existing customers. Different goals need different pages and calls to action.
Write a short statement explaining what a successful visitor should understand and do. This becomes a useful guide when deciding what content belongs on the website.
Prepare the homepage message
The homepage needs a clear explanation of who the business helps, what it provides and where it operates. Avoid beginning with general phrases that could describe any company. The opening should help the right visitor recognise that they are in the correct place.
Useful homepage content may include the main services, a brief reason to trust the business, selected project evidence, a simple process and direct pathways to contact or request a quotation.
Create a complete service list
List every service that should appear on the website, then group related services. For each important service, prepare answers to the following:
- What is the service?
- Who is it for?
- What problem does it solve?
- What is included?
- What information must the client provide?
- What affects the price or timeline?
- What happens during delivery?
- What happens after completion?
- What should the customer do next?
This information is more useful than a short list of service names. It also helps determine which services need dedicated pages.
Collect company background information
An About page should include relevant history, mission, values and working approach. It does not need to tell every detail of the company’s story. Focus on information that helps a prospective client understand the organisation and assess whether it is suitable.
Only include awards, certificates, team numbers, years of experience and achievements that can be verified. Unsupported claims may create credibility problems.
Prepare customer and project evidence
Client names and logos
Confirm that the business has permission to display each logo. Map every file to the correct client name and avoid guessing from unclear filenames.
Portfolio projects
For each project, record the client, service delivered, project objective, completion status and live URL. Where possible, prepare approved screenshots. Do not claim specific results unless they are documented.
Testimonials
Testimonials should be genuine, attributed correctly and approved for publication. Keep the original meaning and avoid rewriting the statement into a stronger claim than the customer made.
Organise visual assets
Prepare the company logo in a high-quality format, brand colours, fonts, team photographs, workplace images, product photographs and project screenshots. Use original images where possible. Images should be clear, relevant and legally available for use.
Rename image files descriptively and keep a record of what each image shows. This helps developers place them correctly and write accurate alternative text.
Prepare contact and conversion information
Decide how visitors should contact the business. Options may include phone, WhatsApp, email, a quotation form or a booking form. Each form should request only the information needed to respond meaningfully.
Also define who receives enquiries, how quickly the business normally responds and what happens after a form is submitted. Do not promise response times that the team cannot maintain.
Prepare product information for e-commerce
An online store requires more than product names. Prepare categories, descriptions, prices, variants, stock information, photographs, delivery areas, payment arrangements, return policies and customer-support details.
Product data should be consistent. Unclear pricing, missing images or incomplete delivery information can delay development and create customer confusion after launch.
Prepare organisation and NGO content
Organisations may need mission, programmes, geographic coverage, leadership, governance, reports, publications, partners, events, donation information and beneficiary stories. Confirm which information can be published and how sensitive data will be handled.
Collect frequently asked questions
Ask staff which questions customers repeat before buying. Useful FAQs often cover prices, timelines, service areas, requirements, payment stages, support and what is excluded. Real questions can improve both service pages and the enquiry process.
Prepare legal and policy information
Depending on the website, the business may need privacy information, website terms, cookie information, return and refund policies, delivery terms or service conditions. These documents should reflect actual business practices. Generic templates should not be published without review.
Assign content responsibilities
Choose one person to coordinate content, collect approvals and provide consolidated feedback. When several people send separate versions, the project can become inconsistent and slow.
Use a simple content tracker with the page name, responsible person, status, source material and approval date. This makes missing information visible.
A practical pre-development checklist
- Confirmed company name and contact details
- Website goals and target audience
- Approved service list
- Company background and values
- Logo and brand assets
- Original photographs and project images
- Verified client and portfolio information
- Form requirements and recipient details
- Product data where applicable
- Policies and legal information
- Domain and hosting access
- One person responsible for approvals
Do not delay every decision until design begins
Design can help organise information, but it cannot replace missing facts. When content preparation begins early, layouts can be designed around real messages rather than placeholders. This usually leads to fewer revisions and a website that is more useful at launch.
Write for customer questions, not internal departments
Businesses often organise information according to their internal structure. Customers usually think in terms of problems, outcomes and decisions. A page called “Operations Division” may mean little to a new visitor, while a page explaining the relevant service and who it helps is clearer.
Review every proposed page from the visitor's perspective. The heading, opening paragraph and call to action should make sense without requiring prior knowledge of the organisation.
Plan content for search without forcing keywords
Search-focused content begins with a real question or need. Assign one primary topic to each important page and include closely related explanations naturally. Do not create several pages that answer the same question with slightly different wording. This can confuse visitors and create keyword cannibalisation.
Titles and descriptions should accurately preview the page. The content must then deliver on that promise. Useful local context can include service areas, customer processes and practical Malawi considerations, but location names should not be repeated artificially.
Prepare content for mobile reading
Many visitors will scan the website on a small screen. Break long explanations into clear sections, use meaningful headings and keep important contact actions visible. Avoid placing essential information only inside an image, PDF or decorative slider.
Forms should be short enough to complete on a phone. When more detail is required, use conditional fields or collect it during the next conversation.
Create an approval and update process
Content becomes outdated when nobody owns it after launch. Assign responsibility for prices, services, staff information, contact details, policies and news. Set review dates for important pages and keep the source documents used to verify claims.
A website is more trustworthy when information remains current. Content governance should therefore be considered part of the project, not an optional activity after launch.
Frequently asked questions
Can a website project begin before all content is complete?
Yes, but the structure, responsibilities and content deadlines should be agreed early so missing information does not delay design, review or launch.
Should website text be copied directly from a company profile?
A company profile can provide source information, but website copy usually needs to be reorganised around visitor questions, page purpose and clear actions.
Who owns photographs and written content supplied for a website?
Ownership depends on how the material was created or licensed. Businesses should only supply content they have permission to publish.
How much text does a business website need?
The amount depends on the service, search intent and user questions. Each page should be complete and useful rather than padded to reach an arbitrary length.
