Request for Consultancy Service Corporate Website Development

About Us Ethio-BioPharma Enterprise (EBPE) is Ethiopia’s state-owned pharmaceutical manufacturing enterprise, established to build the nation’s capacity to manufacture vaccines, essential medicines, diagnostics, medical supplies and other healthcare technologies locally. Operating under EIH, EBPE is developing an integrated pharmaceutical campus at the Kilinto Special Economic Zone in Addis Ababa, co-locating multiple manufacturing units that share infrastructure, talent, and corporate services.

1. Job Summary

Ethio-BioPharma Enterprise (EBPE) is a state-owned enterprise dedicated to the research, development, and manufacturing of vaccines, diagnostics, medicines, and other health technology products to serve national and regional health needs. EBPE was established by the Federal Democratic Republic of Ethiopia Council of Ministers Regulation No. 536/2023 and the Ethiopian Investment Holdings (EIH) Board of Directors Resolution of August 16, 2025. Its production facilities are located at the Kilinto Special Economic Zone in Addis Ababa, Ethiopia.EBPE operates under a broad mandate covering the development and supply of vaccines, essential medicines, in-vitro diagnostics, and medical supplies. The enterprise is at an active stage of institutional build-out: the ShieldVax fill-finish facility is under construction, and EBPE is advancing product and technology partnerships with international manufacturers and technology transfer partners. It engages regularly with the Ministry of Health, Industry Park Development Corporation, multilateral development partners, and prospective investors.A credible and functional corporate website is a necessary component of EBPE's external communications infrastructure. It will serve as the primary digital reference point for a range of audiences, including prospective technology transfer partners, investors, public health counterparts, development finance institutions, and the general public. At present, EBPE does not have an operational website, which limits the enterprise's visibility and makes it more difficult to communicate its mandate, capabilities, and strategic direction to these audiences.2.Purpose of the ConsultancyThis document sets out the scope, objectives, requirements and deliverables for the EBPE corporate website development assignment, and the information that invited firms must provide in order to submit a responsive proposal.Sections 1 to 6 describe the assignment: its background, objectives, scope of work, technical and functional requirements, and the deliverables expected at each phase. Sections 7 to 11 set out the implementation period, the eligibility requirements, the contents of the technical and financial proposals, and how proposals should be submitted and will be assessed.Invited firms should read the whole document before preparing a proposal. The firm selected under this process will be referred to as the Consultant and will be engaged under a written contract with EBPE.

1. Objectives

The assignment has the following objectives:

1. Design and develop a professional corporate website that accurately represents EBPE's mandate, institutional profile, product portfolio, and strategic priorities.
2. Provide an accessible, multilingual digital platform through which EBPE can communicate with investors, technology partners, government counterparts, public health stakeholders, and the general public.
3. Build an information architecture that can grow with EBPE, accommodating new products, partnerships, and institutional developments without requiring structural redesign.
4. Deliver a website that meets current standards for performance, security, accessibility, and search engine visibility.
5. Provide a channel for communication with diverse stakeholders, including government bodies, international health partners, technology transfer partners, investors, and the general public.
6. Support future growth by building in scalability for integration with other digital platforms, additional languages, and new content areas as EBPE's activities expand.
7. Transfer sufficient knowledge, documentation, and technical access to EBPE staff to enable the enterprise to manage and update website content independently after handover.

4. Scope of Work: The assignment covers all activities from initial planning through post-launch support. The Consultant is responsible for the activities described below.4.1 Planning and Requirements finalization

• Conduct a structured requirements workshop with EBPE to confirm website objectives, target audiences, key user journeys, content priorities, and the full functional scope.
• Review EBPE's existing brand materials, including the official EBPE logo, color palette, typography, and any approved visual identity or communications guidelines. The EBPE logo and other brand assets will be provided by EBPE for integration into the website.
• Agree on the technology stack, hosting environment, and content management system with EBPE before commencing design work.
• Prepare and submit a project plan covering all activities, responsibilities, milestones, review points, and the overall timeline for EBPE's approval.

4.2 Information Architecture and Sitemap

• Develop a proposed sitemap covering all main sections and subsections of the website.
• Define the navigation structure, page hierarchy, and URL scheme.
• Present the proposed information architecture to EBPE for review and approval before proceeding to design

4.3 Design

