Web Designer Red Flags: 10 Warning Signs Before You Sign the Contract

Why the red flags matter more than the portfolio

Prospects usually evaluate web designers by looking at their portfolio. That's the wrong primary filter. A designer can screenshot beautiful sites on their portfolio without those sites being their work, without them being launched, or without them actually being maintainable by the client.

The specific things that predict a bad outcome aren't in the portfolio. They're in the operational signals: how the designer bills, how they communicate, how they handle contracts, what they say about ownership. These signals are what to check first — before you get distracted by pretty screenshots.

The 10 red flags below aren't dealbreakers individually. Any one of them might have a reasonable explanation. But when multiple show up together, they consistently predict projects that go badly. Learn to see them.

Red flag 1: No recent client references

What it looks like: The designer offers testimonials on their website but won't or can't produce actual references you can call. Or the references they give are old (2+ years).

Why it matters: Testimonials on a website are unverifiable and often fabricated. Recent references (last 90 days) tell you what the designer actually delivers now, not what their marketing claims. If a designer can't produce 2-3 recent clients you can call, the reason is usually either (a) they don't have recent clients, or (b) recent clients wouldn't recommend them.

What to do: Ask specifically for "2-3 clients from the last 90 days I can call or email." If the designer stalls, deflects, or offers to send you old case studies instead, that's your answer.

Red flag 2: Hourly billing without a cap

What it looks like: Quote says "$120/hour, estimated 40-60 hours." No maximum. No specific deliverable list.

Why it matters: Uncapped hourly billing means the designer has no incentive to complete efficiently. Every additional hour is additional revenue. Projects quoted at 60 hours frequently run 100+ hours, and the final bill can be 2-3x the initial estimate. You have no recourse because the contract permits it.

What to do: Insist on either a fixed-price contract or hourly billing with a hard cap. If the designer won't commit to either, that tells you they're either uncertain about scope (they should say so) or comfortable with open-ended billing (which serves them, not you).

Red flag 3: Ownership terms not written into the contract

What it looks like: Contract discusses payment terms and deliverables but doesn't explicitly state who owns the domain, hosting account, and source code after launch.

Why it matters: When ownership isn't explicit, the designer's default is often to keep control — domain in their name, hosting on their account, source code they hold. This becomes a problem the moment you want to change designers, and it's the specific mechanism that traps clients in ongoing relationships they'd otherwise leave.

What to do: Insist on written ownership terms. Specifically: "Domain will be registered in [client name] at [registrar]. Hosting will be on [client's account] at [provider]. Source code will be delivered as a complete repository at [format] within [X days] of launch." Vague language like "you own your site" is not enough — the specifics matter.

Red flag 4: Portfolio dominated by templates

What it looks like: The portfolio shows 15 sites that all use the same design pattern — same hero structure, same section rhythms, same typography scale — just with different logos and colors swapped in.

Why it matters: A designer whose portfolio is all one template is a template-swap operator, not a custom designer. That's a real product at a real price point ($500-$1,500), but it's rarely what the designer claims to be selling at higher prices. If they're charging $3,500+ for what's really a template swap, you're overpaying by 3-5x.

What to do: Look at 5-10 sites in the portfolio. Are the structural approaches meaningfully different? Different sections? Different navigation patterns? Different content architectures? If they all use the same skeleton, it's templated work. Nothing wrong with that at template pricing — problem when it's not.

Red flag 5: Communication response over 24 hours during the sales process

What it looks like: You email a question about the project. It takes 2-3 days to get a response. You have to follow up to get answers.

Why it matters: Communication speed during the sales process is the best speed you'll ever see. Sales cycles are when designers try hardest. If response is already slow before you've paid, it will get worse during the project — often catastrophically worse if you become a problem client or a difficult account.

What to do: Test communication with 2-3 email exchanges before signing. If any single response takes over 24 hours during normal business days, the designer either has too many clients to serve yours well or doesn't prioritize responsiveness. Both predict a bad experience.

