citech.et, reimagined.

'Consultancy of Integrated Technology for Health' is an expansion of the acronym, not a value proposition. A visitor from a regional hospital has no immediate reason to read further. The headline should answer: what problem do you solve, for whom, and with what result?

Ranging from laboratory machine integration to nutrition meal plans and grant writing, the breadth signals a generalist — which is a liability when selling to health institutions that want specialists. The page needs a clear primary offer with secondary services positioned accordingly.

It is not clear until the contact section that this business operates in Ethiopia. Health IT is deeply localised — Ethiopian hospital procurement teams need immediate confirmation this consultancy understands local systems (HMIS, MOH standards), and international NGOs need to know the geographic footprint.

There is no button, form prompt, or directed next step anywhere in the service or hero sections. The only path to contact is scrolling to the bottom and finding a phone number and Gmail address. Every service description should carry a specific prompt — 'Request a Bahmni assessment', 'Get a live streaming quote'.

Institutional buyers rarely cold-call. A structured enquiry form that captures the type of institution, the service of interest, and the timeline would dramatically lower the barrier to first contact and give CITecH qualified lead data to act on.

Consultancies that serve public health institutions often face long procurement cycles. Even a vague indication of engagement model (project-based, retainer, day-rate) helps procurement officers decide whether to invest time in a conversation, and filters out poor-fit enquiries.

With ten distinct service lines targeting different buyer types (hospitals vs. individuals for nutrition, NGOs for grants), an intake form with conditional logic could instantly route enquiries to the right service area and trigger an auto-response with relevant case examples — currently all of this is manual via a Gmail inbox.

CITecH's EMR expertise positions them to offer AI-assisted clinical decision support or documentation tools as an add-on service. A simple on-site chat widget that answers common Bahmni implementation questions could demonstrate capability while capturing leads.

Event live streaming is a time-sensitive, repeatable service. Currently there is no way to check availability, submit an event brief, or receive a quote without manually contacting the team. A simple booking intake flow would reduce back-and-forth and allow CITecH to handle more concurrent enquiries.

St. Paul's Hospital, AaBET Hospital, and Hawassa Referral Hospital are named but with no project descriptions, dates, scope, or outcomes. A single case study — even one paragraph describing a laboratory machine integration at St. Paul's and what it achieved — would be worth more than all the service descriptions combined.

Health IT buyers are buying expertise. No team members, qualifications, or professional backgrounds are visible. Even a brief team section with names, roles, and relevant certifications (OpenMRS, HL7, etc.) would substantially increase trust with institutional procurement teams.

For a consultancy targeting hospitals and health institutions, citechconsultancy@gmail.com is a credibility gap. A branded domain email (e.g. info@citech.et) is a straightforward fix that signals permanence and professionalism.

The Facebook, Twitter, and Instagram links in the footer appear to be placeholder anchors ('#') with no actual destination. Dead social links actively reduce trust — remove them or connect them to real profiles.

Each service should have its own URL or at minimum a stable anchor so that a sales conversation can direct a prospect directly to, say, the Bahmni Consultation section. Currently sharing the site means sharing the homepage and hoping the visitor scrolls to the right place.

Some services use H5 headings, others H3, with no visual or structural logic. This is not merely aesthetic — screen readers and search engines use heading structure to understand page content, so inconsistent hierarchy reduces both accessibility and SEO for service-related searches.

The primary contact is a phone number, but it is rendered as plain text rather than a tappable 'tel:' link. On mobile — the dominant device in Ethiopia — this means users must manually copy and dial, adding unnecessary friction at the most critical conversion point.