Agency vs freelancer vs DIY for a small business website

Define the website's job

Start with the customer action. It may be an email, an intake form, a purchase, a booking, or a phone call. List the questions a visitor must answer before taking that action. Then list the proof, service details, location information, and policies needed to support the decision.

Turn that list into a page plan. A page plan names each public page and states its purpose. Include forms, analytics, redirects, search metadata, accessibility checks, and the person who will update the site after launch. Without this scope, three proposals may describe three different websites.

Choose DIY for a small controlled scope

A do-it-yourself build can work when the site is small, the offer is already clear, and an owner has time to write, assemble, test, and maintain it. A prepared website system can handle ordinary pages and forms without custom development. The owner also keeps direct control of routine changes.

DIY still requires decisions. Someone must compress images, write accessible labels, connect the domain, configure form delivery, create page titles, and test the site on phones. Count that time as part of the project. If the build repeatedly displaces sales or customer work, the apparent simplicity may not be useful.

Choose a freelancer for a defined specialty

A freelancer can be a good fit when one person has the main skill the project needs. Examples include visual design for an established page plan, development from finished designs, copy for a known offer, or a technical search review. A direct working relationship can keep communication short.

Ask which parts are included and which require another person. A strong designer may not write the copy or configure tracking. A strong developer may expect finished layouts and content. Neither gap is a problem when it is named, owned, and scheduled before work begins.

Choose an agency for connected responsibility

An agency can fit when strategy, information architecture, copy direction, design, development, search setup, and measurement must work as one release. Information architecture means the way pages and navigation organize the site's subjects. Coordination matters when a decision in one discipline changes another, such as a new page plan changing design, redirects, and analytics together.

Ask who makes decisions, who does the work, and who checks it. A clear agency plan should name milestones, feedback windows, launch responsibilities, and the system for handling scope changes. The word agency alone does not prove that those roles are present.

Compare ownership after launch

The website needs an owner after it is published. Confirm who holds the domain, hosting account, source files, analytics access, form destination, and content credentials. Ask how backups work and how the business can export its content.

Also define maintenance. Routine text edits, new pages, security updates, broken links, and measurement reviews may have different owners. A handoff is complete when the business knows what it controls, what requires help, and how to request that help.

Use the same evidence for every option

Give each candidate the same page list, feature list, content state, and target action. Ask for assumptions and exclusions in writing. Review relevant finished work, but also ask how the person or team handled testing, forms, redirects, and post-launch fixes.

Choose the model that makes responsibilities easy to see. The lowest coordination burden often matters more than the number of people involved.

Example

This example uses illustrative assumptions, not client data. Assume a planned site has 9 pages. The owner expects 3 rounds of review and needs 25 minutes to check each page during each round.

• Assumption: 9 pages.
• Assumption: 3 review rounds.
• Assumption: 25 minutes per page per round.
• Review math: 9 × 3 × 25 = 675 minutes, or 11.25 hours.

That review time exists whether the build is DIY, freelance, or agency-led. The delivery choice changes who prepares the work and resolves conflicts, not the owner's responsibility to verify facts and decisions. The calculation is a planning estimate, not a project result.