Red flag 6: Cash-only or wire-transfer-only payment

What it looks like: The designer requires payment by cash, wire transfer, cryptocurrency, or Venmo. They specifically don't accept credit cards or platform payments with consumer protection (Stripe, PayPal, etc.).

Why it matters: Credit card and platform payments have chargeback protection — if the work isn't delivered as agreed, you have recourse. Cash and wire transfers have none. Legitimate designers accept credit cards because they don't need to avoid the traceability. Designers who insist on cash have a reason.

What to do: If the designer refuses standard payment methods, that's a serious warning. Legitimate providers who use Stripe, Square, or similar platforms have both consumer protection and legitimate business operation. Anything else warrants extreme scrutiny.

Red flag 7: 100 percent payment required upfront

What it looks like: "Full payment due before work begins. Nonrefundable."

Why it matters: 100% upfront gives the designer no incentive to complete the project because they already have their money. Standard industry practice is milestone payments (25-50% deposit + balance at completion) or protected payment platforms that release funds on delivery.

What to do: Insist on either a milestone structure (25-50% deposit, balance at completion) or credit card payment with normal chargeback protection. Some legitimate flat-rate providers do collect full payment upfront when they use platforms that provide chargeback protection — that's different from cash-in-hand upfront.

Red flag 8: No defined post-launch support terms

What it looks like: Contract covers building the site. Says nothing specific about what happens after launch when you need updates, when things break, or when you have questions.

Why it matters: Post-launch is where most client-designer relationships break down. If terms aren't defined upfront, expect friction. Common patterns: designer bills $150+/hour for post-launch changes with no cap; designer becomes unresponsive after payment; designer requires a monthly retainer to touch anything.

What to do: Insist on written post-launch terms. Specifically: how long is included support, what triggers additional charges, what the response-time commitment is, and what happens if the designer becomes unavailable. Vague answers here predict friction later.

Red flag 9: Offshore team hidden behind a domestic front

What it looks like: The designer presents as a local Orange County studio with local phone number and local imagery, but when you dig, the actual work is done by contractors in the Philippines, India, or Pakistan.

Why it matters: Offshore work isn't inherently bad — some offshore teams do excellent work. The red flag is hiding it. It signals the designer is misrepresenting the operation, which usually predicts other misrepresentations. It also creates communication friction (time zones, language, culture) that wasn't disclosed.

What to do: Ask directly: "Who specifically will be doing the design and development work? Are they local or offshore?" A legitimate designer will answer honestly. If they hedge, deflect, or claim the work is local when reviews suggest otherwise, that's your answer.

Red flag 10: Vague scope that doesn't specify inclusions vs exclusions

What it looks like: Contract says "custom website design and development." Doesn't specify page count, features, or what's not included.

Why it matters: Vague scope is the source of most flat-rate disputes. The designer's interpretation of "custom website" is usually smaller than the client's. Mid-project you discover things you thought were included aren't. Additional costs appear.

What to do: Insist on specific scope: page count, feature list, integration list, and — critically — a list of what's NOT included. Standard exclusions on a professional flat-rate contract: custom application development, extensive brand strategy, ongoing SEO campaigns, Google Ads management, photography. If those aren't specified either as included or excluded, the contract is incomplete.

How to use these red flags

One or two red flags doesn't mean the designer is bad — every business has some rough edges. Three or more shows up together, that's the pattern to worry about. Specifically:

• 1-2 flags: Ask about the specific concerns. Might be explainable.
• 3-4 flags: Serious concern. Get quotes from at least 2 other providers before committing.
• 5+ flags: Walk away. The pattern predicts a bad outcome, and no amount of "but their work looks good" changes that.

The specific insight from watching web design contracts across hundreds of projects: portfolio quality is a poor predictor of client outcome. Operational signals — how the designer bills, how they contract, how they communicate — are much better predictors. Learn to weight them accordingly.