Sales pitches to be skeptical of when hiring a web designer
The ranking guarantee
The proposal is sitting open on your screen right now, and somewhere in it is a line about page one of Google. Read it again. Does it promise you'll rank, or land on page one, or beat a named competitor in search results?
No one selling a website can honestly make that promise. Rankings depend on a search engine's own algorithm, on what competitors do next, and on dozens of factors a single project never controls. Nobody building your site controls any of those, no matter how confident the pitch sounds.
A guarantee stated with a straight face isn't confidence. It's a claim nobody can back, offered because it closes deals fast. An honest version sounds more like an approach - built with search visibility in mind - rather than a promised outcome.
If a pitch won't say that plainly, ask why not, out loud, and watch the answer. None of this means search visibility is a lost cause. What realistic search visibility work actually looks like is a genuinely useful subject. A guarantee dressed up as a feature just isn't part of it.
Urgency pricing on a project that takes weeks
"This price is only good today." "Sign by Friday and the setup fee disappears." A website build spans several weeks and needs your input at multiple points along the way. There's no honest reason the price should shift because of what day you happen to sign.
Urgency tactics work by shrinking your thinking time, not by offering a real discount. That's the entire mechanism: a deadline built to get you to skip the parts of deciding that take longer than a single afternoon.
A rushed yes on a project this size is exactly the yes worth slowing down before you give. Real vendors, the ones with a full calendar and steady work, rarely need a deadline to close a deal. Their price holds whether you sign today or next Tuesday.
If the offer is genuinely good, it holds up next week too. Ask directly: "If I need a few more days to decide, does this price disappear?" The answer says more than the original pitch ever did.
A calendar packed with other clients is a fair reason to say a slot might fill up. That's a scheduling fact, not a pricing threat. The two get blurred together on purpose in a pitch built around urgency, and it's worth pulling them apart before you sign anything.
Scope described in words too vague to hold anyone to
"A beautiful, modern website that gets you noticed." That sentence describes a feeling, not a deliverable. Nobody can dispute it later, because nobody can point to what it actually promised in the first place. Vague scope isn't a style choice. It's what fills the space when someone doesn't want to commit to specifics.
Compare that to language you could actually hold someone to: a page count, a contact form, mobile display, a content system you can log into and edit. That's a deliverable. "A site that gets you noticed" is closer to a mood board than a plan.
Ask for the vague phrase to be translated into a list. Watch what happens. A real designer can turn "gets you noticed" into pages, features, and a rough timeline without much effort. One who can't, or won't, is telling you the phrase was the whole plan.
If a pitch stays vague after you push for a direct answer, that's the answer. The full vetting process these red flags feed into exists partly to force this kind of specificity before any money changes hands, and the full picture of all four builder options is worth reading alongside it, since vague scope shows up across all four paths, not just one.
No-contract handshake deals
"We don't really do contracts, we just get started" sounds relaxed right up until something goes wrong: a missed date, a disagreement about what was promised, a dispute over who owns the finished files. Without anything written down, there's nothing to point back to except two people's separate memories of a phone call.
A written agreement protects both sides equally in theory. In practice, its absence protects the person already holding your deposit more than it protects you. A handshake feels friendly right up until the day it isn't, and by then the friendliness isn't much use to you.
Getting real terms in writing instead of a pitch is not an unreasonable ask on a project of any size, and asking for it early tells you plenty about how the rest of the relationship will run.
The pattern of going quiet right after the deposit clears
The pitch itself won't show you this one. It shows up right after, once the paperwork is done and the money has already moved. Fast, warm, responsive contact before payment, followed by a noticeable slowdown the moment the deposit clears.
One quiet day proves nothing on its own. People get busy. A pattern of it, especially paired with vague scope and no written contract, is worth naming out loud before it becomes a habit you're stuck inside for the rest of the project.
Before paying anything, ask what response time looks like once the project is under way, and watch whether the answer matches what you've already seen so far. Consistency before and after payment is a small thing to check and a meaningful thing to find missing. It costs nothing to ask, and the answer is worth more than the reassurance that comes with it.
None of these five patterns proves a project will go badly on its own. A single one, spotted early and asked about directly, usually resolves itself in one honest conversation. Two or three stacked together, in the same pitch, are worth taking seriously before any money moves.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go