How to Find Clients for Web Development (Not Web Design)

Web development clients come from a different place than web design clients, and the distinction matters more for prospecting than it does for the work.

Everything written about the difference is career content — what a designer does versus what a developer does, and what each earns. The commercial version is more useful: a design client is buying a presence, and a development client is buying a function. Those are different people, reached differently.

The row that reorganises everything: a development client almost always already has a website. Which means the entire no-website prospecting method — the core of this corpus — is a design-work method, and applying it to development work produces the wrong prospects.

Design work is bought when somebody decides they should be findable, which can happen at any time and often does not. Development work is bought when a process breaks, and the break is usually visible from outside if you know what to look for.

A restaurant taking bookings through a WhatsApp number that now gets ninety messages a day. A coaching institute collecting admission forms on paper because the enquiry volume outgrew a spreadsheet. A wholesaler whose rate list is a PDF being emailed by hand. A retailer taking orders on Instagram DMs and losing track.

Every one of those is a business that outgrew a manual process. They are not looking for a website — they are looking for the pain to stop, and they frequently do not know that what they need is software.

So the prospecting question is different. Not "who has no website" but "who is doing something by hand that has clearly got too big", and that is visible in review counts, in queue photographs, in what people complain about in reviews, and in what the business posts about.

In rough order of how much work each produces for a small agency.

Existing design clients, later. The most reliable source by a distance. A business you built a site for in year one comes back in year two wanting bookings, a catalogue, a login. You already have the trust, you already know the business, and there is no competition. This is the strongest argument for care plans that has nothing to do with the monthly fee.

Referrals from other developers. Agencies turn down work constantly — the wrong stack, too small, badly timed. A relationship with two or three other shops produces steadier development work than any outbound campaign, and it costs nothing but being reachable and not stealing their clients.

Businesses whose current site visibly cannot do something. A restaurant with a menu PDF and no ordering, a clinic with no appointment booking, a supplier with no enquiry routing. These are findable and the gap is demonstrable, which makes for a much stronger approach than a general offer.

Failed projects. Uncomfortable and real. A meaningful share of development work is finishing or rescuing something somebody else started, and those businesses are actively looking. They are also cautious, slow to commit and worth being careful with — ask what happened before quoting anything.

Harder than for design, because the scope is genuinely unknown at the start and the failure mode is expensive rather than merely disappointing.

Is the process actually breaking, or is somebody bored? "It would be nice to have an app" is not a project. "We lose two orders a week in WhatsApp" is one, and the difference is whether there is a countable cost.

Who maintains it afterwards? Development work does not finish at launch. A business with nobody technical and no maintenance budget will have a broken system in eight months and will remember whose fault it is.

What does it integrate with? The answer determines whether this is a two-week project or a three-month one, and the client usually does not know that their existing billing software is the deciding factor.

Have they done this before? A business commissioning software for the first time needs a much smaller first project than they will ask for. Building the smallest useful thing first is not upselling in reverse — it is the only way a first software project ends well.

Most small agencies do, and the sensible arrangement is a sequence rather than a split.

Prospect for design work, because it is the only side where you can generate volume on demand, and because the no-website market is large and reachable. Then let development work arrive from that base — from the clients you built for, as their businesses grow into needing more.

The reverse — prospecting for development work cold — is slow, because the trigger is an event you cannot cause and cannot predict. Waiting for a process to break at a business you have never met is not a pipeline.