How to Evaluate an IT Project Management Company?

Short answer: An IT project management company runs projects on behalf of your organisation — typically a fixed-scope engagement with their PMs leading and your team executing (or vice versa). Five things to evaluate: domain fit, methodology match, team depth (not just the salesperson), references with specifics, and an honest exit clause. Most failed engagements miss the domain-fit check; the rest are downstream of that.

A consultancy which offers project leadership as its product is a project management company. They assign project heads   usually business analysts or engineers   to run IT projects on your behalf. Typically, the fixed-scope and fixed-fee engagement comes with a defined schedule of deliverables. The good among them bring projects to closure within the timelines; the bad ones cost you the engagement fees, and the cost of the project they didn’t deliver. Most of the craft they sell maps to the project management ground rules every software project needs — what's worth paying for is whether the firm enforces them under pressure.

Here’s why it matters: organisations hire IT PM companies for the wrong reasons (to offload accountability, to signal the board, “Pat says we should have project management”) The appropriate underlying reason – the team does not have a PM with the relevant experience needed for a relevant project – gets lost. It is essential that the selection process corresponds with the right reasons.

This guide walks through what an IT project management company actually does, what 5 things to evaluate, what red flags to look out for, what are the important clauses in the contract, and when it is a wrong-step to hire one. People in Charge of tech i.e. CTOs, IT directors & founders evaluating whether to bring in an external project manager.

What an IT project management company actually does

Honesty of scope.

• Project leadership. A PM or PMs from the company embed with your team, run the project, report up.
• Methodology imposition. They bring their preferred framework (PRINCE2, PMI, hybrid agile, whatever). Cultural fit matters more than the framework name; Atlassian's overview of project management methodologies lays out where each style breaks down.
• Stakeholder management. They handle the meetings, the status updates, the difficult conversations with execs.
• Risk management. They maintain the risk register, escalate issues, track mitigations.
• Sometimes more. Some companies offer business analysis, change management, organisational design, training. The "more" varies; the core is project leadership.

What they usually don’t do

• Engineering. They project-manage your engineers; they don't replace them.
• Product strategy. What to build is your org's question; how to deliver it is theirs. The line between the two is worth re-reading in where product management and project management intersect before signing.
• Long-term ownership. When the project ends, they leave. Anything that requires ongoing ownership goes back to your team.

Our engagement model can be per-PM hourly, fixed-fee for per-project, retainer for portfolio-level management. The most frequent fixed-fee per project is the most honest –the company has an incentive to finish.

The five things that determine quality

Assess each contender based on these five. A solution that receives a score of five out of five on the five criteria is rare. Those that score three or four are workable solutions. Those that miss two or more are warning signs.

When looking for an IT PM company an important criterion is domain fit. A company that has delivered five similar projects in your industry   banking core systems, healthcare EHR migrations, SaaS platform builds, whatever   is dramatically different from one that’s never done it. The Project Management craft consists of two layers, a portable layer and a domain-specific layer. The portable layer consists of Gantt, risk register, stakeholder management, etc. The domain-specific layer consists of regulatory milestones, integration patterns, vendor ecosystems, etc. It takes many years to build the domain layer.

Whether you have labelled it or not, your team has a working method. A heavy-weight PM company that applies a heavyweight method onto an agile team breaks that team. A PM company that applies pure agile onto a regulated waterfall development environment fails compliance. Engage in a dialogue over methodology before you sign; if their reply is “oh we adapt”, ask how — the official Scrum Guide is two pages and a useful litmus test for whether they actually know the framework they're quoting.

The PMs who sell the project may not be the same PMs that deliver the project. Inquire directly: who will be assigned, what experience do they have, can I meet them before committing? The ones where the bait-and-switch is the model are the companies that avoid this question.

Case studies that are vague on the website are useless. Request three named projects, associated contacts, and reasons. Reach out to those contacts to glean the positives and negatives. If a vendor cannot produce 3 specific references, it’s either too new, too unsuccessful or too defensive about its track record.

Clarity on exit means definition of done. When does the engagement come to close? What do you hand over to your team? If a contract does not answer these questions, it becomes a contract at renewal almost regardless of whether the project finishes or not.

Common red flags

After many projects, these patterns recur.

• Senior salesperson, junior delivery team. The pitch is given by partners; the work is done by associates. Standard consulting model; lethal in IT PM specifically because the PM's experience is what you're buying.
• "We do everything." A company that claims expertise in every domain has expertise in none. The good companies have niches.
• Aggressive upselling during the engagement. The PM keeps "discovering" new work that requires additional contracts. Sometimes legitimate; often scope manipulation — see how to respond to new ideas mid-project for the discipline that distinguishes the two.
• Resistance to engineering involvement. PMs who treat engineering as a black box that produces deliverables on schedule miss the failure modes that matter in IT projects.
• Heavy on process artifacts, light on outcomes. Twenty pages of PRINCE2 documentation per week; no evidence the project is closer to done.
• No PM-to-engineer ratio discipline. One PM should handle one or two real projects; companies that pitch one PM running five projects are running PM theatre.

When hiring an IT PM company is the right call

Certain situations when it is effective.

• Major one-off project with no internal PM capacity. ERP migration, data centre consolidation, regulatory compliance build. Your team will run BAU; the project needs dedicated PM that you don't have, and any honest firm will admit upfront that estimating these projects is hard under most methodologies.
• Specialised domain expertise. A specific regulatory regime, a specific technology stack, a specific stakeholder configuration that your team hasn't navigated before.
• Politically charged project. A consolidation across business units, a vendor selection that two departments disagree on, a build that crosses org boundaries. External PM can sometimes break the political logjam that internal PM can't.
• Time-boxed surge. Three months of intense delivery; not worth hiring a full-time PM for.

