In-House SaaS Product Team System
Single-product companies whose in-house team develops a cloud product with continuous releases.
From ideas to the roadmap, building, release, usage measurement, and improvement — a product cycle that never stops.
No credit card required — your project is set up with the full system in under a minute
This is the system board as you'll receive it: workflow columns and starter cards showing the first steps
How does work flow in this system?
Every idea or customer request enters as a card in “Ideas”, where it is gathered and studied; in the periodic priority review, the product manager moves the selected ones to “Prioritized” against clear criteria: size of impact, number of requests, and cost to build. When it enters the release plan, it moves to “Build” with the developers, then “Release” when shipped to users with release notes, then “Measure”, where usage metrics are watched for a defined period, and finally “Improve” if the feature needs refinement based on the numbers — and a new cycle begins from there.
The Forum is the product council: roadmap decisions, which ideas were accepted and which rejected and why — transparency that prevents closed topics from being reopened every month. Announcements carries release notes to the whole team: what shipped today and what Support and Customer Success must know about it before users ask them. Chat is for daily coordination among developers. Dues posts customer subscriptions if connected to the system, so recurring-revenue growth shows next to development activity.
The product manager owns the “Ideas” and “Prioritized” columns and writes the specs for whatever enters “Build”; developers execute and move cards to “Release”; and the customer success team feeds “Ideas” with classified user requests and takes part in “Measure” with market feedback, checking Announcements before every release to ready the answers customers will hear. Decisions flow from customer data and requests to the product manager to the Forum to the build plan.
Who does what?
The operational roles in this system and each role's responsibility in daily work — assign them to your team as-is or adapt them to your reality.
Product Manager
Owns “Ideas” and “Prioritized”: studies and classifies requests and selects what enters the release plan, writes specs, and documents roadmap decisions in the Forum.
Developers
Build whatever enters “Build” to the approved specs, move cards to “Release”, and share in cost estimation before committing.
Customer Success
Feeds “Ideas” with classified user requests and recurring complaints, contributes to “Measure” with features' impact on customer satisfaction, and readies their team for every release from Announcements.
Data Analyst
Builds the usage-measurement dashboards for each feature in “Measure” — adoption and churn rates — and provides a neutral reading on which the product manager bases the “Improve” decision.
What's prepared for you from day one?
System units
- Tasks — A kanban board with workflow columns and execution cards
- Chat — The team's fast daily coordination channel
- Forum — Documented discussions in organized sections — decisions and knowledge that never get lost
- Announcements — The official voice of management — circulars and alerts that reach everyone
- Dues — Internal money with strict privacy — dues, advances, and expenses
Forum sections (4)
- Product Decisions & RoadmapWhich features were accepted and which rejected and why, and the approved roadmap order — a reference that prevents reopening closed decisions.
- Aggregated Customer RequestsPatterns of recurring user requests with their volume and impact — the raw material priorities are built from.
- Measurement ResultsReading the usage metrics of each shipped feature: did it hit its goal? And what do we conclude for coming releases?
- UX & InterfaceProposed experience and interface improvements with examples and references, before they enter build plans.
«Working Rules for This System» — Pinned in the forum
1) No building outside “Prioritized”: everything entering “Build” has passed the priority review and has a written spec. 2) Acceptance and rejection decisions are documented with their reasons in the “Product Decisions” section and are not re-discussed without new data. 3) Release notes are published in Announcements before or with the release — the support team is never surprised by a user's question. 4) Every shipped feature passes through “Measure” with predefined metrics before it is judged. 5) Customer requests are logged as cards in “Ideas” however small — collective memory does not depend on individuals. 6) Linked customer subscriptions are posted in Dues and reviewed monthly with the product's growth.
Welcome announcement: «Welcome to the Product System»
From today, every feature passes as a card from “Ideas” to “Improve”, roadmap decisions are documented in the Forum with their reasons, and every release's notes are published here before they reach users. First step: gather the scattered ideas into the “Ideas” column and approve the next release's priorities. The working rules are pinned in the Forum.
Systems similar to this one
Ready? Your first project is two minutes away
Create your free workspace now, and invite your team before the day is over.