By Touchbase Technologies · Published
How to get clients for a web development company
Choose one kind of customer and one website task you can deliver well. Then look for businesses where that task matters, show a relevant example and offer a clearly bounded project. A promise to build “anything your business needs” makes it difficult for a buyer to understand why they should speak with you now.
This guide is for a developer or small team selling website work to clients. Selling a custom project is different from finding users for a subscription product. Your customer needs to understand the scope, responsibilities, approval process and what will happen after launch. The examples below are fictional planning examples, not real customer results or conversion benchmarks.

Package a customer task rather than a list of technologies
A business owner may not have a framework preference. They may need customers to request a repair, understand a service area, book a class or find an accurate product specification. Describe the task first, then explain the technology when it affects cost, maintenance or a meaningful customer decision.
For example, a developer could offer to rebuild one service page and its inquiry form, with agreed mobile layouts and a handoff to the staff who answer inquiries. That is easier to evaluate than an open-ended promise to redesign the entire business.
Write a service brief with the audience, the problem you are equipped to investigate, the deliverable and the boundaries. Include what you do not yet know. A proposed booking form does not automatically include payment processing, scheduling software, a new CRM or migration of historical records.
The SBA's marketing guidance encourages businesses to connect an audience, a sales plan and marketing actions. For a development company, apply that by deciding which business task your service supports and how you will reach people responsible for it.
Select a prospect group you can understand
Pick a group narrow enough that you can learn its vocabulary and delivery constraints. “Independent repair shops with a service-inquiry website” is a more useful research starting point than “all small businesses.” It does not mean every repair shop needs a new website or can afford your service.
Consider your own experience, examples you can legitimately show and the kind of support you can provide after launch. If you cannot maintain a complex integration, do not use it as the centerpiece of your offer. If you have no examples in the sector, create a clearly labeled demonstration rather than implying you have already delivered results for a similar customer.
Build a short research list. Record the business website, the specific service it provides, the person or public business contact responsible for inquiries, the observation you want to discuss and the source page. Separate a published contact address from a confirmed working mailbox. Never turn a guessed email into a claim that you found the owner's contact details.
Research a real public task without inventing a diagnosis
Start with what a visitor can observe on public pages. Can you find the service information? Are opening hours and service areas clear? Is a visible form field understandable? Does the mobile menu cover a key button? Write the page URL, the conditions you checked and the observation.
Do not claim the business is losing a particular amount of revenue, has a security vulnerability or is violating a rule because you looked at its homepage. A quick review does not establish those conclusions. Do not submit test inquiries, scan private systems or create customer records without permission.
For form work, the W3C tutorial on labeling controls explains the relationship between descriptive labels and their form fields. That is a concrete technical reference for discussing a field whose purpose is unclear. It is not a complete accessibility audit or proof of a legal outcome.
| Research note | Useful observation | Unsupported leap to avoid |
|---|---|---|
| Service page | The page describes repairs but does not state which bicycles the shop accepts | Your customers are definitely leaving because of this |
| Mobile layout | At the tested viewport, the menu overlaps the inquiry button | Your website never works on mobile |
| Inquiry form | The field has no visible description in the reviewed screen | This proves the entire site fails accessibility requirements |
| Maintenance | The public page lists last year's workshop dates | Your developer has abandoned your business |
The W3C's preliminary accessibility checks are explicitly a starting point. Use a limited review to ask a useful question, not to produce a dramatic score that overstates what you examined.
Show one relevant example before asking for a large commitment
If the task is improving repair inquiries, show a demonstration of that task. A brief walkthrough can explain how a customer selects a repair type, provides the information staff need and receives a clear confirmation. Mark sample names and submissions as demonstration data.
Show the parts you actually built. Distinguish a working form from a static visual design and a planned integration. If the example uses a fictional repair shop, say so. Do not add an invented testimonial or a claim that the design increased bookings.
A small example can also reveal an unsuitable match. The owner may already have a booking system that solves the problem, or staff may prefer phone inquiries. Learn that before writing a full proposal. The product-demo guide explains how to keep a walkthrough focused on an observable task rather than unsupported promises.
Write a first message that earns a specific conversation
Use one observation, one reason your experience might be relevant and one small question. Keep it understandable without an attachment or a meeting invitation. The following is a fictional message to adapt only after doing the research it describes:
Hi Maya, I was reading your public repair page and could see the service list, but I couldn't find which bicycle types you accept before sending an inquiry. I build service pages and inquiry forms for small teams. Would a short example of how that detail could appear beside the form be useful? Thanks, Alex
This is not a high-performing template claim. Its value is that the observation is checkable and the question is easy to answer. Replace the invented name and page observation with verified information. Respect requests not to be contacted, and do not keep sending the same message to an unresponsive address.
If the person replies, ask about the actual process: who handles inquiries, what information is missing and what systems already exist. You are learning whether there is a useful project, not forcing the prospect into the service you decided to sell before listening.
Turn interest into a bounded paid project
A discovery conversation should produce a brief that both sides can read without guessing. The discovery-call recap guide provides a related handoff structure. Before beginning work, clarify the commercial terms and approval process in writing.
Here is a suggested brief for a fictional bicycle repair shop. It is a planning example, not a contract template or a standard package every shop needs.
| Decision | Example project boundary |
|---|---|
| Customer task | Understand repair options and submit one useful inquiry |
| Deliverables | One service page, one inquiry form and an on-screen confirmation |
| Client inputs | Approved service wording, photographs they may use and an inquiry destination |
| Existing systems | Keep the current domain and existing scheduling system |
| Acceptance | Agreed content is visible; labels are clear; a permitted test inquiry reaches the intended destination |
| Exclusions | Payments, inventory, a full rebrand and migration of old customer records |
| Reviews | One named approver and agreed revision rounds |
| Handoff | Source files or platform access, maintenance instructions and ownership responsibilities |
Verify the client's rights to the materials and agree who can publish changes. Keep domain and business-account ownership clear. Do not make the customer dependent on a personal account that disappears when a contractor leaves.
Review the acquisition process with honest denominators
For a hypothetical month, a team researches 12 relevant businesses, contacts eight appropriate published business addresses, receives three replies and holds two useful scope conversations. One conversation becomes a signed project. Those numbers describe an invented example only; they are not a forecast or a recommended volume.
Keep the stages separate. A reply asking to stop is not a qualified lead. A meeting is not revenue. A verbal yes is not a completed project. Record which audience and offer were used, which messages reached a working destination and where the next action belongs.
If nobody replies, review relevance, contact quality and the clarity of the offer before increasing volume. If people reply but decline, ask whether the project boundary, timing or existing tools make your offer unsuitable. If proposals stall, check who can approve the work and whether the deliverables were concrete enough to evaluate.
Use a marketing calendar to reserve time for research, useful examples, customer replies and delivery. Do not create a schedule that wins inquiries you have no capacity to handle.
Choose supporting tools after the process is clear
You can run this process with a research sheet, your existing mailbox and a shared project brief. If you consider Touchbase for supporting acquisition work, compare its current plans and allowances with the tasks you need. A tool should support accurate research and accountable replies; it cannot make an unsupported claim true or deliver a client project for you.
Questions developers ask
Should I offer a complete free website to get my first client?
A clearly labeled demonstration can establish what you can build without delivering an entire production project unpaid. Choose a bounded example that you may show publicly. Agree the scope and payment terms of actual client work before starting it.
Can I say a prospect's website is costing them sales?
Not from a quick public review alone. Describe what you observed, explain the limits of the review and ask whether it creates a problem for the business. Do not invent lost-sales figures to make a message more persuasive.
What should my first offer be?
Start with a task you can build, demonstrate and support. Define the client inputs, acceptance criteria, exclusions and handoff. A narrower offer is useful when it makes the commitment clearer, not when it hides the work required to finish the job.
Prepared with AI assistance and checked against the sources linked in this guide.
Your next step
Get started with Touchbase
Find relevant customers, prepare outreach for review and keep contacts, replies and follow-up connected.
Start for freeStart with a Free account. Upgrade or add credits when you need more capacity. Compare plans