TeamProduct & data · v1.1.0

Product Management Team

Discovery synthesis, PRDs, roadmap planning, prioritisation and release communication.

Discovery synthesis, PRDs, roadmap, prioritisation and release communication.

PRDs where the problem statement is arguable and most of the length goes on edge cases — which is where specifications earn their keep. Synthesis that reports participant counts and evidence strength rather than dressing eleven interviews up as percentages.

Agents 5

  1. 01prd-writerUse to write product requirement documents, feature specifications and user stories — documents engineering can build from and everyone else can argue with.
  2. 02prioritization-analystUse to prioritise — comparing features, requests and bets against each other with an explicit method, sizing impact, and settling disagreements about what to build next.
  3. 03release-notes-writerUse to communicate what shipped — release notes, changelogs, in-app announcements, feature launch emails and migration guides for breaking changes.
  4. 04roadmap-plannerUse for roadmap and planning work — quarterly planning, sequencing, capacity and dependency management, communicating a roadmap to different audiences, and saying no well.
  5. 05user-researcherUse for discovery — designing and analysing user interviews, synthesising qualitative feedback, building journey maps, and turning support tickets and sales objections into product insight.

Skills 2

  1. 01discovery-synthesisTurn raw discovery input — interviews, support tickets, sales objections, usage data, reviews — into findings with evidence strength and a clear decision. Use when synthesising research, analysing feedback, or answering "what are users actually telling us?".
  2. 02prd-writingWrite a product requirements document that engineering can build from and stakeholders can argue with — problem with evidence, behaviour, edge cases, success metrics and rollout. Use when asked for a PRD, spec, feature document or user stories.

Commands 2

  1. 01/prdWrite a full product requirements document — problem with evidence, behaviour, edge cases, metrics and rollout.
  2. 02/prioritizePrioritise a backlog or a set of options with an explicit method, visible inputs and a stated recommendation.

What this team will not do

It will not invent research findings, usage figures or ticket volumes; present qualitative counts as population percentages; write untestable requirements; commit to dates for unscoped work; or announce something as generally available when it shipped to 5% behind a flag. If the evidence contradicts the plan, it reports that as the finding rather than writing a document to justify a decision already made.

€49one-time

→ Colleagues

Also worth hiring

All teams →
Team

Web Craft Studio

A design-led web team for sites that look authored rather than generated: art direction with a real point of view, motion with a purpose, craft-level frontend, copy that says something, plus the accessibility and performance discipline award-caliber sites usually skip.

6 agents · 2 skillsProduct & data · v1.1.0
€79incl. VATvs €45k / month on payroll
Team

Data & Analytics Team

Analytics engineering, SQL analysis, dashboard design, experimentation and data quality — organised around metric definitions everyone agrees on.

5 agents · 2 skillsProduct & data · v1.1.0
€49incl. VATvs €37.5k / month on payroll
Team

Migration & SEO Team

Replatforming that keeps the traffic: migration architecture, platform engineers for Shopify, WordPress/WooCommerce and PrestaShop/Magento, technical SEO, content and URL mapping, analytics and Search Console continuity, and international SEO.

8 agents · 3 skillsEngineering · v1.1.0