Red Flags in Web Design Proposals: What to Watch For Before Signing Anything

Every year, businesses across Kenya and across Africa sign web design contracts that they later regret. Not because the designers they hired were dishonest people but because the proposals those designers presented contained specific warning signs that, if recognised and understood at the time, would have prompted harder questions, clearer agreements, or different hiring decisions. Understanding the red flags in web design proposals is the specific commercial intelligence that separates business owners who protect their investment with clear eyes from those who discover the problems only after the money has been spent.

A web design proposal is a document that defines the commercial relationship between you and your design partner for the duration of the project. It establishes what will be built, what it will cost, how long it will take, what each party is responsible for, and what happens when things do not go according to plan. A proposal that defines these things clearly and fairly is a proposal that protects both parties and sets the project up for success. A proposal that is vague, incomplete, or one-sided in its terms is a proposal that is creating the conditions for the disputes, overruns, and disappointments that damage so many web design relationships.

This guide gives you the specific red flags in web design proposals to watch for, explains precisely why each one is commercially concerning, and tells you what to ask for instead.

Red Flag One: No Discovery or Strategy Stage

The most commercially significant of all red flags in web design proposals is the absence of a defined discovery or strategy stage before visual design work begins. When a proposal jumps directly from project initiation to design mockups without a documented planning phase, it is telling you something important about how the designer approaches commercial web design.

A discovery and strategy stage is where the commercial foundation of the website is established: the specific business goals the website must achieve, the specific target audience whose decision journey the design must serve, the competitive context that the design must address, the content strategy that will give the design its substance, and the performance objectives against which the website’s success will be evaluated. Without this foundation, the design work that follows is built on assumptions rather than on documented understanding, which is why designs produced without prior discovery so frequently require fundamental revision once the client sees them and realises the assumptions were wrong.

The commercial cost of skipping discovery is not visible at the proposal stage. It becomes visible during the revision cycle when fundamental direction changes are required because the design was built on incorrect assumptions, and after launch when the website fails to produce the commercial outcomes it was supposed to achieve because it was not designed around a clear commercial strategy.

When a proposal does not include a discovery stage, ask specifically: how do you establish the commercial goals, target audience, and content strategy before beginning design? A confident, commercially oriented designer will describe their discovery process even if it was not explicitly labelled as such in the proposal. A designer who does not have a substantive answer to this question is a designer whose work will be driven by visual preference and professional convention rather than by your specific commercial requirements.

Red Flag Two: Vague Scope Description

The second major category of red flags in web design proposals is a scope description that is too vague to provide a reliable basis for cost and timeline estimation or for dispute resolution when the project’s direction is contested.

A scope description that says website design and development for Ksh 75,000 with a six-week timeline tells you almost nothing commercially useful. It does not tell you how many pages will be designed. It does not specify what functionality will be implemented. It does not define what content the quoted price includes. It does not specify what SEO work is part of the scope. It does not define what post-launch support is included. And it does not establish a clear reference point for determining whether a client request during the project is within scope or constitutes an additional billable request.

Vague scope descriptions are one of the most common origins of budget overruns and relationship disputes in web design projects in Kenya and across Africa. When the scope is not clearly defined, every new requirement that emerges during the project can be presented either as a reasonable extension of what was agreed or as a new request that warrants additional billing, depending on which interpretation benefits the party making the argument. Without a clear scope document, there is no reliable way to resolve this ambiguity, which means the outcome depends on negotiating power and relationship quality rather than on a documented agreement.

A professionally prepared web design proposal should specify: the number of pages to be designed and developed, with a list of the specific pages; the specific functionality to be implemented including any forms, integrations, e-commerce features, or booking systems; the content management system and any specific configuration requirements; the SEO setup that is part of the scope; whether copywriting is included or client-provided; what post-launch support is included and for how long; and the specific deliverables the client will receive at project completion including file ownership and access credentials.

If a proposal you receive does not include this level of scope specificity, requesting a more detailed scope document before signing is not an expression of distrust. It is the minimum commercial due diligence that any significant business investment warrants.

Red Flag Three: Unrealistically Low Pricing

Among the red flags in web design proposals, unusually low pricing that is significantly below what comparable professional work is available for in the market is a signal that deserves careful investigation rather than immediate excitement. The commercial adage that you get what you pay for is not universally true but it is true often enough in web design to make very low pricing a genuine commercial risk signal.

