Product Management for Software Teams
Decide what to build, prove it was worth building, and carry a team through shipping it
- Duration
- 12 weeks
- Level
- Beginner to Intermediate
- Effort
- 10–12 hrs/week
- Format
- Live online + product labs
Next cohort intake is open · instalments available
Most product managers learn the job by getting it wrong in front of a team. This track compresses that: you run discovery on a real problem, write the spec an engineer builds from without a follow-up call, choose metrics you can defend, and ship a slice with a live team, then explain every trade-off in an interview.
What you will be able to do
- Run discovery that produces a problem statement, not a wish list
- Prioritise with evidence and say no without losing the room
- Write one-page specs that engineers build from on the first pass
- Choose, instrument and read the metrics that show whether it worked
- Plan a launch with pricing, onboarding and support in place
- Defend every product trade-off you made, in an interview or a board meeting
Entry expectations
If you are close but not quite there, tell us at application. We would rather get you ready than turn you away.
- 01Comfortable using software products and describing what they do and for whom
- 02Basic spreadsheet skills
- 03No coding required, but genuine curiosity about how software gets built
The route, module by module
8 modules over 12 weeks. Every one ends in something deployed to a real URL and reviewed line by line.
- The job across company sizes
- product vs project vs programme
- decision rights
- the weekly rhythm
- where new PMs fail in their first ninety days
- Interviewing without leading
- observing real work
- jobs to be done
- segments and problem statements
- writing down what you are not building
- Opportunity sizing
- cost of delay
- RICE and its failure modes
- roadmaps as bets, not promises
- saying no with evidence
- One-page specs
- user stories that carry intent
- acceptance criteria
- edge cases and failure states
- running a spec review
- Activation, retention and revenue metrics
- choosing a north star honestly
- instrumenting events
- A/B tests and when not to run them
- reading a funnel
- Estimation without fiction
- trade-offs under a deadline
- technical debt as a product decision
- design critique
- a stand-up people do not dread
- Launch checklists
- pricing and packaging basics
- onboarding as a product surface
- support loops
- the post-launch review
- Discovery to shipped increment on a real project alongside SaaSFarers engineers
- a written product review defended in front of the team
What you will have built
- 01A discovery report from real user interviews, ending in a problem statement the team agrees on
- 02A prioritised roadmap with the reasoning written down and the rejected options kept
- 03A one-page spec that an engineer built from without a follow-up call
- 04Capstone: a shipped product slice with its metrics review
Roles this prepares you for
Before you apply
Not the right track? Try these
AI Engineering & Applied LLMs
Build AI features that survive production, not demos that survive a slide
View trackFull-Stack SaaS Development
Learn to build multi-tenant products, not another todo app
View trackFrappe & ERPNext Developer
A specialist skill with more open roles than qualified people
View trackReady to build things that ship?
Apply for the next cohort. The first conversation is an honest assessment of where you are and what it will take.