For product managers. From a rough thought to a considered decision.
Turn your product memo into a decision document with a clear recommendation, traceable evidence, and explicit uncertainty. Catch the weak assumption before stakeholder review鈥攁nd change your recommendation when the facts call for it.
In development 路 Try the interactive example below. Hosted reviews and paid plans are not available yet.
Product memo
Our self-serve conversion rate fell from 8% to 5% last quarter. Several sales interviews mentioned price, but we have not isolated the cause of the decline.
We recommend reducing the entry-level price by 30% to improve conversion.
Select the highlighted claim to examine it.
Preview the order of ideas before changing the document.
Scripted example, not a live AI review. Nothing you do here is submitted or saved.
01 路 A stronger decision document
Bring a product strategy, proposal, or decision memo. Examine the claims that matter, connect them to evidence, and see which unresolved questions could change the recommendation.
The planned experience keeps the document at the center. Every review should lead to a useful next step: supply evidence, revise the recommendation, or make the uncertainty explicit.
Write Capture the problem and the decision you are proposing.
Examine Inspect a claim, its evidence, and what remains uncertain.
Revise Preview a change and consider the conclusions it affects.
Share Explain your recommendation and what could change it.
02 路 Rigorous reasoning
A polished paragraph can still rest on a weak assumption. Diyalamp鈥檚 planned review experience focuses on the few questions that could materially change your product decision.
Distinguish an observation from an explanation. See whether the evidence supports what you are saying, and examine a more precise formulation.
A claim proportionate to its support.When an assumption changes, see which recommendations may need another look. You choose what to revise.
A coherent argument after each change.Use an optional story spine to rearrange the ideas in your memo. Preview the structure before accepting it.
A clear path for your reader.Examine the strongest alternative, a pivotal uncertainty, or the evidence that would reverse your recommendation.
A decision that can be reconsidered.03 路 Organizational culture
Move from one well-reasoned memo to a shared product practice. Make claims traceable, alternatives visible, and uncertainty explicit across your team.
The long-term vision is an organizational home for writing standards and decision rationale, so teams can understand why a choice was made and when to revisit it.
Rigor should help people think. It should never become a document quota, an employee score, or another approval checklist.
Shared standards, team records, and organization-wide governance are roadmap capabilities.
From one PM to a product organization
Three planned offerings, one purpose: stronger product thinking. Explore the free example today; subscriptions and checkout are not open.
For individual product managers
A thoughtful place for your next consequential memo.
A shared practice
For product teams
Make rigorous review part of how your team works.
For product organizations
Support a consistent decision-writing practice across teams.
Capabilities describe our direction, not currently available features. Pricing and delivery scope will be confirmed before any purchase.
Start with a real review problem
We鈥檙e exploring a six-week design-partner pilot with small product teams: review selected memos, establish a lightweight review standard, and learn which changes improve the team鈥檚 decision process.
The first conversation is about your review bottleneck. Scope, delivery, confidentiality, and pricing would be agreed before a pilot begins.
Discuss a pilotOpens an email draft. Please describe the problem without sending confidential documents.
Bring A recurring problem with proposals, evidence, or review cycles.
Try A focused review using an approved or sanitized memo.
Learn Which material weaknesses were caught and resolved.
Decide Whether the value warrants a continuing team practice.
An open foundation
The open-source engine organizes review around framing, evidence, reasoning, alternatives, and an explicit decision. The planned product turns that foundation into a useful writing experience.
AI findings can be wrong. Authors must be able to inspect, challenge, and dismiss them. This approach does not guarantee a correct business outcome.
Explore the open-source engineThe interactive pricing-memo example on this page and the open-source engine. Hosted review, accounts, subscriptions, and team workflows are still in development.
The aim is to help you develop and test your reasoning. Proposed edits should be visible, reversible, and accepted by you. The final decision stays yours.
The initial commercial focus is reviewing consequential product documents. A calm writing experience and shared organizational standards are part of the broader direction.
No. A strong review can change the recommendation. The goal is a decision proportionate to the evidence, including honest uncertainty and the strongest alternative.
Clear words. Considered decisions.
Try the pricing memo. See how one weaker premise can change the right next step.
Explore the decision review