Someone can check option 1 (for example) for radio buttons in the pricing table and sign it, and then the second person can change it to option 2.
Like other fields, the radio buttons and checkboxes should be assigned to a role or an individual.

Pricing Table: Predefined tokens (#2 need)
Pricing Tables are the main reason we use PD, so the tokens that pre-fill from SF is information can't be lost.

Ability to set up default tax for the pricing table

Duplicate price column in a pricing table.

Sometimes people want to show a recipient how much they are saving per month per pricing table line item in the pricing table before the 12-month-term multiplier (or whatever) is applied.

The ability to lock a section of the pricing table so that users have access to edit a column within the table but admins have the ability to lock certain columns down.

Ability to have product description in the pricing table pulled from HubSpot in a way it is inside the HubSpot in the product description. ex: Bulleted points.

Pushing SKU from Hubspot to PandaDoc.

Offer a conditional discount based on time- For instance, if the customer approves within the first 7 days after receiving the quote, they'll get 10% off, but if after the 7 days pass, the 10% discount option is removed.

Make pricing table footer fields available for custom mapping

Allow users to add the Cost of Goods as a column in a pricing table.

The option to make SKU column invisible for the client (when the document is sent) but visible after signing the document for the sender (or any team member).

The option to have the Quantity column for an unchecked box in the pricing table automatically set to 0.