What does a web development consultant actually do?

When I tell people I'm a web development consultant, I get one of two reactions. Either they assume I just build websites (so why not just say that?) or they assume I charge a lot of money to tell people things they already know (the classic consultant stereotype). The reality is somewhere else entirely.

The short version

I help businesses make good decisions about their web technology, and then I build or manage the implementation. The consulting part and the building part are equally important.

Why not just hire an agency?

You absolutely can, and sometimes that's the right call. But agencies have a business model that creates certain incentives. They have teams to keep busy, preferred platforms they're most efficient on, and a sales process designed to close projects. When you ask an agency "what should I build?", the answer tends to be "the thing I'm best at selling you."

A consultant works differently. I don't have a team of WordPress developers waiting for work, so I don't have an incentive to recommend WordPress for everything. If the right answer for your project is Shopify, I'll tell you that, even if it means less development work for me. My incentive is to give you the right advice, because my reputation depends on the outcome, not the sale.

What a typical engagement looks like

Most projects start with a discovery phase. I'll look at your current website (if you have one), understand your business goals, talk to the people who actually use the site day-to-day, and figure out what needs to happen. Sometimes the answer is a complete rebuild. Sometimes it's fixing the three things that are actually broken and leaving the rest alone. I've talked businesses out of spending £20,000 on a new site when £2,000 of targeted improvements would have solved their actual problems.

From there, I'll put together a recommendation, what platform, what approach, rough timelines, and realistic costs. If it's something I can build, I will. If it needs a team or specialist skills I don't have, I'll help you find the right people and manage the project.

Ongoing, I handle things like hosting management, security updates, performance monitoring, and being the person you call when something breaks or when you want to change something. Think of it as having a technical partner rather than a vendor.

The things I actually do

Day to day, it's a mix. Some days I'm writing code, building a custom WordPress theme, integrating an API, fixing a performance issue. Other days I'm reviewing proposals from other agencies to make sure a client is getting a fair deal. Sometimes I'm migrating a site from one host to another, or setting up proper backup systems, or explaining to a client why their SEO company's recommendations don't make sense.

The common thread is that I'm solving problems with web technology. Sometimes that means building something. Sometimes it means advising on what to build. Sometimes it means telling someone not to build anything at all.

Who hires a consultant?

Typically, businesses like yours that are too small to have an in-house developer but too complex for a DIY website builder. They need someone who understands the technology, can give honest advice, and can actually do the work, not just talk about it.

I also work with businesses that have been burned by an agency and want an independent perspective before committing to another project. A couple of hours of consulting before signing a £30,000 contract can save a lot of pain.

If any of that sounds like your situation, I'd be happy to have a conversation. No sales pitch, no commitment, just an honest chat about what you need. Get in touch at [email protected].