Professional web design requires significant time investment: discovery and strategy work, information architecture planning, visual design development, responsive development and testing, SEO configuration, content population, and quality assurance. Each of these stages requires genuine professional skill and cannot be compressed below certain time thresholds without compromising the quality of the output. A proposal that quotes significantly below the market rate for equivalent work is almost certainly cutting corners somewhere in this process, and the most commonly cut corners are the planning stages that most directly affect commercial outcomes.

Very low pricing is sometimes a function of inexperience rather than dishonesty. A new designer who has not yet developed a full understanding of the time required to execute a complete professional web design process will sometimes quote prices that do not reflect the genuine scope of the work, discovering during the project that the scope is larger than the price accommodates. This typically produces one of three outcomes: the designer cuts scope to bring the project within the quoted budget, producing a less complete website than the client expected; the designer overruns the budget and either absorbs the loss or renegotiates with the client mid-project; or the designer delivers the project but at a quality level that reflects the compressed timeline the low price required.

None of these outcomes serves the business owner well. Professional web design in the Kenyan market for a quality business website that includes proper discovery, professional design, competent development, thorough SEO setup, and adequate testing has a price range that reflects the genuine skill and time investment required. Proposals that fall significantly below this range without a clear explanation of why should be questioned specifically: what specific stages or services are excluded to achieve this price?

Red Flag Four: Unrealistically Fast Timeline

Closely related to pricing concerns, an unrealistically fast promised timeline is one of the red flags in web design proposals that creates commercial risk by establishing expectations that cannot be met without compromising quality.

A complete professional web design project for a standard business website includes multiple stages that each require genuine time investment. Discovery and strategy cannot be rushed without producing inadequate foundations. Information architecture planning requires time for both the designer’s work and the client’s review and feedback. Visual design requires creative development time and multiple iterations. Development requires careful implementation and testing. Content population requires the client to provide content and the designer to implement it carefully. Quality assurance requires systematic testing across devices and browsers. And the client review process at each stage requires time for the client to review thoughtfully and provide useful feedback.

Compressing all of this into an unrealistically short timeline is only achievable by skipping stages, reducing the thoroughness of each stage, or working at a pace that produces errors and quality compromises. A proposal that promises a complete professional website in one week for a project that realistically requires four to six weeks is either misrepresenting the scope of work that will be delivered or misrepresenting the timeline it can be delivered in.

For businesses in Kenya that are eager to get their website live quickly, this is a commercially difficult message to accept but an important one. The time invested in doing the project properly is recovered many times over in the commercial performance of a website that was built on proper foundations compared to one that was rushed. A website that takes six weeks to build correctly and that performs well commercially for several years is a significantly better investment than one that takes one week to build and requires either a complete rebuild or years of underperformance as a consequence of its rushed foundations.

Red Flag Five: No Clear Payment Structure or Milestone Linkage

Professional web design proposals define payment structures that are linked to project milestones rather than to arbitrary payment schedules, and the absence of a clear, milestone-linked payment structure is one of the red flags in web design proposals that protects neither party effectively.

A payment structure that requests full payment upfront gives the designer the entirety of the commercial incentive to complete the project before any work has been done, which reduces the client’s commercial leverage throughout the project. A payment structure that requests no payment until completion gives the client all the commercial leverage but leaves the designer financially exposed for weeks or months of work with no guarantee of payment, which is unfair to the designer and creates incentives for scope disputes at payment time.

A well-structured payment schedule is linked to specific, verifiable project milestones. A typical professional payment structure might request a deposit of thirty to forty percent at project start to confirm commitment and begin work, a second payment of thirty to forty percent upon approval of the visual designs to confirm that the design direction is agreed before development begins, and a final payment of twenty to thirty percent upon project completion and launch. This structure aligns financial incentives with project progress, gives both parties skin in the game at every stage, and provides the client with commercial leverage to ensure the project is completed satisfactorily.

For businesses in Kenya commissioning web design, any proposal that requests full upfront payment without milestone-linked subsequent payments should prompt specific questions about why the payment structure is structured this way and negotiation toward a more milestone-based structure that protects your investment throughout the project.

Red Flag Six: No Mention of Content Responsibilities

One of the most consistently overlooked red flags in web design proposals is the absence of any specific discussion of content responsibilities: who is responsible for creating the text, photography, and other media assets that the website will contain, and by what deadline that content must be available.

Content is the most common cause of web design project delays in Kenya and across Africa because its requirements are typically underestimated by business owners and inadequately communicated by designers at the proposal stage. A proposal that does not explicitly address content responsibilities is a proposal that is setting the stage for a mid-project content emergency when the design is ready and waiting for content that the business owner has not started creating because they did not understand it was their responsibility.

