Cost Comparison
Feature Detail
Description
The Cost Comparison feature presents a side-by-side breakdown of the costs and overhead associated with running a peer mentor program manually versus using Meander. It highlights concrete line items such as staff hours spent on Excel aggregation, paper-based reporting, manual Bufdir submission preparation, and coordinator overhead - set against Meander's subscription cost and projected efficiency gains. The widget is designed to be embedded on the sales website alongside or below the Impact Calculator, reinforcing the ROI narrative with a structured cost-benefit framing that addresses the most common objection in the sales process.
Analysis
Budget-conscious buyers in the non-profit and public-sector space rarely approve software purchases on feature merit alone - they need to demonstrate that the cost is justified relative to current spend. The Cost Comparison widget directly addresses this by making the hidden costs of manual workflows visible: coordinator hours, reporting errors, volunteer churn from friction, and compliance risk. By anchoring the conversation to existing expenditure rather than new spend, the widget reframes Meander as cost-neutral or cost-reducing in most realistic scenarios. This is particularly effective for organizations already paying staff to manually aggregate Word forms and Excel sheets, as described by NHF and HLF in the workshop documentation. The feature supports the sales team with a shareable artifact and reduces time-to-decision for procurement stakeholders who need structured justification.
The widget is a static or lightly interactive React component in the Next.js sales website. It renders a two-column comparison table with line items for manual-process costs on the left and Meander costs on the right, with a net savings row at the bottom. If the Impact Calculator is present on the same page, the widget optionally reads the user-entered organization size to scale the manual-cost estimates dynamically; otherwise it defaults to a median organization profile. No backend is required. Styling must match the sales website design system and remain fully responsive. Line items and assumptions must be editable via a simple content configuration object so the sales team can update numbers without code changes. All table content must be screen-reader accessible with proper table semantics and column headers.
Components (42)
Shared Components
These components are reused across multiple features
User Interface (9)
Service Layer (15)
Data Layer (8)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.