Skip to main content

Branching for non-org teams


Jeff_McKeand

Branching is awesome, but restricting it to org-only teams is not. Experimentation and versioning are essential, table-stakes practices in product design, no matter the number of designers on a team.

Figma has always been focused on making great design accessible to and inclusive of all, but this pricing strategy is exclusionary in nature. Even if there are restrictions for number of branches, branching should be available to non-org teams. Please fix.

Pavels_Amosovs

Voted! I sincerely hope this was a mistake 🙂


Daria_Feszak

I agree with you 100%.


Jerome1

Yes it’s a shame if it’s for organization only, i hope this just for the beta… Beacause the non-org plan have teams and need also this kind of features !


Niki
  • April 27, 2021

I think it’s a must-have feature even for the smallest design entity. We always do branching for explorations, iterations or whatever. But at the moment in a more or less manual way, e.g. via version history or via duplicating files. There are many use cases where branching is very very useful.


DivinoAG

I absolutely agree. Branching as implemented on Figma is absolutely groundbreaking, and it could be the way to make Figma become the equivalent to Github for designers. But limiting it to Org will keep it as something most users will never see, hindering the ability to learn how to work in a professional environment.

If anything, I think this is backwards: branching is something that Figma should push to the widest audience possible, and make it available for Open Source projects for instance.


h.rude
  • May 7, 2021

100% agree. Why restrict it to Org? We are a team of 2 designers and our current pipeline is to create mockups meeting the requirements, without adding any extra nice to haves first, so the DevTeam knows exactly what to do for the next release. But of course the UX work continues, after the Dev-Handoff and also Text QA is taking place on the “first concept”, whiel UX is already working on the next steps.


Pavels_Amosovs

Why restrict it to Org?

Monetization? 🙂 I guess the hypothesis was that because this is a real pain for many small teams or even individuals, so it’s a great way to force us to upgrade to the Org plan. Plus, the Org plan has a yearly subscription 💰 Not sure if this will work though 🙂


Laszlo_Ambrus

We looked into upgrading, but for three times the cost and no other useful, for us at least, feature it makes little sense. Not to mention the annual billing doesn’t work for companies who us a lot of contractors, it’s way too rigid.


h.rude
  • May 12, 2021

As @Laszlo_Ambrus said. Thinking about cost and benefit, it’s just makes me really sad. For us, there is nothing that justifies the increase of costs for “just” the branching. I hate to say “just” because I’d say it’s essential, but currently the work around costs us less than paying the annual subscription.


Jordan_Gardiner

I hope we get some clarity on this because it’s a feature that 100% benefits all designers. I’d expect this to be at least on the pro plan.


Pavels_Amosovs

On the other hand, seems like the dark theme is much more important to the majority of designers here 😃


Logan_LaBo

I’m on a team of 8 or so. While we don’t need all the organization features out our size, we definitely need this one! Totally agree.


Sam_Tupy

This is a great call. I’m in full support.


Vinicius_Rosa

I also feel like pro plan should have at least some version of the branching feature. Maybe offering it as a paid addon for less than the extra $30/editor.


Gary_Whitter

I totally agree. I’m the only designer in the company, but this feature is essential. It should be offered as an add-on or a paid plugin. Moreover, they are asking for a minimum of 3 editors to switch to the “Organization” plan. In order to have this feature, you’ll have to pay US$ 1,620.00 / year. It’s ridiculous! I think it goes against the vision that Figma offered us when it started. 😡


Logan_LaBo

Bumping this. It’s been so long since I commented I actually forgot I did and came here to make a new ticket requesting this. Please add this to the Professional plan Figma!


Peyi_Oyelo

Bump Bump. I need this a lot!!


bhanuja
  • January 17, 2023

Absolutely! Bump! This is an incredible feature that should be brought to non-org specific users; I use it within an organisation, but also see use cases for it in a professional model.


Seriously ridiculous that Branching is not a common feature of the tool.


dvaliao
Figmate
  • Community Support
  • March 25, 2024

Hey All, thanks for the feedback and apologies for the late acknowledgement!

We hear you. This is definitely a feature that could benefit all users. We’ll pass this topic onto our team for future consideration.


Rodrigo3

Figma has been “considering it” for years but cash grab is more important as usual. And freelanced small companies seem not to be deemed important as clients.


Lee_Hayward

2024 - Is branching coming to ‘lesser’ plans?

I freelance design and run my own small company, I don’t have anyone else in my team, it’s just me. I’m constantly changing designs, but it’s hard to keep track without branching; however, I cannot access this feature as a) I cannot justify paying £40 a month just for this feature, and b) this plan requires a minimum of 3 seats which means £120 a month.

This is a core free feature in the coding workspace, so why is this gatekeeped at such a ludicrous price for multi-membered teams only?

Figma was built on individuals like me adopting it before it was mainstream, and now popular, the full benefit range has left us behind. I don’t even mind paying, just enable it in the professional plan…


Nelson3
  • October 17, 2024

I don’t mind paying for features but for individual designers being forced into buying into 3 seats just to get branching is ridiculous. Going from $180 to $1,620 a year for one feature makes zero sense on any business level.

Branching is a foundation feature for individual designers not just organizations. I hope Figma moves this feature into the Professional tier or allow Professionals to buy into the branching feature individually.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings