Proposals
Devplan creates proposals from connected customer feedback and product context. It brings a suggested scope, customer demand, and supporting evidence together so your team can decide which opportunities deserve a closer look.
Use Proposals when deciding what to build next. Instead of assembling a case from scattered conversations, start with the need Devplan has identified, inspect the sources, and develop the strongest ideas into projects.
Evaluate a proposal
Open Proposals and select an item. A proposal can include:
- Demand summary: the problem or opportunity behind the suggestion.
- Customers referenced: the customers connected to that demand, with account information where available.
- Proposed scope and relevant product areas: what the work could address and how it relates to your product.
- Evidence: the conversations, documents, signals, or issues supporting the proposal. Open these references to understand the original request and its context.
For example, when reviewing a proposal to improve onboarding, look at which customers encountered the problem, what prevented them from progressing, and whether the suggested scope addresses that need. This gives your team a concrete basis for discussion before committing to a project.
Compare priority
Where available, Devplan provides an estimated RICE score, combining reach, impact, confidence, and effort. You can sort proposals by this score and hover over a score to see its explanation.
Use the estimate to decide what to examine first, then weigh the evidence against your priorities and existing work. Missing customer information or a missing score means Devplan lacks that context; it does not establish that the opportunity has no value.
Develop it into a project
When a proposal is worth pursuing, select Define project. Weaver opens a conversation with the proposal's demand summary, scope, product context, and evidence notes already available. Work with Weaver to create a brief, adding constraints or clarifying the outcome you want.
Once the brief is generated, Devplan moves the proposal into Projects and opens its definition. Continue refining requirements and planning the work there. The proposal provides the starting case for the work; your team decides its priority and delivery commitments.
Keep the collection useful
Search for relevant proposals, sort by recency or RICE score, and add tags to organize them. Archive suggestions you do not want in the active collection.
If the collection is empty or lacks useful evidence, check your integrations. Customer conversations, meeting notes, support tickets, and CRM records give Devplan more context for identifying worthwhile work.