Skip to main content
Question

Confusing Dev Seat Pricing, Proration Transparency, and Vendor Access Limitations

  • March 25, 2026
  • 0 replies
  • 29 views

Mustho

 

Hi Figma team,

I wanted to share some feedback based on my experience using the Organization plan, specifically around Dev seats, billing transparency, and external collaboration.

1. Dev Seat Pricing vs Actual Charge (Proration Confusion)

On the pricing page, a Dev seat is clearly listed as $25/month. However, when attempting to add a Dev seat, the upcoming invoice shows a charge of $175.89.

While I understand this is likely due to prorated billing until the end of the billing cycle, this is not clearly communicated in the UI.

Issue:

  • The pricing page sets an expectation of a simple monthly cost

  • The invoice shows a significantly higher amount without a clear breakdown

  • Users are left confused and unsure if this is an error

Suggestion:

  • Show a clear cost breakdown before confirmation:

    • Monthly price

    • Proration period (e.g., “7 months remaining in billing cycle”)

    • Total calculated cost

  • Add a tooltip or inline explanation explaining why the price differs from $25

2. Lack of Cost Transparency Before Seat Confirmation

Currently, the user only sees the final prorated amount in the invoice view, not during the decision moment.

Suggestion:

  • Add a pre-confirmation modal like:

    • “You will be charged $175.89 today for this seat (covers Apr–Oct billing cycle)”

  • This would significantly improve trust and reduce hesitation

3. External Vendor Access Limitations

A major challenge is working with external development vendors.

Currently:

  • To give proper Dev Mode access, we must assign a Dev seat

  • All seats are billed to our organization

  • There is no