• Develop wireframes for all key page templates, including (at a minimum) the homepage, about section (covering mandate, leadership, and organizational structure), product and capability pages, news and announcements section, partner and stakeholder section, investor information section, contact page, and any other sections agreed with EBPE during the planning phase.
• Develop high-fidelity visual design mockups based on approved wireframes, incorporating EBPE's official logo and brand identity. The design must reflect EBPE's role in the health and pharmaceuticals manufacturing sector through a clean, professional layout.
• Conduct design review sessions with EBPE and revise as necessary. A minimum of two review rounds is expected before final design approval.
• Prepare a style guide documenting the EBPE logo usage rules, typography, color usage, spacing, iconography, component standards, and design tokens, for reference throughout development and future updates

4.4 Development

• Build the website in accordance with approved designs and the requirements set out in Section 5, using a widely supported, secure CMS platform (such as WordPress, Drupal, or an equivalent agreed with EBPE).
• Configure and customize the CMS to enable EBPE staff to create, edit, and publish content without technical support.
• Implement all functional requirements, including the content sections listed in Section 5.11, multilingual content support (English and Amharic at minimum), contact and inquiry forms, a news and announcements module, a document and media library, and integration with analytics and other agreed services.
• Integrate social media links and social sharing functionality connecting the website to EBPE's official accounts on agreed platforms.
• Develop a partner and stakeholder section providing relevant information for government bodies, international health organizations, and prospective partners.
• Configure secure hosting setup, including server hardening, access controls, and environment-level security settings, in coordination with EBPE.
• Ensure all code is clean, well-commented, and maintained in a version-controlled repository throughout development.
• Develop the website in a staging environment for EBPE review and approval before deployment to production.

4.5 Content Population

• Work with EBPE to receive, organize, and integrate approved content into the website, including institutional text, product and service descriptions, imagery, documents, and other media.
• Provide EBPE with content templates and editorial guidance for any sections where content has not been finalized at the time of development.
• Flag any content gaps, inconsistencies, or missing assets to EBPE for resolution before launch.

4.6 Testing

• Conduct comprehensive functional testing across all pages, forms, navigation elements, and interactive features to confirm that all specified requirements are met.
• Conduct cross-browser and cross-device compatibility testing covering current versions of all major browsers (Chrome, Firefox, Microsoft Edge, and Safari) and a representative range of screen sizes, from large desktop to small mobile.
• Conduct performance testing and optimize load times to meet the benchmarks set out in Section 5.8.
• Conduct User Acceptance Testing (UAT) with EBPE staff prior to final sign-off, providing a structured walkthrough of all website functions and incorporating any feedback before the website is considered ready for deployment.
• Prepare and share a consolidated test report with EBPE documenting all test categories, test cases, results, and issues resolved prior to launch.

4.7 Deployment

• Configure the production hosting environment and deploy the completed website.
• Set up domain configuration, SSL/TLS certificates, and DNS settings in coordination with EBPE.
• Configure staging and production environments to enable future updates to be tested before going live.
• Complete a pre-launch checklist covering content accuracy, broken links, form functionality, SEO metadata, analytics tracking activation, performance benchmarks, and security configuration.
• Formally hand over the live website to EBPE following written sign-off

4.8 Documentation, Training and knowledge Transfer

• Prepare technical documentation covering the website architecture, technology stack, configuration settings, deployment procedures, and ongoing maintenance requirements.
• Prepare a CMS user guide covering content creation and editing, media management, user account administration, and routine CMS operations.
• Deliver a minimum of two hands-on training sessions for EBPE staff responsible for website administration and content management, tailored to the technical experience of the relevant staff.
• Transfer all source code, credentials, configuration files, theme files, plugin licenses, and related materials to EBPE at the point of handover, with clear documentation of each item.

4.9 Post Launch support

• Provide a support period of no less than six months from the go-live date, during which the Consultant will respond to and resolve any defects, bugs, or technical issues reported by EBPE. Critical issues should receive a response within one business day.
• Conduct a post-launch review at the end of the support period to assess website performance against agreed benchmarks and identify recommended enhancements for EBPE's consideration.

1. Functional and Technical Requirements

• The website must meet the requirements set out below. Where a requirement refers to an industry standard or benchmark, compliance must be demonstrated through testing before the website is accepted by EBPE.

5.1 Website Architecture The website must be built on a stable, widely supported technology platform appropriate to EBPE's operational context and internal technical capacity. The platform must be agreed with EBPE before development begins. Requirements include:

• A modular page structure that allows sections to be added, removed, or reordered without requiring bespoke development work each time.
• A clean separation between the content layer and the design layer, enabling template or theme updates without disrupting published content.
• A sitemap and URL structure that is logical, human-readable, and supports SEO.
• Clearly separated staging and production environments with documented deployment procedures.
• Compatibility with the hosting environment and any existing infrastructure agreements held by EBPE

5.2 User Experience and Responsive Design

• The website must render correctly and perform well on desktop, tablet, and mobile devices without the use of a separate mobile site or mobile-specific subdomain.
• Navigation must be intuitive and consistent, with a clear visual hierarchy, predictable placement of menus and calls to action, and a search function accessible from all pages.
• Page layouts must accommodate varying content lengths without visual breakage or degradation.
• All interactive elements, including forms, buttons, links, dropdown menus, and file download triggers, must be clearly identifiable and function consistently across devices and browsers.

5.3 Content Management

• The website must be built on a widely used, secure, and well-supported CMS platform (such as WordPress, Drupal, or an equivalent) that allows authorized EBPE staff to create, edit, publish, and unpublish content without developer involvement. The specific platform must be agreed with EBPE during the planning phase.
• The CMS must support role-based access control with at minimum two user levels: editor (who can draft and submit content for review) and administrator (who can publish, manage user accounts, and configure CMS settings).
• The CMS must support scheduled publishing, allowing content to be set live at a predetermined date and time.
• The CMS must include a media library for uploading, organizing, and managing images, PDFs, videos, and other file types, with basic editing and metadata functionality.
• Content editing must be possible through a visual interface that does not require knowledge of HTML or code, while still allowing structured entry of SEO metadata, custom URLs, and other page-level settings.

5.4 Multilingual Capability

• The website must support content in at minimum two languages: English and Amharic. The architecture should allow additional languages to be added without structural changes.
• Language switching must be available from a consistent, prominent location on every page.
• The CMS must allow content to be created, edited, and published independently in each language, without requiring content in one language to be a direct translation of another.
• The URL structure for multilingual content must follow a standard convention, such as /en/ and /am/ language prefixes, to support independent indexing by search engines.
• Text direction, Amharic script rendering, and font display must be tested and confirmed functional before launch.

5.5 Cybersecurity

• All data transmitted between users and the website must be encrypted using a valid SSL/TLS certificate (HTTPS). The website must be configured to redirect all HTTP traffic to HTTPS.
• The CMS must enforce strong password requirements and support two-factor authentication for administrator-level accounts.
• All CMS software, themes, and plugins must be current and free of known critical vulnerabilities at the time of launch, and the Consultant must apply security patches promptly throughout the post-launch support period.
• File upload functionality, where included, must be restricted to approved file types and scanned for malware before content is processed or stored.
• HTTP security headers (including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options) must be configured and tested before launch.

5.6 Search engine Optimization

• Every page must support individually editable meta titles and meta descriptions through the CMS.
• The website must generate an XML sitemap submitted to major search engines, and a robots.txt file, both correctly configured at launch.
• URL paths must be descriptive and human-readable, without auto-generated numeric identifiers or session parameters.
• All image fields must include an editable alt text attribute accessible through the CMS.
• The website must implement structured data markup (schema.org) for relevant content types, including the organization profile and news articles.
• Canonical URLs must be configured to prevent duplicate content issues arising from URL variations.
• The website must achieve a passing score on Google's Core Web Vitals assessment before handover.
• The website must meet the “Good” thresholds for all applicable Core Web Vitals metrics and achieve a “Good” Web Vitals assessment before handover

5.7 Analytics

• The website must be integrated with Google Analytics 4 (or an alternative agreed with EBPE) before launch, with tracking confirmed functional across all page types.
• Event tracking must be configured to capture key user actions, including form submissions, document downloads, video plays, and clicks on external links.
• A standard reporting view or dashboard must be configured so that EBPE staff can monitor basic website traffic metrics without requiring specialist analytics knowledge.
• The Consultant must provide a brief written guide explaining how to read and use the analytics reports.

5.8 Performance

• The website must achieve a Google PageSpeed Insights score of at least 80 on mobile and 90 on desktop, tested on the live production environment before handover.
• Images must be compressed and served in modern formats (WebP or equivalent) without visible quality degradation, with appropriate responsive image sizing.
• Static assets, including CSS, JavaScript, and web fonts, must be minified and served with appropriate browser caching and compression headers.
• Content delivery through a CDN should be implemented where this is consistent with EBPE's hosting approach and security requirements.

