Website Projects
Someone has to drive it. That's usually the reason it hasn't happened.
The website everyone agrees needs doing
Most website projects don't stall because of the design or the developer. They stall because no one has the time to gather the photos, chase the copy, decide what stays and what goes, and keep asking the questions that need answering before anything can move.
So it sits. Either it never starts, or it starts and drifts, and six months later you're still sending people to a site you apologize for.
The work isn't building it. It's everything around building it.
What I actually Do
I run the project. That means scoping what the site needs to do before anyone opens a design tool, then sorting out the parts that always hold things up: what content exists, what has to be written, what photos you have and what you need, which pages are worth keeping and which have been dead for two years.
I bring in the designer or developer if you don't have one, or work with the people you already use. I write the brief, keep the schedule, run the reviews, and handle the back and forth so you're making decisions instead of managing a project.
And I ask the unglamorous questions early, because they're the ones that derail things later. Who owns the domain. Where the hosting lives. Who has the logins. Whether anyone is going to update this after launch, and how.
To be clear about what I'm not: I'm not a developer or a designer. I don't write the code and I'm not choosing your fonts. What I do is make sure the people who do that work have what they need, and that the thing actually ships.
What this Usually Includes
Scoping what the site needs to do and who it's for
Sitemap and page structure
Content audit: what exists, what's missing, what can go
Gathering copy, photos, and assets
Sourcing and briefing the designer or developer
Managing the build schedule and review rounds
Coordinating domain, hosting, and access
Launch checklist and post-launch handoff
Why me
I spent three and a half years at a marketing and PR agency as an account and traffic director, where website projects were one of the most common things on my client list. I ran them the same way I'd run yours: scoping the thing, keeping the designers and developers supplied with what they needed, and making sure the client wasn't the reason it was late.
Here's what I saw over and over. A company that badly needed a new site would hand the project to someone on staff who already had a full-time job. That person wasn't in over their head because they weren't smart. They just had no room for it, no experience running a build, and no standing to push their own leadership for decisions or ask the uncomfortable questions. When a project ran late, it was almost never the agency. It was that nobody on the client side had the time or the authority to keep it moving.
Your team already has jobs. This one can be mine. I have the time, I've done this before, and I have no problem asking you the hard questions. Websites also come with their own language, and a lot of clients nod through conversations they don't fully follow. I know enough to translate the parts that matter to your decisions, and when something needs explaining, I'll ask your developer for it in plain English. Nobody should be approving work they don't understand.
What Comes Next
Photos & Video
A new site with old photos is a half-finished site. Planning a shoot, sourcing the photographer, and organizing what comes back is its own project.
Brand First
If the look and messaging are part of what's not working, the website isn't the place to start. That's a brand conversation.
Got a Site that Needs Doing?
Tell me where it is now, whether that's nothing yet or a half-finished draft from last year, and we'll figure out what it takes to get it live.