How to start a web design agency with a deliverable first offer

1. Choose a buyer situation you can understand

‘Websites for small businesses’ is too broad to guide an offer. A more useful starting hypothesis is ‘enquiry websites for independent service providers with one main offer and no online checkout.’ You can then identify the content, page types, and technical limits you are likely to encounter.

A niche is a way to reduce uncertainty, not a guarantee of higher rates. Speak with a few potential buyers before building a large template library. Ask what their current site prevents them from doing, who updates it, where enquiries go, and what triggered the conversation now. Record their words, including reasons a new website is not a priority.

Buyer: independent consultant with one established service.
Problem: prospects cannot understand the offer before a call.
Inputs: approved service facts, biography, photos, and contact inbox.
Output: home, service, about, and contact pages.
Done: content approved; mobile, links, and enquiry delivery tested.
Excluded: checkout, memberships, custom integrations, ongoing copywriting.

2. Make the business affordable to operate

List the costs you will owe even without a sale: essential software, insurance or professional support appropriate to your situation, communications, and your own minimum income needs. Keep this planning separate from project revenue. A signed proposal is not collected cash, and an annual software commitment is not a monthly experiment.

For each offer, estimate discovery, content work, building, revisions, testing, and handoff. If you intend to use AI, measure a sample build with those stages included. Do not price from generation time alone. Keep tax, registration, contracts, and local compliance questions with qualified local advisers rather than borrowing another agency’s paperwork without review.

• Build a quote from costs and scope
• Write a package buyers can understand

3. Build proof without inventing clients

If you have no client work, create a clearly labeled self-initiated project. Use a fictional business or your own project, approved assets, and realistic constraints. Show the brief, a few important decisions, the responsive result, and the tests you ran. Do not put a real company’s logo beside a concept in a way that implies they hired you.

One case study that explains your decisions is more useful than several unexplained home-page screenshots. For example, show how you changed a vague ‘Get started’ button into an enquiry path that explains what details are needed and what happens next. You can demonstrate clarity and testing without claiming conversion gains you have not measured.

• Write a case study with evidence instead of invented results

4. Qualify the first project before sending a proposal

Start with people who can explain a real problem and introduce you to its owner. A referral, a local professional partnership, or a relevant conversation can be a useful entry point. Ask for a discovery discussion rather than promising a redesign will create revenue.

Before quoting, confirm the decision maker, budget range, content owner, launch constraint, existing accounts, and critical website functions. ‘We need it next week’ is not enough information to agree to a date. If the content is missing or an integration is uncertain, propose a smaller release or discovery phase.

Decline work outside your competence when you cannot arrange reliable specialist support. Complex commerce, sensitive data, or a custom application should not become a learning experiment funded by an unsuspecting client.

• Build a small, measurable client-acquisition process

5. Use approval gates so problems surface early

A practical sequence is brief approval, content approval, representative-page approval, full-site review, and launch sign-off. At each gate, name the approver and the evidence they are reviewing. The representative page should test the hardest common layout—not merely the easiest home-page hero.

Use one feedback location and ask the client to consolidate comments. Label corrections against the brief separately from new requests. Before launch, test the actual visitor journey on mobile and keyboard, verify submitted enquiries arrive, and record domain and platform ownership. Leave the client a short handoff document with update instructions and the support boundary.

6. Improve one delivery cycle before taking on more

At closeout, compare the estimate with actual hours and note where the client waited on you or you waited on them. Convert repeated checks into a checklist and repeated layout work into reusable components. Do not standardize an unresolved mistake just because it happened twice.

Capacity includes sales calls, administration, revisions, and existing-client support. If you have 25 delivery hours available in a week, booking 25 hours of new builds leaves no room for a failed form or a late review. Decide what work you will reserve capacity for and stop selling starts you cannot support. Ask for permission before publishing the project or requesting an introduction.