A professionally prepared proposal should explicitly state whether copywriting is included in the project scope or whether the client is responsible for providing all written content for every page. If the client is responsible for content, the proposal should specify what content is required, in what format, and by what deadline, with a clear statement that the project timeline depends on content being available at the agreed date.

This explicitness protects the client by ensuring they understand their responsibilities before the project begins. It protects the designer by establishing a clear basis for timeline adjustments if content is delivered late. And it protects the commercial quality of the project by ensuring that content creation is planned and resourced adequately rather than being discovered as a gap when the design is waiting for it.

Red Flag Seven: No Discussion of Website Ownership and Access

The red flags in web design proposals include a category of concerns that are not about project quality but about the commercial terms of the relationship: specifically, who owns the website and its components at project completion and what access the client has to their own digital asset.

Some web design companies in Kenya and across Africa retain hosting of their clients’ websites on their own servers without clearly transferring website ownership and access credentials to the client. This creates a commercial dependency where the client’s website is effectively held by the designer: if the relationship breaks down or if the client wishes to move to a different provider, they cannot simply take their website and move it because they do not have the access credentials needed to do so.

A professionally prepared proposal should explicitly state that the client will own the website and all its components at project completion, that the client will receive full administrator access to the content management system, that the client will have access to or ownership of the domain name, and that the hosting arrangement is either client-controlled or transferable to the client’s control without obstruction.

If a proposal does not address website ownership and access, asking specifically about these terms before signing is essential. The questions to ask are: who will own the domain name and how is it registered; who will host the website and who controls the hosting account; will I receive full administrator access to the CMS; and if I want to move to a different provider in future, what is the process and are there any restrictions or fees associated with that transition?

Red Flag Eight: Promises of Guaranteed Google Rankings

Among the most reliably concerning of all red flags in web design proposals is any promise of guaranteed first-page Google rankings or guaranteed specific ranking positions for specific keywords within a specified timeframe. This promise is a commercial misrepresentation that should immediately raise serious questions about the trustworthiness and knowledge of the designer making it.

Google search rankings are determined by a complex algorithm that evaluates hundreds of factors, many of which are beyond the control of any individual website or designer. Factors including the quality and quantity of links from other websites, the search history and behaviour of individual users, and the ongoing competition from other websites for the same keywords cannot be guaranteed regardless of the quality of the SEO work done on any specific website. Any designer who claims to guarantee specific ranking positions either does not understand how search rankings work or is making a commercially dishonest claim to win business they might not otherwise secure.

What a professional designer can honestly promise is that they will implement SEO best practices comprehensively and correctly, that the website will be technically configured to give Google the clearest possible signals about its content and quality, and that the on-page SEO elements will be optimised for the target keywords. These honest representations of what SEO work achieves are the appropriate claims for any web design proposal.

When a proposal contains ranking guarantees, asking specifically: what happens if those rankings are not achieved by the promised date and what specific SEO work is included in the scope to support ranking improvements, will typically reveal either that the guarantee is qualified with conditions that make it commercially meaningless or that the designer cannot explain their specific approach to SEO work in the substantive terms that genuine SEO expertise would support.

Red Flag Nine: No Quality Assurance or Testing Process Described

A professionally managed web design project includes systematic quality assurance testing before the website launches: testing across different devices, different browsers, different screen sizes, and different connection conditions to verify that the website works correctly and performs well for the full range of visitors who will use it. The absence of any mention of quality assurance in a web design proposal is one of the red flags in web design proposals that suggests the designer launches websites without systematic testing, which means bugs and performance problems are discovered by real visitors after launch rather than caught and resolved before launch.

A QA process described in a proposal should include browser compatibility testing across the major browsers used by the target audience, device testing on actual mobile devices rather than only browser simulators, loading performance testing using specific tools with specific performance benchmarks, functionality testing of all interactive elements including forms and contact mechanisms, and SEO configuration verification that all technical SEO elements are correctly implemented before Google indexes the live website.

The commercial cost of launching without adequate QA is the damage to visitor trust and conversion that bugs and performance problems cause during the period when they are present on the live website. A contact form that does not work correctly is losing enquiries. A mobile layout that breaks on a common Android device is losing the visitors who use that device. These are direct revenue losses that a proper QA process before launch prevents.

Red Flag Ten: Refusal to Provide References From Previous Clients

