What is this?
Proposal(k) renders partner-branded plan services proposals from a Design(k) Pro plan output. It produces a fully formatted PDF in the TPA partner's design language — currently Cetera Retirement Plan Specialists.
How does the data get here?
In the standard pipeline, Design(k) Pro writes a payload to localStorage.designk_proposalk_export. Use "Pull from Design(k)" to read it. You can also paste a JSON payload directly, or load the bundled Cetera sample to see how things work.
What can I edit?
Sponsor identity, scenario summary, fees, tax credits, prepared date, and compliance notes. The participant roster and allocations come from Design(k) and aren't editable here — change them upstream if needed.
Multi-scenario
v0.2 supports 1–3 plan scenarios rendered side-by-side (e.g. Custom(k) + Easy(k)). Use the scenario tabs in the Review section to switch between scenarios and edit each one. The Worker renders all scenarios into a single PDF with a multi-column Opportunity Summary. V1 single-scenario payloads are auto-normalized to V2 format.
V1 backward compatibility
Payloads with a single scenario object (V1 format) are automatically normalized to the V2 scenarios[] array format when loaded. No changes needed to existing Design(k) integrations.