Most web projects have a project manager. Most clients don’t know what that person is supposed to be doing. That gap — between the title and the actual job — is where timelines slip, scope expands, and invoices grow.
Here is what a web project manager actually owns, what falls outside their remit, and how to evaluate whether the one assigned to your project is doing the job.
The Core Job: Translation and Accountability
A project manager sits between the client and the build team. Their primary function is translation — converting business requirements into actionable tasks for designers and developers, and converting technical updates into plain language for the client.
That sounds simple. It isn’t. Most miscommunications in web projects happen at this handoff point. A requirement like “make it more modern” needs to become a specific visual direction before it reaches a designer. A developer note like “the CMS integration is blocking the theme layer” needs to reach the client as “we need one more day before we can show you the homepage template.”
Accountability is the second core function. A project manager owns the timeline. Not “keeps an eye on it” — owns it. If a deadline slips because a developer underestimated a task, the project manager should have caught that three days before the deadline, not the morning it was due.
What a Good PM Does in the First Week
The first week of a project is diagnostic. A competent project manager will:
- Lock down a written scope with explicit exclusions
- Set a project schedule with milestone dates, not just an end date
- Identify the single client point of contact and communicate only through that channel
- Establish a feedback protocol — what format, what turnaround, what happens if feedback is late
If your project started without any of these, the PM is managing reactively. That’s how “quick eight-week builds” become five-month ordeals.
What Project Managers Do Not Own
This is where confusion creates problems. A project manager is not:
- A designer. They don’t make visual decisions. They relay design feedback and flag when a client request would require a scope change.
- A developer. They don’t write code, review pull requests, or decide which technical approach to use.
- An account manager. In many agencies, these roles get blended — the person managing timelines is also pitching upsells and fielding renewal conversations. Those are competing incentives.
- A creative director. They don’t push back on bad creative. That’s the lead designer’s job.
When a project manager tries to do all of these things, they do none of them well. The result is a project where nobody owns anything clearly.
Marcus, a restaurant chain owner, hired a mid-sized agency for a WooCommerce build. His project manager sent weekly emails, joined every call, and described the project in enthusiastic terms at every check-in. The build still took 22 weeks and launched with broken checkout flows. When Marcus asked what had happened, the PM cited “communication challenges with the design team.” Nobody owned the gap between design approval and development handoff. That gap cost Marcus $8,000 in retainer fees and a delayed peak season launch.
How Timelines Get Built — and Why They Break
A competent project manager builds a timeline from the work backward, not from the deadline forward. The difference matters more than it sounds.
Working backward: what does the developer need to begin each phase? What dependencies exist? Where is the client the bottleneck? Build the schedule around those realities.
Working forward: here’s the launch date, divide the weeks evenly, hope it fits. This is how most agency timelines are built. It’s also why most agency timelines are wrong.
The three most common timeline killers:
- Feedback rounds that weren’t scheduled — clients respond late, everything downstream shifts
- Scope creep that wasn’t formally acknowledged — new features get quietly absorbed until the timeline collapses under their weight
- Internal resource conflicts — the developer assigned to your project is also on two others, and another client’s crisis took priority
A project manager who won’t tell you about resource conflicts until you’re already affected is a project manager who is managing the agency’s interests, not yours.
If you want to see what a well-structured project handoff actually looks like, the website handoff guide covers exactly what you should receive at the end of a project — and your PM should be preparing those deliverables from day one.
Communication Cadence and Escalation
The right communication frequency depends on the project phase. During development, weekly status updates are usually sufficient. During review rounds, daily communication may be appropriate. What should never happen is silence — particularly during transitions between phases.
Sarah ran a $60,000 e-commerce build at a firm that went quiet for three weeks during development. Her PM had gone on holiday with no handover. When the project resumed, two weeks of work had to be redone because a key client decision hadn’t been made before development began. The PM’s absence had masked a process gap that cost the agency time and the client money.
Escalation paths matter. Your project manager should be able to tell you: if something goes wrong that they can’t resolve, who do they escalate to, and what is the expected response time? If there’s no answer to that question, you have no escalation path — which means problems that should be handled in 24 hours become problems that sit for a week.
What the PM’s Tools Reveal
Ask your project manager what tool they use to track tasks. The answer tells you more than the tool itself.
Agencies that use dedicated project management software — Basecamp, Asana, Linear, Jira — and actually share live access with clients are operating transparently. You can see task status, blockers, and timelines without asking.
Agencies that track projects in spreadsheets, or that don’t share any project management access with clients, are operating opaquely. You know what they tell you. When the timeline slips, you find out when it has already happened.
Our custom WordPress development process includes client-accessible project tracking as a default, not an optional upgrade. You shouldn’t have to request visibility into your own project.
The Overlap With Account Management
This is where the agency business creates a structural problem that clients pay for. In smaller agencies, the project manager and account manager are the same person. That person is responsible for client satisfaction (account management), timeline and scope adherence (project management), and relationship growth (sales). Those last two are in direct tension.
A project manager who is also your salesperson has an incentive to say yes to scope changes rather than log them as change orders. They want you to like them. Logging a change order makes people feel charged for something they assumed was included. So it gets absorbed — and the project grows in scope while the timeline stays the same.
The build team pays for this, and eventually so do you.
Five Questions to Ask Your Project Manager Before Work Begins
Before a project kicks off, ask your PM these directly:
- What triggers a formal scope change, and what is the process when one occurs?
- How many other projects are the assigned developers currently working on?
- What happens to my timeline if a developer gets pulled onto an emergency for another client?
- How will I receive project updates — what format, what frequency, from whom?
- Who do I contact if I’m not getting responses from you?
The answers to these questions don’t guarantee anything. But a PM who can’t answer them — or who answers vaguely — is telling you something important about how the project will be run.
Frequently Asked Questions
What’s the difference between a project manager and an account manager at a web agency? A project manager owns the timeline, scope, and task execution — the internal mechanics of getting the project built. An account manager owns the client relationship — communication, satisfaction, and account growth. At smaller agencies, one person often does both, which creates competing incentives. When your PM is also trying to sell you additional services, they have a reason to prioritize your happiness over your timeline.
Do I need my own project manager if the agency has one? Not always, but having a single internal point of contact on your side is valuable. That person doesn’t need to be a professional PM — they just need to have the authority to make decisions and respond to feedback requests promptly. The single biggest cause of timeline slippage is slow client feedback. Someone on your team needs to own that.
How should I handle it if my project manager goes silent? Escalate immediately and in writing. Don’t call — email or message through the project management tool so there’s a documented record. If you’re not getting responses within 48 hours on an active project, that’s a communication failure on the agency’s part, not a routine gap. Document every instance.
What should a project manager hand over at the end of a project? At minimum: all source code, CMS credentials, hosting credentials, third-party integration credentials, a list of all assets and where they’re stored, and a brief on how to make routine updates. If your agency’s PM is handing you a login and calling it a handoff, read the website handoff guide to understand what’s missing.
Can a project run without a dedicated project manager? Yes — and small agencies often operate this way, where the lead developer manages their own schedule and communicates directly with clients. This works when the developer is experienced enough to do it and when the client scope is tight. It breaks down on larger projects with multiple stakeholders, complex integrations, or extended timelines. The risk isn’t the absence of the title — it’s the absence of someone who owns the accountability function.