5.9 Backup and recovery

• Daily automated backups of both the website files and the database must be configured and active before the go-live date.
• Backups must be stored in a location separate from the primary hosting server.
• The restoration process must be documented, tested, and confirmed functional before handover.
• EBPE staff responsible for website administration must be shown how to initiate a manual backup and how to restore the website from a backup in the event of failure

5.10 Scalability

• The website architecture must accommodate the future addition of new sections, language versions, content types, and product pages without requiring structural redesign or significant redevelopment.
• The hosting environment must support traffic growth and be configurable to scale server resources during periods of elevated demand.
• The CMS must remain performant as the volume of content and the number of registered users grows over time.

5.11 Website Content Sections

• The website must include the following content sections as a minimum. Additional sections may be agreed with EBPE during the planning phase.
• • Homepage: institutional overview, mission, and key calls to action.
  • About EBPE: mandate, establishment, vision and mission, organizational structure, and leadership profiles.
  • Products and capabilities: information on the EBPE product portfolio (vaccines, diagnostics, medicines, medical supplies) and manufacturing capabilities.
  • News and announcements: a regularly updated section for institutional news, press releases, and updates.
  • Partners and stakeholders: information for government counterparts, international health organizations, technology transfer partners, and investors.
  • Social media integration: visible links to EBPE's official accounts on agreed social platforms, with optional social feed display.
  • Contact and inquiries: contact details and inquiry forms for general, partnership, and media inquiries.
  • Document library: a repository for publicly available institutional documents such as annual reports, policy documents, and publications.

• • 6. Expected Deliverables

The following deliverables are expected from each phase of the assignment. Where approval is required, the next phase may not commence until EBPE has confirmed approval in writing.PhaseDeliverablesApproval requiredPhase 1: Planning

• Requirements documentation (objectives, audiences, user journeys, functional scope)

• Technology stack recommendation with rationale
• Project plan (activities, milestones, responsibilities)

Project plan requires EBPE approval before design commencesPhase 2: Architecture and design

• Sitemap and navigation structure
• Wireframes for all key page templates

• High-fidelity visual design mockups (minimum two homepage concepts)

• Style guide

Sitemap, wireframes, and final design each require EBPE approval before proceedingPhase 3: Development

• CMS installation, configuration, and role-based user setup

• Fully functional website in staging environment (all sections, forms, and integrations active)

• Social media integration and partner/stakeholder section

• Third-party integrations (analytics, contact forms, others as agreed)

• Version-controlled code repository

EBPE review and sign-off on staging build before deploymentPhase 4: Testing

• Functional test report
• Cross-browser and cross-device compatibility report
• Performance report (PageSpeed Insights scores)
• User Acceptance Testing (UAT) completion record, signed off by EBPE

All critical and high-severity findings must be resolved before deploymentPhase 5: Deployment

• Live website on production environment
• DNS and SSL configuration
• Active staging environment for future updates
• Completed pre-launch checklist
• Formal handover with EBPE written sign-off

Written sign-off from EBPE required before the assignment is considered completePhase 6: Documentation and training

• Technical documentation (architecture, stack, configuration, maintenance)
• CMS user guide
• Minimum two hands-on training sessions for EBPE staff

• Full transfer of source files, credentials, licenses, and configuration data

EBPE to confirm receipt and adequacy of all transferred materialsPhase 7: Post-launch support

• Bug fixes and issue resolution throughout the support period (minimum six months)
• Post-launch performance review report

• List of recommended enhancements based on post-launch experience

Post-launch review report submitted to EBPE at end of support peri

1. Implementation Period

The assignment must be completed within 60 calendar days from the date of contract signature to the go-live date, followed by the post-launch support period of not less than six months required under Section 4.9.Proposals submitted by the consultant/consulting firm must include a work plan showing how the phases and deliverables in Section 6 fit within this period, and must identify the inputs required from EBPE and the points at which EBPE approval is needed.The assignment must be completed within 60 calendar days from the date of contract signature to the go-live date, followed by the post-launch support period of not less than six months required under Section 4.9.Proposals submitted by the consultant/consulting firm must include a work plan showing how the phases and deliverables in Section 6 fit within this period, and must identify the inputs required from EBPE and the points at which EBPE approval is needed.

