A note before you read
This Product Requirements Document (PRD) is a living document. We’re sharing it early with you so you can see where we’re headed and help shape it with your feedback. Nothing here is set in stone, and it shouldn’t be read as a firm commitment on features or timelines.
Your input will make the end result better , thanks for being part of the process!
- Martin
1. Problem Statement
End-customers must currently confirm every single product or product group when accepting an offer. For large and complex proposals (e.g. events with AV, catering, logistics), this creates unnecessary friction:
Customers must spend time clicking Yes on many mandatory groups, even though these are already part of the offer.
Offers can appear more complicated than necessary, with high-value groups shown as separate accept/decline decisions.
Some customers choose not to use the tool for acceptance at all and instead handle the process manually outside the system.
Project Managers (PMs) often pre-accept groups on behalf of the customer, which skews reporting and adds extra manual work.
2. Goals & Objectives
Reduce friction by removing unnecessary product-level acceptance for mandatory products.
Provide a simpler and more efficient acceptance process for end-customers.
Ensure the total price is clear and visible upfront.
Keep flexibility for upsell and cross-sell by retaining Yes/No/Maybe on optional products.
Increase conversion rates and shorten sales cycles.
Enable customers who currently handle acceptance manually outside the system to complete the process directly in the tool.
3. Scope
Functional Requirements
Introduce a new Feature Toggle:
AutoAcceptMandatoryProducts.When enabled:
Mandatory products:
Hide “Accept” column/heading.
Hide Yes/No/Maybe buttons.
Automatically set status = “Yes” when the offer loads.
Pre-included in the total price.
Optional products:
Keep existing Yes/No/Maybe functionality for upsell/cross-sell.
Applies at the product line level.
Applies to Offer view and the Confirmation PDF
4. Non-Goals
Group acceptance logic improvements (currently based on lowest product ID).
Handling offers that contain only mandatory products (edge case acceptance logic).
Advanced UI redesign for mixed offers.
Reporting/analytics adjustments for acceptance vs. estimates.
5. Acceptance Criteria
When the feature is enabled:
Mandatory products do not show Yes/No/Maybe controls.
Mandatory products automatically have status = “Yes”.
The Offer total includes mandatory products upfront.
Optional products always retain Yes/No/Maybe controls.
Offers with only mandatory products can not be accepted (MVP limitation).
6. Release Plan
Phase 1 (MVP – this PRD):
Implement feature toggle.
Auto-accept logic for mandatory products.
Hide controls for mandatory lines.
Include values in total.
Phase 2 (Future iterations):
Group acceptance logic refinement.
Error handling for edge cases.
UI improvements for clarity.
7. Value & Impact
Business Value: Higher conversion rates, faster sales cycles, and stronger fit for event agencies and TMCs.
Customer Value: End-customers see a simple, clear total and can accept offers more quickly.
PM Value: PMs spend less time manually pre-accepting products or chasing customers for acceptance.
Adoption Value: Customers who previously worked outside the system due to limitations will be able to handle acceptance directly inside the tool.