What Does a Product Manager Actually Do? A Simple Guide for Startups
If you are building a startup in Ireland or the UK, you have probably heard the term "product manager" thrown around. Maybe an advisor told you that you need one. Maybe you saw the role in a job listing and wondered how it differed from a project manager. Or maybe you are a founder doing everything yourself and someone suggested you are already acting as your product manager without realising it.
The product manager role is one of the most misunderstood positions in business. Ask ten people what a PM does and you will get ten different answers. Some will say they are mini-CEOs. Others will describe them as glorified project coordinators. Neither description is accurate, and the confusion can lead startups to either hire the wrong person or neglect a function that is absolutely critical to building something people actually want.
I have worn the product manager hat for two products I built and shipped: Dine With Me, a social dining app on iOS and Android, and Media Training AI, an AI-powered public speaking platform. In both cases, the PM role was not a title I gave myself -- it was a set of responsibilities that had to be covered for the products to succeed. Somebody had to decide what to build, why to build it, and in what order. Somebody had to talk to users, prioritise features, coordinate development, and make hard trade-offs when time and resources were limited. That somebody was me.
This guide explains what the product manager role actually involves, why startups need PM thinking even if they cannot afford a dedicated PM, and how the role differs from other positions you might already have on your team.
What a Product Manager Actually Does
At its simplest, a product manager is responsible for ensuring the right product gets built for the right people at the right time. That sounds straightforward, but it involves a surprisingly wide range of activities.
The core responsibilities
Understanding the problem. A PM spends significant time talking to users, analysing data, and studying the market to deeply understand the problem the product is solving. This is not a one-time activity. It is continuous. The problem evolves as the market changes, as competitors emerge, and as users' needs shift.
Defining the vision and strategy. Where is this product going in six months? A year? Three years? The PM sets the direction, making sure every feature and decision moves the product closer to a clear goal. Without this, teams build features that feel disconnected or chase opportunities that do not align with the business model.
Prioritising ruthlessly. Every product has an infinite list of potential features and improvements. The PM decides what gets built now, what gets built later, and what does not get built at all. This is perhaps the hardest part of the job, because saying "no" to a good idea is much harder than saying "yes."
Communicating across teams. The PM sits at the intersection of engineering, design, marketing, sales, and leadership. They translate business goals into technical requirements, translate technical constraints into business language, and keep everyone aligned on what matters most.
Measuring outcomes. A PM defines what success looks like for each feature and for the product as a whole. They set metrics, track results, and use data to inform future decisions. Building something is only half the job. Understanding whether it worked is the other half.
Product Manager vs Project Manager: The Confusion That Costs Startups
This is the single most common misconception I encounter. People use "product manager" and "project manager" interchangeably. They are fundamentally different roles with different skill sets and different impacts on your business.
Project manager
A project manager is responsible for execution. They manage timelines, budgets, resources, and processes. Their primary question is: how do we deliver this on time and on budget? They are masters of coordination, scheduling, and risk management.
Product manager
A product manager is responsible for direction. They decide what to build and why. Their primary question is: are we building the right thing for our users and our business? They are masters of user understanding, strategic thinking, and prioritisation.
Why the difference matters for startups
If you hire a project manager thinking they will fill the product manager role, you will get someone who is excellent at delivering things on schedule but has no framework for deciding whether those things should be built in the first place. You might ship features on time and under budget that nobody uses.
Conversely, if you hire a product manager expecting them to manage timelines and assign tasks, you will underutilise their strategic skills and frustrate them with administrative work.
For early-stage startups in Ireland and the UK, the founder typically needs to fill both roles initially. But understanding the distinction helps you know which hat you are wearing at any given moment and which skills you need to develop or hire for as you grow.
| Aspect | Product Manager | Project Manager |
|---|---|---|
| Primary focus | What to build and why | How to deliver it |
| Key question | Are we solving the right problem? | Are we on schedule? |
| Success metric | User adoption and business impact | On-time, on-budget delivery |
| Key skill | Strategic thinking and user empathy | Planning and coordination |
| Interacts most with | Users, design, engineering, leadership | Engineering, vendors, stakeholders |
A Day in the Life of a Product Manager
To make the role concrete, here is what a typical day might look like for a PM at a startup.
Morning: Research and analysis
Review overnight data. Check key metrics: user sign-ups, feature adoption, retention rates, support tickets. Look for patterns. Did the feature you launched last week move the needle? Is there a spike in complaints about a specific flow?
Read three to five pieces of customer feedback. This might be app reviews, support emails, survey responses, or notes from recent user interviews. Look for recurring themes.
Mid-morning: Prioritisation and planning
Meet with the engineering team to review the current sprint. Discuss blockers, clarify requirements, and answer questions about upcoming features. Make decisions about trade-offs: should we fix this bug or ship that feature?
Update the product roadmap based on new information. A customer segment is asking for a feature you had planned for next quarter -- does it make sense to pull it forward?
Afternoon: User interaction and strategy
Conduct a 30-minute user interview with a customer who recently churned. Understand why they left and what would bring them back.
Draft a product brief for a new feature. Define the problem it solves, the expected outcome, the success metrics, and the scope. Share it with design and engineering for feedback.
Late afternoon: Communication and alignment
Write a weekly product update for stakeholders: what shipped, what is in progress, what is coming next, and what you have learned from users this week.
Respond to requests from sales and marketing. The sales team wants a specific feature for a prospect. The marketing team needs messaging guidance for the upcoming campaign. Filter these through the product strategy: does this align with where we are going?
Why Startups Need Product Management Thinking
You might not be able to hire a dedicated product manager. Most early-stage startups in Ireland and the UK cannot. A PM at a tech company in Dublin or London commands a salary of 60,000 to 100,000 euros or more. That is out of reach for a bootstrapped startup.
But you absolutely need the thinking that a product manager brings. Here is why.
Without PM thinking, you build based on assumptions
When I was building Dine With Me, I had strong opinions about what features the app needed. Real-time chat seemed essential. A gamified scratch card for discovering dining experiences felt like the core differentiator. Payment integration through Stripe was obviously necessary.
But opinions are not evidence. PM thinking forced me to validate each assumption. Which features did users actually engage with? Which ones did they ignore? What did they ask for that I had not considered? The answers to these questions shaped the product far more than my initial vision did.
Without PM thinking, you build too much
The natural tendency for any builder -- whether you are a developer, designer, or founder -- is to add more. More features. More options. More complexity. PM thinking counteracts this by constantly asking: what is the minimum we need to deliver value?
Every feature you add has a cost. Not just the development cost, but the maintenance cost, the cognitive load on users, the testing burden, and the opportunity cost of not building something else. A PM mindset helps you see these hidden costs before they accumulate.
Without PM thinking, you lose focus
Startups face enormous pressure from multiple directions. Customers want different things. Investors have opinions. Competitors launch features that make you nervous. Without someone whose job is to maintain strategic clarity, it is incredibly easy to chase every opportunity and master none.
Essential Product Management Skills for Founders
If you are a startup founder acting as your own PM, here are the skills that matter most.
User empathy
The ability to genuinely understand how your customers experience your product. This means talking to users regularly, observing how they actually use your product (not how you imagine they do), and being willing to have your assumptions challenged.
Prioritisation frameworks
Learn at least one structured approach to prioritisation. The MoSCoW method (Must have, Should have, Could have, Will not have) is simple and effective. RICE scoring (Reach, Impact, Confidence, Effort) adds more rigour. The important thing is having a framework, not which framework you choose.
Data literacy
You do not need to be a data scientist. But you do need to be comfortable looking at metrics, understanding what they mean, and using them to make decisions. Set up basic analytics from day one and review them weekly.
Clear communication
A PM's most important tool is the ability to explain complex decisions in simple terms. Whether you are talking to a developer, an investor, a customer, or a marketing partner, you need to make your reasoning understandable and your priorities clear.
Comfort with saying no
This is the hardest skill for most people, especially founders who want to please everyone. But the ability to say no to good ideas in order to focus on great ones is what separates products that succeed from products that try to do everything and do nothing well.
When to Hire Your First Product Manager
As your startup grows, there comes a point where the founder cannot effectively manage both the business and the product. Here are signs it is time to hire.
- You are spending less than 20 percent of your time talking to users. If operational demands have pulled you away from understanding your customers, a PM can restore that connection.
- Feature decisions are being made reactively. If you are building whatever the loudest customer or the most recent competitor demands, you need someone with the time and focus to think strategically.
- Your team is growing beyond five to seven people. At this size, communication overhead increases significantly. A PM helps keep engineering, design, and business teams aligned without requiring the founder to be in every conversation.
- You have achieved product-market fit and need to scale. Once you know what works, a PM can optimise the product experience and manage the complexity that comes with rapid growth.
FAQ
What is the difference between a product manager and a product owner?
In practice, the terms overlap significantly, especially at startups. A product owner is a specific role within the Scrum framework, focused on managing the product backlog and working closely with the development team. A product manager has a broader scope that includes market research, business strategy, and cross-functional leadership. In large organisations, these are separate roles. In startups, one person typically does both.
Do I need a product manager if I am a solo founder?
You do not need to hire one, but you need to adopt the mindset. Dedicate time each week specifically to product management activities: talking to users, reviewing metrics, prioritising features, and questioning assumptions. The discipline of structured PM thinking will save you from building the wrong thing, even if you are doing it all yourself.
Can a project manager learn to be a product manager?
Yes, but it requires developing a different set of skills. Project managers excel at execution and delivery, which are valuable foundations. To transition to product management, they need to develop user empathy, strategic thinking, data analysis abilities, and comfort with ambiguity. The shift is from "how do we deliver this?" to "should we build this at all?"
How much does a product manager cost to hire in Ireland or the UK?
In Ireland, product manager salaries typically range from 55,000 to 90,000 euros for mid-level roles and 90,000 to 130,000 euros for senior positions. In the UK, the range is similar in pounds sterling, with London commanding a premium of 10 to 20 percent above other cities. Freelance or fractional product managers charge between 500 and 1,200 euros per day, which can be a cost-effective option for startups that need PM expertise but cannot justify a full-time hire.
Building a product and need help thinking like a PM? Get in touch -- I help startups and small businesses in Ireland and the UK build products that solve real problems, from user research through to launch.
