Red Flags When Hiring a Web Designer in Kenya: 9 Warning Signs to Watch For

Kenya’s web design market has a quality problem — not because talent is absent, but because barriers to calling yourself a “web designer” are essentially zero. Anyone with a laptop, a Canva account, and a WhatsApp Business profile can present as a professional web designer. Most of them will not ghost you or steal your deposit. Some will. And a much larger number will underdeliver in ways that are expensive to fix.

The nine red flags below separate the candidates worth continuing conversations with from those who will cost you far more than their quoted price.

The most expensive mistake a Kenyan business makes is not choosing the wrong designer — it is ignoring warning signs they noticed at the time but chose not to act on.

This is the simplest and most common financial red flag in Kenya’s web design market, and it has a straightforward explanation: once a designer has 100% of the money, their incentive to finish the project becomes significantly weaker than it was before. This is human nature, not a conspiracy — but in a market where follow-through is inconsistent, it becomes a structural problem.

The professional standard across Kenya’s web design industry is a milestone-based payment structure. The most common arrangement is:

• 30–50% deposit — paid before work begins, secures the project in the designer’s schedule
• 25–35% at design approval — paid when the client approves the visual mockups
• Remaining balance at launch — paid when the site is live on a staging URL and the client is satisfied

This structure protects both parties. The designer receives meaningful payment before investing significant time. The client retains financial leverage until the deliverable meets the agreed standard.

A WhatsApp conversation is not a contract. It is a record of an informal exchange that a court would struggle to interpret in your favour, even if it captures the substance of what was agreed. This matters not because every web design project ends in a dispute, but because the projects most likely to end in a dispute are exactly the ones where no written agreement was in place.

Every professional web designer in Kenya — whether a solo freelancer or a multi-person agency — should be able to produce a basic written agreement. It does not need to be a complex legal document. It needs to specify: what will be built, what the payment schedule is, who owns the assets at handover, and how disputes will be resolved. A designer who actively resists writing this down is either inexperienced or anticipating that they may not deliver what they are promising.

Under Kenya’s business registration framework, written contracts are enforceable. A WhatsApp exchange can be submitted as evidence but is far weaker than a signed document. If a designer will not produce a basic written agreement — even a one-page document covering the key terms — treat this as a serious warning sign and move on.

A portfolio is the primary evidence of a designer’s capability. It can also be fabricated in under an hour. Screenshots of template demos, Dribbble mockups that were never built, and URLs that resolve to parked domains or error pages are all common misrepresentations in Kenya’s web design market.

The test is simple: click every link. Open each site on your phone. If a portfolio link is dead, there are four possible explanations — the client’s business closed, the site was migrated, the work was done under NDA, or the work never existed. One is plausible. Four is a pattern. Any designer whose portfolio has more than one dead link owes you an explanation before you proceed.

The Google PageSpeed Insights tool is free and takes thirty seconds to run. Paste any portfolio URL and it will give you a mobile performance score. A score below 50 on mobile — for a business website in the Kenyan market — is a technical failure, not a stylistic issue. A designer whose own portfolio clients have sub-50 scores has not applied the performance optimisation skills that Kenyan mobile users require.

This is the single most costly structural trap in Kenya’s web design market, and it is remarkably common. A designer who registers your domain under their own account and hosts your site on their own shared plan has not given you a website — they have given you access to one. The distinction matters enormously when the relationship ends.

Domains are registered through KENIC-accredited registrars for .co.ke and .ke domains. When a designer registers on your behalf using their own email and payment method, you have no direct relationship with the registrar and cannot initiate a transfer without the designer’s cooperation. In practice, this creates a hostage situation — your business’s online identity is under someone else’s control.

Pricing a web design project requires understanding the project. How many pages? What integrations? Is there existing content, or does it need to be written? What platform? What are the performance requirements? A designer who reads a brief and responds with a firm price within five minutes of receiving it has not assessed any of these questions — they have applied a default number from a mental price list.

This matters because the quote they give you will not hold. Either it is deliberately low to win the job and will expand through scope creep and additional charges, or it is a genuine estimate based on no information that will change the moment real requirements emerge.

A professional response to a new brief looks like: an acknowledgement within 24 hours, clarifying questions about scope and requirements, and a detailed proposal within three to five business days that itemises what is included and excluded. The time investment in producing that proposal is itself evidence of professional seriousness. It also gives you a document to hold the designer accountable to once the project begins.

No legitimate web professional will guarantee a first-page Google ranking. Google’s own documentation makes clear that its algorithm is not controllable by third parties, that rankings fluctuate, and that no agency or individual can guarantee a specific position. A designer or SEO provider who makes this promise either does not understand how search engines work, or is telling you what they calculate will close the sale regardless of whether it is true.

What a legitimate designer can do is build a site with sound on-page SEO foundations — proper heading structure, meta descriptions, schema markup, fast load times, mobile optimisation, and a clean URL structure. These are controllable. Rankings are not. The difference between these two things is the difference between an honest professional and someone making a promise they cannot keep.

The moment of highest risk in any Kenyan web design project is the period immediately following the deposit payment. Before payment, the designer is in sales mode — responsive, enthusiastic, and available. After payment, the incentive structure changes. The most common version of this pattern is not an outright disappearance but a gradual degradation of communication quality: replies that take days instead of hours, missed deadlines explained with increasingly elaborate reasons, and deliverables that arrive incomplete.

According to research by Studio Aurora’s 2026 analysis of designer ghosting incidents, the most common underlying cause is not bad faith but a skill gap — the designer discovered mid-project that the work is more complex than they estimated and, rather than admitting it, began avoiding the client. This is why technical questions before hiring matter: they surface capability gaps before any money changes hands.

The contractual protection is straightforward: require weekly written progress updates as a condition of the agreement, and tie the second payment milestone to the delivery of an approved design mockup by a specific date. If two scheduled updates pass without communication, treat it as an early warning sign — not something to brush off.

The phrase “SEO included” appears in the majority of Kenyan web design proposals. In most cases, it means very little. When pressed on what “SEO included” actually covers, most designers will describe activities that are standard technical good practice rather than genuine search engine optimisation: adding page titles, writing a meta description, and installing a plugin like Yoast. These things matter but they are the floor of a technical build, not a searchengine optimisation service.

Real SEO for a Kenyan business website involves: keyword research for locally-specific search terms (including estate names, county modifiers, and Swahili queries); structured data markup for local business schema; optimisation of Google Business Profile to appear in Maps results; content strategy for the specific queries your Nairobi or Kisumu customers are using; and ongoing analysis of which pages are gaining or losing rankings over time. This is months of work — not a checkbox in a build scope.

When a designer includes “SEO” as a line item without specifying what it covers, ask: “What specific activities does the SEO include, and what deliverables will I receive?” If the answer is a list of plugin installations and page title writing, you now know what you are actually getting — and can evaluate whether that matches what was implied.

This is the most sophisticated form of client lock-in in Kenya’s web design market. Rather than the crude hostage of domain and hosting ownership, this involves building a site using a proprietary framework, an obscure page builder, or a heavily customised theme that cannot be touched without the original developer’s knowledge of its architecture.

WordPress — which powers the majority of professional websites built by Kenyan designers — is a deliberate antidote to this problem. Its open-source nature means any competent developer can take over any WordPress site without assistance from the original builder. This portability is a feature, not an accident. When a designer proposes building your site on a platform you have never heard of, or describes a “custom framework” they developed themselves, ask the question directly: “If we stop working together, will another developer be able to maintain this site without your involvement?” A honest answer to this question will tell you everything you need to know.