Is this you?
Who I work with
I work with experienced Project and Delivery Managers at software vendors. Sometimes the title is Implementation Manager or Engagement Manager. People who lead enterprise software implementations and carry responsibility for outcomes that depend heavily on others.
They work at mid-to-large SaaS vendors, typically 500 to 5,000 employees. Their projects involve corporate clients, complex stakeholder landscapes, and significant business impact. They've usually been doing this for 5 to 10 years.
What they have in common: they take their work seriously. They've invested in their professional development. Many hold certifications like Agile credentials, PMP, or PRINCE2. They know the methodology. They can build a project plan, run a RAID log, and structure a steering committee.
And yet, they sense there's more to figure out.
They're ambitious. They have presence but are not arrogant. They want to grow, and they're honest enough to admit that some parts of this work are harder than they expected. They're open to looking at things differently because they recognize the gap between what they learned and what they actually face.
Accountable without authority
You're on the hook for project success. But client-side delays, unclear decisions, and resource gaps are outside your control. When the project struggles, it reflects on you. Even when the causes sit elsewhere.
Stakeholders who stay vague or are misaligned
You ask for clarity. You get partial answers, shifting priorities, or agreement in meetings that doesn't hold afterward. You build plans based on what you're told, then watch the goalposts move.
Politics you can't decode
People nod in meetings but resist behind the scenes. You sense something is off, but you can't quite see it. By the time it surfaces, it's already a problem.
Get your Free BookThe uncertainty of AI
The technology is changing fast, and so are the expectations. You're wondering what your role looks like in a year or two. Will delivery be expected to go faster and cheaper? How do you position yourself? There's no clear answer yet.
Pressure from both sides
Internally, leadership wants to know why the project is over budget or behind schedule. Externally, the client questions why progress is slow. You're explaining in both directions, often for things outside your control.
It can feel lonely
You're expected to have the answers, stay calm, project confidence. But sometimes you don't have the answers. Sometimes you're uncertain too. And it's not always clear who you can talk to about that.
What Makes This Role Different
Being a PM at a software vendor is a specific kind of challenge. You're not managing an internal project with colleagues who share your priorities. You're operating across two organizations: your own and the client's. Each with different incentives, different pressures, different definitions of success.
Your company wants profitable delivery. Your client wants business improvement and to maximize the value of the vendor contract. Sometimes those align. Sometimes they don't.
You're accountable for outcomes, but you don't control the resources, decisions, or priorities that determine them. The client controls their own people and priorities. Your own organization sometimes makes decisions that serve bigger interests but hurt your project. You sit in the middle, expected to make it work.
Add to that: deals sometimes get oversold before they land on your desk. Client stakeholders have their own agendas. Politics play out in ways you can't see until it's too late. And when things go wrong, your name is on it.
The work itself covers a wide range. One hour you're in a detailed requirements session, the next you're negotiating a tense change request, and after that you're having a sensitive conversation with a team member going through a difficult personal situation. The range is broad. The switches are constant.
This is the reality of the role. It's rarely acknowledged in PM training or methodology courses. On top of that, there are few people you can turn to. Your manager, your peers, your team. But with all of them, you want to be perceived as the leader who has things under control. That doesn't leave much room to ask for help.
What Changes
PM Guidance develops the people side of your professional capability. Specifically: influencing, negotiation, creating clarity, applying care, and building the relationships projects depend on. Integrated with the structured PM skills you already have.
This is what it looks like in practice.
You read stakeholder dynamics more accurately and earlier. Instead of reacting to misalignment after it's caused damage, you recognize it developing and address it while options are still available.
You operate with more influence in situations where you have no formal authority. You understand how incentives, interests, and power structures work across the vendor-client landscape, and you use that understanding deliberately.
Your judgment under pressure improves. When things get tense, you respond with more clarity and less reactivity. You make better decisions about when to push, when to slow down, and when to let delivery speak.
You create shared clarity across complex stakeholder groups. Expectations, responsibilities, priorities become genuinely shared rather than assumed. Fewer surprises, less rework, more trust.
You sustain your effectiveness over longer periods. The role doesn't get easier, but you operate within it with more steadiness, more awareness, and less accumulated strain.
And perhaps most practically: your delivery improves. Progress picks up because the human system around it is working better. Decisions happen. Ownership holds. Momentum builds.
What might be going through your mind
"Maybe I'm just not cut out for this." When projects struggle, it's hard not to take it personally. Even when you know the causes were outside your control, the doubt creeps in. You wonder if others have figured out something you haven't.
"I should be able to handle this by now." You have experience. You have credentials. And yet some situations still throw you off. It feels like you should have outgrown this by now.
"Asking for help might make me look weak." The role comes with an expectation of having things under control. Admitting you're struggling, especially to leadership or peers, feels risky. So you keep it to yourself.
"Another course probably won't help." You've done the training. You've read the books. More methodology isn't the answer. But you're not sure what is.
These doubts are common. They're not a sign that something is wrong with you. They're a sign that the role asks for things that your training doesn't provide.
You are not alone in this
The challenges described on this page are built into the role. They come with the territory of vendor-side delivery. Most PMs in this position face them, whether they talk about it or not.
The gap between what you were trained for and what you actually face is real. It's a structural gap in how the industry prepares people for this work.
Free Book
Successful Stakeholder Management in SaaS Delivery Covers key principles of the Art of Project Management: working with project relationships through clarity and care. A practical introduction to this work. Free.
Stakeholder toolkit
Practical tools for mapping and working with your stakeholder landscape. Templates, frameworks, and guides that help you apply clarity and care in your day-to-day project reality.
Stakeholder Clarity course
A structured program for developing the people skills that complement your PM methodology. Covers emotional and mental clarity, stakeholder dynamics, and influence in environments where authority is limited.