1. Eligibility and Qualification Requirements

Proposals will be considered only from firms that meet all of the following requirements. Supporting evidence must be submitted in accordance with Section 9.3.

• Legally registered and holding a valid, renewed trade or business licence covering information technology, software development, or website development services.
• Registered for tax purposes and able to provide a valid tax clearance certificate.
• At least three years of continuous experience in website design and development.
• At least three corporate or institutional websites completed and live within the last five years, each supported by a working URL and a contactable client reference.
• Demonstrated capability to deliver and test Amharic language content, including script rendering and font display, as required under Section 5.4.
• A team covering, at a minimum, project management, development on the proposed CMS platform, user interface and user experience design, testing, and hosting and security configuration.
• Able to complete the assignment within the period set out in Section 7 and to provide the post-launch support required under Section 4.9.

1. Submission Requirements

• Each firm must submit a technical proposal, a financial proposal, and the supporting documents listed below. The technical proposal and the financial proposal must be provided as separate documents, and the technical proposal must not contain any pricing information

9.1 Technical Proposal

• A statement of the firm’s understanding of the assignment, together with any comments on the requirements in Sections 4 and 5.
• The proposed technical approach, including the recommended technology stack, CMS platform and hosting arrangement, with the reasons for each choice.
• A work plan and schedule covering the phases and deliverables in Section 6, showing milestones, review points and the inputs required from EBPE.
• A point-by-point response to the functional and technical requirements in Section 5, stating for each requirement whether it will be met in full and how.
• The proposed team, showing the role, relevant experience and level of input of each member, with curricula vitae for the key staff.
• A portfolio of at least three completed corporate or institutional websites, with live URLs, client names, and contact details for references.
• The approach to testing and quality assurance, and to cybersecurity as required under Section 5.5.
• The approach to documentation, training and knowledge transfer, and the post-launch support arrangements offered, including the response time for critical issues.

9.2 Financial Proposal

• A total lump sum price in Ethiopian Birr for the full scope of work in Section 4, inclusive of all taxes and charges other than VAT, which must be shown separately.
• A breakdown of the total price by the phases listed in Section 6.
• A breakdown of professional fees by staff category, showing the daily rate and the number of days for each.
• Any other direct costs, itemised.
• Annual costs for hosting, domain registration, SSL or TLS certificate, and any commercial theme, plugin or third-party licences, quoted separately. These are provided for information and are not part of the lump sum price.
• A separately quoted price for an extended maintenance and support package of twelve months beyond the support period required under Section 4.9.
• The period for which the quotation remains valid, which must be not less than [60] calendar days from the submission date.

9.3 Supporting Documents

• Certificate of business registration or equivalent incorporation document.
• Renewed trade or business licence for the current year.
• Taxpayer identification number (TIN) certificate, and VAT registration certificate where applicable.
• Valid tax clearance certificate.
• Company profile.
• A signed cover letter confirming acceptance of the requirements in this document and the validity period of the quotation, signed by a person authorised to bind the firm.
• 10. Submission Address

ItemDetailSubmit toEthio-Biopharma Enterprise, ebpe@ethiobiopharma.etDeadline for submission30 September 2026Deadline for questions20 September 2026Email subject lineProposal – EBPE Corporate Website DevelopmentFormatTechnical proposal and financial proposal as separate PDF files; supporting documents may be combined into a single PDFLanguageEnglishQuestions on this document may be sent to the same address by the date shown above. Responses will be shared with all invited firms.EBPE may request clarification of any proposal received, and may invite firms to present their proposed approach before a decision is made.11.Basis of selectionProposals submiited by the Consultacy Service provide will be assessed on technical quality and price, with technical quality carrying the greater weight. The technical assessment will consider:

• Relevant experience of the firm and the quality and current condition of the websites in its portfolio.
• The technical approach, the proposed platform and work plan, and how completely the requirements in Section 5 are addressed.
• The experience and suitability of the proposed team.
• Amharic language capability, and the training, knowledge transfer and support arrangements offered.

EBPE is not bound to accept the lowest priced proposal, or any proposal, and may cancel this request at any time without incurring liability to any firm.All materials produced under the assignment, including the source code, designs, configuration files and documentation, will be the property of EBPE. Hosting, domain, and any licence accounts required to operate the website will be registered in EBPE’s name and handed over to EBPE together with the materials listed in Section 4.8.