How to Hire a Project Manager for Your Agency

If you run a marketing agency and you are searching for how to hire a project manager, you have usually already made the hard part of the decision. Something is slipping, you are the person who notices, and you want that to stop. What is left is the part the job boards do not help with: what the role actually owns, whether your agency is ready for it, and how to tell in an interview whether the person across from you has run delivery or only read about it.

I have spent twelve years running delivery operations for marketing agencies across 79 completed engagements, most of them in this exact seat. So I have an obvious interest in how you answer this question, and you should read everything below with that in mind. I will be specific about where a full-time employee beats hiring someone like me, because the honest version of this is the only version worth your time.

What does a project manager actually own in an agency?

The title gets used loosely, and that vagueness is the first cause of a bad hire. In a marketing agency, the project manager owns the layer between “the client said yes” and “the work is delivered.” In practice that means five things:

• Intake and scoping. A signed project becomes a plan with owners, dates, dependencies, and a definition of done before anyone starts producing.
• The weekly rhythm. A standing cadence of check-ins, blocker removal, and priority calls, so the team knows what is due without asking you.
• Status and reporting. Clients hear from the agency on schedule, internally and externally, whether or not anyone remembered to ask.
• Risk. Problems get flagged early enough that you still have options. A project that surprises you in week four was already off track in week two.
• Delivery and retrospective. Work ships, and what went wrong gets captured so the next project starts with that knowledge already in it.

Just as important is what the role does not own: your strategy, the creative decisions, the client relationship, or the offer. A project manager owns individual projects. If what you actually need is someone who decides which projects matter, in what order, and whether the company is doing the right things at all, that is the portfolio, and it belongs to an operations lead or an integrator. Different seat, different hire. Getting this wrong is how agencies end up disappointed in a perfectly competent PM.

How do you know your agency is ready to hire one?

The signals are consistent enough to list. You are ready when several of these are true at once:

• You are the only person who knows where every project stands, which means you cannot be anywhere else.
• Clients follow up because nobody told them what was happening.
• Deadlines slip for coordination reasons, not talent reasons.
• New clients onboard slowly because intake is a message and a hope rather than a process.
• Your team is capable but stalls without you in the room.

Now the other direction, because the fair answer is not always “hire someone.” Below roughly five people, the founder is the system, and that is not a failure of management. At that size everyone is already in the same conversation, and a project manager will spend the week creating visibility for a group that can already see each other. Wait.

The second reason to wait is harder to admit. If your delivery process changes every week and nothing is written down, a new project manager will spend their first quarter inventing your process instead of running it. That is systems work, not project management, and it is much cheaper to do it deliberately than to buy it accidentally inside someone’s ramp-up period.

Should you hire full-time, fractional, or buy the function as a service?

Three real options, and the choice is mostly about whether the work fills a full week yet.

Full-time

A full-time project manager is a fixed cost that starts before the workload does. You are not only buying hours. You are buying recruiting time, onboarding, employment overhead, a ramp-up period where you train someone rather than being helped by them, and a notice period on the way out. None of that is an argument against it. It is an argument for hiring full-time when the role genuinely fills forty hours and your process is defined enough that a new person can step into it. When both are true, an employee in the room every day is the better structure.

Fractional

A fractional project manager is a person in the seat part-time. You buy hours rather than headcount. My own arrangement is 10 to 15 hours a week on a $4,000 to $6,000 monthly retainer with a 90-day minimum, which covers three to five active projects depending on complexity. The structural argument is simple: when the role does not yet fill a full schedule, paying for a full schedule is the expensive choice, and the ramp-up problem largely disappears when the person has done the job many times before.

The function as a service

Some owners want a person embedded in the team. Others want the coordination handled so completely that they stop thinking about it. That second group is buying project management as a defined service rather than a seat. You keep the client relationships, the strategy, and the final say on what ships. Delivery coordination, timelines, resourcing, status, and escalation move out of your building.

Agencies face the same firm-or-person decision when they buy automation help, which I worked through in my piece on choosing between an AI automation agency and an independent consultant. The test is the same here: does the engagement start from your delivery process, or from someone’s preferred platform.

What should you ask a project manager in the interview?

Skip the questions that reward preparation. Ask about work they have actually done.

• “Walk me through the last delivery week you ran.” Not a project, a week. You are listening for a rhythm they can describe from memory: what happened on which day, who they chased, what they decided without escalating.
• “Which tools have you run delivery in, and what did you do in the first week in one you had not used before?” I work inside ClickUp, Asana, Monday.com, Airtable and Notion, and I will still say tool fluency is not the skill. Someone who has run delivery can learn your board in days. Someone who only knows a tool cannot learn judgement in a quarter.
• “Tell me about a project that slipped. When did you know, who did you tell, and what did you do next?” This is the single most useful question in the interview. Everything worth knowing is in the timing. A strong answer has them knowing early, telling someone immediately, and presenting options rather than an apology.
• “How would you decide what gets escalated to me?” You are testing whether they will filter or forward. A PM who escalates everything has moved the work back to you with extra steps.
• “What would you document first?” The answer reveals whether they think in systems or in tasks.

The red flags I would not ignore

• Tool answers to process questions. If every answer becomes a feature description, they have administered software rather than run delivery.
• No project has ever slipped on them. Either untrue, or they were never accountable enough to notice.
• Certifications offered in place of delivery stories. A certificate proves someone passed an exam about a methodology. It is not evidence they have held a deadline. I hold no tool certifications and do not claim any, and I would apply the same standard to anyone you interview.
• They need a fully documented process before they can start. Your process is imperfect. Part of the job is working inside that reality while improving it.
• They want to migrate you to their preferred platform in week one, before they understand how your delivery runs.

What should the first 30 days look like?

Set this expectation before they start, because a vague first month is how good hires get judged unfairly.

Week one is continuity, not change. They read whatever exists: briefs, the task board, client communication from the last month. They talk to whoever knows the most about each project. By the end of the week they should be able to run the status call. The messier your current state, the more of week one goes into documenting rather than changing anything.

Week two, they own the rhythm. The cadence runs whether or not you are in it. Blockers reach them before they reach you.

Weeks three and four, the first improvement lands. One documented process, one recurring problem removed, and the first honest retrospective. Not a reorganisation. One visible thing.

The test at day 30 is not a report. It is whether you can ask where everything stands and not be the person who answers.

So who should you actually hire?

My verdict, with the bias declared again: I sell fractional and outsourced versions of this role, so discount accordingly.

Under about five people, hire nobody yet and write down how you deliver. Between roughly five and fifteen, where the role is needed but does not fill forty hours, fractional or the function as a service usually fits better, and it defines your process before a permanent hire inherits it. Once delivery reliably fills a full week and the process is documented enough to hand over, hire full-time, and hand your new employee a system rather than a mess. If the real problem turns out to be the portfolio rather than the projects, stop reading job descriptions for project managers, because you are hiring the wrong seat.

Whichever route you take, hire on evidence. Twelve years, 79 completed engagements and a 4.9 out of 5 client rating is what I put in front of agency owners, and it is the kind of record you should ask any candidate to produce before believing an article like this one.

Where to start before you write the job description

You do not have to make this call blind. The reason every engagement of mine begins with the Agency Ops Audit is that a $1,500 fixed-fee review answers the prior question: what is actually breaking in your delivery, what a project manager would own on day one, and whether you need one at all yet. Two weeks, a written 90-day roadmap, and a 60-minute readout call. If the answer is a full-time employee and not me, I will tell you, and the roadmap becomes the brief you hand them.