Version 4.3Shipped
- Export any report as a PDFYou voted for this
- Sign-in stays on after the app closes
Use cases
One loop, seven ways in
Who hears customers and who decides, on the same evidence.
Product managers
Get your week back for strategy
- One inbox, duplicates flagged
- AI drafts; you accept, edit or discard
- The day starts with what needs you
- Ideas to triage12
- Problems to confirm3
- Tickets due4
- Replies due2
Written by AI · weekly brief
Grew: “Reports are hard to share”, 9 new votes from 4 customers.
Shipped: version 4.3, with 2 problems.
Told: 49 people, by email and in the portal.
Heads of product
Prioritise by evidence, not by volume
- Ideas, customers and votes on every problem
- A customer counts once, however often they ask
- Points per cycle for the team’s view
- M.K. Shared an idea LUM-I12
- M.K. Opened a request LUM-T9
- M.K. Commented LUM-I13
- M.K. Voted LUM-I14
M.K.counts once
31customers
Support teams
Pass product problems on, with evidence
- Customers search the help center first
- A request becomes an idea in one click
- Requests stay private
Searched “share report”Export a report
R.A.
I need to send this report to my board every week. Is there a way?
L
Not yet. I added your request to the problem we are working on.
Only this customer and the team can see this request.
Turn into an idea LUM-I31 in LUM-P7
Engineering
Specs you can build from
- Versioned specs; Jira gets the saved one
- An epic per release, an issue per problem
- The ProductOS Agent runs it with Claude Code or Codex
Claude, through the MCP server
Log the call note about weekly reports for Lumen.
create_ideaLUM-I48Weekly report by email
add_idea_to_painLUM-I48LUM-P7
ProductOS Agent
$productos-agent run
LUM-P7Claude Code is working
productos/lum-p7-reports-are-hard-to-share
ProductOS: LUM-P7
Pull request opened
Founders and customer success
Close the loop with every customer who asked
- Everyone who asked or voted is told
- The changelog in customer language
- “You voted for this” on what they backed
October
49 emails sent In every voter’s portal
Companies with several products
One workspace per product, one bill
- Its own portal, keys and Jira project
- Switch between products in one click
- Priced per product, not per person
Teams that self-host
Your data on your own servers
- The same code as the cloud, with no open core
- Functional Source License; each version becomes Apache 2.0 two years after its release
- Without an AI key, no text goes to an AI provider
Your servers
- ProductOS
- Database
- Files
- Mail server
Offline helper No text to an AI provider
Functional Source LicenseEach version, from its release
Apache 2.0Two years later
Start with the requests you already have
Import a spreadsheet and see your first problems.