What does a web developer actually do for a small business?

The job title covers an unhelpfully wide range. Someone selling a template setup and someone building a booking system that talks to your CRM both call themselves web developers, and the gap between them is most of the confusion around what this costs.

What is the actual work?

Four things, roughly in the order small businesses need them.

Custom functionality. Anything the platform does not do out of the box. A form that routes inquiries by service area. A quote calculator. A booking flow that checks real availability. Whenever the answer to “can the site just do X” is no, this is the work.

Integrations. Connecting systems that were not built to talk to each other, so information moves without anyone retyping it. The site to a CRM, the CRM to a scheduler, the scheduler to invoicing. Unglamorous and frequently the highest-value part.

Performance and reliability. Making pages load fast on a phone on a weak signal, and keeping them working. Compression, caching, and the structural decisions that determine whether a site is fast by default or fights you forever.

Measurement. Wiring up analytics, conversion tracking, and call tracking so you can tell which channel produced which job. This is the piece most often promised and least often finished, because nothing visibly breaks when it is missing.

How is that different from a designer?

Design decides what it looks like and how it is arranged. Development decides how it works and what happens when someone uses it.

On large projects they are different people. On small business projects one person often covers both, with a bias. Someone from a design background makes better-looking sites with weaker integration work. Someone from engineering makes the opposite trade.

Worth asking directly which bias you are hiring, because it predicts what will be strong and what will need fixing later.

A marketing agency is a third thing again: traffic, ads, and content, usually subcontracting the build. Nothing wrong with it, but be clear who is responsible when a form breaks.

Do I need one at all?

Often no, and it is worth being honest about that.

If your site is a brochure that proves you exist to people who already found you, a template does that, and paying for custom development buys very little.

A developer earns their cost when one of these is true:

• The site must produce leads from strangers rather than only confirm you exist
• Information is being retyped between systems every week
• You cannot tell which channel produced a job
• Something specific to how you work does not exist as an off-the-shelf product
• The current site is slow in a way the platform will not let you fix

None of those is about appearance, which is why “we need a new website” is usually the wrong framing for the problem being felt.

What should I expect while working with one?

Questions before quotes. Anyone quoting a firm number before understanding what the site must do is guessing, and guesses on this work run wrong by large multiples.

Being asked for content early. Copy and photos are the most common cause of a stalled build. A developer asking for them in week one is managing the risk, not stalling.

Access requests. Domain registrar, hosting, analytics, Google Business Profile. Gather these before starting; hunting a password nobody has costs more projects a week than any technical problem.

Plain explanations. A developer who cannot explain a trade-off in terms of what it costs you and what it gets you is either not thinking clearly or not interested in you making an informed decision. Neither is a good sign.

What should I ask before hiring one?

Five questions, and the answers are more revealing than a portfolio:

1. Who owns the domain, hosting, and code when this is done? The only correct answer is you.
2. What happens when something breaks in six months, and what does it cost? Silence here means an invoice later.
3. How will we know whether this worked? If measurement is not mentioned, it will not be built.
4. What is out of scope? More useful than what is in scope, and it is where surprise costs live.
5. Will you be doing the work? Reasonable either way, but you should know.

Portfolios show what a site looked like on launch day. These questions show what working together will be like in month six, which is what you are actually buying.

For most small businesses the useful engagement is not “build me a website.” It is the site, the offer, the follow-up, and the tracking scoped as one thing, which is what a lead generation engagement covers.