The final major category of red flags in web design proposals is refusal or reluctance to provide direct references from previous clients whose websites the designer has built. A designer with a track record of commercially effective work and satisfied clients will have clients who are willing to speak to prospective new clients about their experience. The absence of available references is commercially significant information about the designer’s confidence in the quality of their previous work and the satisfaction of their previous clients.

When asking for references, be specific about what you want to verify: you want to speak with previous clients in similar business categories whose websites have been live for at least several months, so that both the project experience and the post-launch commercial performance can be discussed. References from clients who received their website very recently may be able to speak to the project experience but not yet to the commercial outcomes, which are the most commercially important validation available.

Questions to ask references include how the project was managed, whether the timeline and budget were adhered to, whether the scope was clearly defined and consistently maintained, what the post-launch support experience was like, and most importantly what specific commercial results the website has produced in terms of enquiries, search rankings, or other measurable business outcomes.

Frequently Asked Questions

Should I use a template checklist or evaluate proposals individually?

The most effective approach combines both. Having a clear sense of the specific issues to watch for, as outlined in this guide, ensures that no important red flag is missed in any proposal evaluation. But evaluating each proposal against these concerns in the specific context of the individual designer and the specific project requirements allows for the nuanced judgment that a mechanical checklist cannot capture. A minor red flag in one context may be a more significant concern in another, and the quality of the designer’s response to questions about concerning elements is itself an important part of the evaluation.

What if I find some red flags in a proposal from a designer whose portfolio I really like?

The discovery of red flags does not necessarily mean the designer should be rejected. It means the concerns should be specifically raised and the designer given the opportunity to address them. A designer who has red flags in their proposal because of careless proposal preparation rather than substantive capability gaps will be able to address the concerns clearly and specifically when they are raised. A designer who cannot or will not address the concerns clearly is a designer whose capability gaps the red flags were correctly signalling. The quality of the designer’s response to your concerns is itself a valuable evaluation input.

How do I raise concerns about a proposal without seeming confrontational?

Frame your concerns as requests for clarification rather than accusations. Saying I wanted to understand more specifically what the content responsibilities would be in this project, as the proposal does not address this in detail is a more commercially productive framing than this proposal does not mention content responsibilities which is a red flag. The first framing invites a specific, informative response. The second creates defensiveness that may not be productive for either party.

Is it appropriate to negotiate the terms of a web design proposal?

Yes, and a professional designer will expect and welcome negotiation on terms that are not in their clients’ best commercial interest. Negotiating for a milestone-linked payment structure, a more specific scope description, a clearer content responsibility definition, and explicit website ownership terms are all commercially legitimate negotiations that protect your investment without being unreasonable. A designer who refuses to negotiate on terms that a reasonable client would want clarified is demonstrating inflexibility that will likely manifest in other ways during the project.

What is the most important red flag to address before signing?

The vague scope description is the red flag with the most directly damaging commercial consequences if left unaddressed, because it is the source of the majority of budget overruns and relationship disputes in web design projects. A project begun with a clearly defined scope that all parties have agreed on has the best available protection against the misaligned expectations that produce expensive disputes. Every other issue in this guide can be addressed within the project if goodwill exists on both sides, but scope ambiguity is the one that consistently produces problems even in relationships with genuine goodwill on both sides.

The Proposal Is the Contract. Read It Like One.

The red flags in web design proposals described in this guide are not academic concerns or worst-case scenarios. They are the specific issues that produce the most common and most commercially damaging web design project problems experienced by businesses across Kenya and Africa. Understanding them before you sign is the most effective protection available against joining the large number of business owners who discover these problems only after their investment has been committed and the problems have become expensive to resolve.

A web design proposal is a commercial contract. Reading it with the same attention you would give any significant commercial agreement, questioning the elements that are unclear or concerning, and insisting on modifications that protect your investment are not signs of distrust. They are the commercial discipline that professional business owners apply to all significant investments and that produces better outcomes consistently compared to signing quickly on the basis of positive impressions and hoping for the best.

At AfricanWebExperts, our proposals are designed to address every one of the concerns in this guide transparently and specifically, because we understand that a client who signs with clear eyes and full information is a client who is set up to be a satisfied partner rather than a disappointed customer. We welcome the hard questions because we are confident in our answers.

👉 Get your free quote on WhatsApp and let us show you what a transparent, comprehensive, and commercially honest web design proposal looks like for your specific project.

Or visit our Contact page and one of our experts will be happy to start that conversation with you.