When it's the wrong call

The authentic cases.

• Routine product development. You have engineering teams shipping product continuously. You don't need a project management company; you need an engineering manager.
• Small projects (< 3 months, < 5 people). The overhead of bringing in an external company exceeds the cost of running the project with whoever's on the team.
• Highly technical work where engineering and PM blur. Modern agile dev teams often combine PM and engineering responsibilities; bringing in a generic PM company that doesn't understand the work creates friction.
• The org is using a PM company as cover for not making decisions. External consultants can't fix internal misalignment about goals or priorities. They'll run the project; they won't tell your CEO they should pick a direction.
• The team has internal PMs who could do the job with adjusted priorities. Sometimes the answer is "redeploy internal PMs" rather than "outsource".

A genuine opinion is that IT PM consultancies fit worse in today’s software product orgs than before. So, the PM job is more product-shaped than project-shaped when it comes to continuous delivery work. Firms that focus on project-based approaches find it hard to adapt to products — Martin Fowler's thinking on continuous delivery captures why the model breaks once cadence becomes the unit of work.

The mathematics surrounding smaller stories indicates that cycle times tend to decrease from days to hours. Not just that, teams also manage to reach users up to 14 times faster. The key here is the part that reads the team owning the workflow and not passing it to an external PM — the case in agile tools simplify instead of managing complexity is exactly this. Extra handoff layer due to adding a PM company to smaller stories running on internal cadence.

Contract clauses that matter

If you decide to hire a product management company, what clauses matter?

• Named team members. Specific people, not a generic "PM consultant role".
• Defined deliverables, not effort. Pay for what they produce, not for hours worked.
• Exit / hand-off plan. Documented, with a date, with a signed acceptance of the hand-off.
• Penalty for missed milestones. Real teeth, not "we'll discuss".
• Right to terminate for cause. Defined causes — missed milestones, unauthorised team substitution, scope abandonment.
• IP ownership. Anything they produce on your project belongs to you, including the documentation.
• Replacement of underperforming PMs. Specific clause — if your PM is not working out, you can request a replacement without renegotiating.

A weak contract with a strong firm is perfectly fine. It is possible that a strong contract can work with a weak company.  Weak contracts with weak companies are where engagements go to die.

A real opinion on the category

Our take is this. Most IT PM companies sell the same three things: PM craft, domain expertise, and reputational cover. The first portable device is increasingly being commoditised — a single ordered backlog and a velocity-per-card discipline (the model in Tracker, the iPod of project management software) does most of the visible work for free. The second one is rare and worth the price. What most engagements pay for – even if not spoken – is the third.

If your employer wants to hire a PM firm so they can pin the blame for failure on them when the project fails, that is a political not a project need. PM firms can fulfill the need. Acknowledge this; things will go smoother when both sides realize what is being bought.

When hiring for #2 (agent requires real domain expertise), spend your time on the domain-fit evaluation.  The difference between a domain strong and a domain weak company shows up in the first month at the latest.

If your internal team is unable to do that ask why are you hiring for it #1. Mostly, there is a question of capacity (this is a legitimate concern) but some also say process (an external company is not going to fix this).

Frequently asked

What does an IT project management company do?

They provide PMs who run IT projects on your behalf, usually embedded with your team. They lead the project, manage methodology and stakeholders, and track risks. Usually, they are not involved in engineering or ownership.

How much does an IT project management company cost?

Varies considerably. The hourly fee for a project manager (PM) is between $100 and $300 in most markets while the fee for fixed-fee project engagements is between $50,000 and $500,000 depending on the scope. Specialists in a domain and named partner consultancies charge more than generalists.

When should I hire an IT project management company?

One-time project with no internal PM resource, specialist domain knowledge requirement, politically-charged cross-org project, heavyweight urgent delivery timebox. Don’t hire one for repetitive product building or little projects.

How do I evaluate IT project management companies?

There are five criteria – domain fit (similar projects delivered), methodology match (fits your team’s culture), team depth (the people you meet are the people you get), references with specifics (named projects and contacts), and finally exit clarity (defined hand-off).

What are the red flags?

The senior salesperson and junior delivery team make 'we do everything' claims, have heavy process artifacts with no outcomes, resist engineering involvement, use generic case studies, aggressively upsell, and have no PM-to-project-load discipline.

What contract clauses matter?

Team members are named, pricing based on deliverables (not effort), exit plan is defined, penalty for missed milestones, right to terminate for cause, ownership of IP, right to request PM replacement. A weak contract with a strong contracting company can survive, a weak contract with a weak contracting company is where engagements fail.

Can a small business afford one?

The pricing structures of most IT PM Companies fit within Enterprise Budgets. -------------- The better option for small businesses is to hire a single freelance PM or a small specialist consultancy rather than hiring an enterprise PM firm.

Should I outsource project management or hire internally?

Outsource for specialist work within a time-box according to the project (the PM leaves). Source candidates from within for ongoing product work where the PM's knowledge snowballs. Your work can either be project-shaped or product-shaped depending on the mixture.

Still stuck

Engaging an IT project management company is a proper approach when you run have genuinely run out of PM capacity for time boxed specialist projects. For mainstream product development it’s a bad move; the work is becoming ever more product-shaped and continuous, and PM firms suit project-shaped engagements better.

If your team is running software product development and if you are thinking of an IT PM company because of the chaotic feeling due to tooling, the answer is likely better tooling, not external PM.  LiteTracker is designed for a tracker with one ordered backlog only card story velocity owner per card. Free plan, no limits on team size.

Either way, indicate what you are actually buying and assess accordingly.